Problem to solve
Adding an MCP server in DimCode currently requires users to manually write complete JSON configuration (transport type, URL, headers, etc.). This is a high-friction experience — error-prone and intimidating, especially for new users.
For the most common case — HTTP/SSE-based MCP services — users typically only need to provide two pieces of information: the server URL and an API key. Yet they are forced to deal with the full JSON structure, which is easy to get wrong (missing commas, mismatched quotes, wrong field names).
Desired experience
- Form-based adding: Provide a visual form for the most common scenario (HTTP/SSE). Users just fill in two fields — URL and API Key — and click to add. No JSON required.
- One-click paste: Support pasting a connection string directly from the MCP provider (e.g.
https://xxx.com/mcp?key=sk-xxx), and auto-parse it into the correct configuration.
- JSON advanced mode: Keep the raw JSON editor as an "Advanced" collapsible section for power users who need full control over the configuration.
- Preset templates: Built-in templates for popular MCP services (Serper, Filesystem, GitHub, etc.) — select a template, fill in the key, done.
Current workaround
- Manually write the full JSON configuration, field by field, referencing documentation.
- Prone to format errors (missing commas, wrong quotes, typos in field names) that silently break the config.
- New users don't know the expected JSON structure and must search through docs just to get started.
Use case
- Quickly connect third-party MCP services (search, databases, API tools) without touching JSON.
- Lower the onboarding barrier for new users who just want to connect a service and go.
- Reduce time wasted debugging configuration errors that stem from manual JSON editing.
想解决的问题
当前在 DimCode 中添加 MCP Server 需要用户手写完整的 JSON 配置（transport 类型、URL、headers 等），门槛高、易出错。
对于最常见的 HTTP/SSE 类型 MCP 服务，用户通常只需要提供两个信息：服务端 URL 和 API Key，却被迫面对完整的 JSON 结构，容易因格式错误（少逗号、引号不对、字段名拼错）导致配置失败。
期望的体验
- 表单化添加：提供可视化表单，最常见场景（HTTP/SSE）只需填两个字段 — URL 和 API Key — 一键添加，无需写 JSON。
- 一键粘贴：支持从 MCP 提供方直接复制连接字符串（如
https://xxx.com/mcp?key=sk-xxx），自动解析填充为正确配置。
- JSON 高级模式：保留手写 JSON 入口给高级用户，作为「高级 / Advanced」折叠项。
- 预设模板：内置常用 MCP 服务的模板（Serper、Filesystem、GitHub 等），选择模板后只需填 Key。
当前替代方案
- 手动编写完整 JSON 配置，对照文档逐字段填写。
- 容易因格式错误导致配置失败，调试耗时。
- 新用户不知道 JSON 结构，需要翻文档才能上手。
使用场景
- 快速接入第三方 MCP 服务（搜索、数据库、API 工具），无需接触 JSON。
- 降低新用户上手门槛，连接即用。
- 减少因手动编辑 JSON 导致的配置错误和调试时间。
Problem to solve
Adding an MCP server in DimCode currently requires users to manually write complete JSON configuration (transport type, URL, headers, etc.). This is a high-friction experience — error-prone and intimidating, especially for new users.
For the most common case — HTTP/SSE-based MCP services — users typically only need to provide two pieces of information: the server URL and an API key. Yet they are forced to deal with the full JSON structure, which is easy to get wrong (missing commas, mismatched quotes, wrong field names).
Desired experience
https://xxx.com/mcp?key=sk-xxx), and auto-parse it into the correct configuration.Current workaround
Use case
想解决的问题
当前在 DimCode 中添加 MCP Server 需要用户手写完整的 JSON 配置（transport 类型、URL、headers 等），门槛高、易出错。
对于最常见的 HTTP/SSE 类型 MCP 服务，用户通常只需要提供两个信息：服务端 URL 和 API Key，却被迫面对完整的 JSON 结构，容易因格式错误（少逗号、引号不对、字段名拼错）导致配置失败。
期望的体验
https://xxx.com/mcp?key=sk-xxx），自动解析填充为正确配置。当前替代方案
使用场景