MCP Config Generator
Build and sanity-check Model Context Protocol server JSON for Claude Desktop, Claude Code project files, Cursor, VS Code, and other MCP clients. Generate stdio, streamable HTTP, or SSE starters without uploading the config.
Reviewed June 1, 2026. Privacy model: tool input is processed in your browser and is not uploaded to BytePane servers.
Start from a preset
Claude Desktop style JSON
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/me/Documents"
]
}
}
}Project/client JSON with explicit type
{
"mcpServers": {
"filesystem": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/me/Documents"
]
}
}
}Validation checklist
Server key is portable
The generated mcpServers object can use this server name safely.
stdio command is present
Arguments are emitted as an array so the client does not need to parse a shell string.
Client schema differs by product
Claude Desktop, Claude Code, Cursor, VS Code, and extension-based MCP installs do not always use identical fields. Treat this as a copy-ready starter and confirm against current client docs.
Where to put the config
Claude Desktop
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Project clients
Claude Code: .mcp.json or CLI add-json workflow
Cursor/VS Code: check the current client docs for workspace paths.
Current-doc caveat
Claude Desktop also supports desktop extensions, and MCP clients are changing quickly. Use this page to generate a clean starter, then verify the target client documentation before rollout.
Source checkpoint
Reviewed June 1, 2026 against the official Model Context Protocol local-server and server-building docs, Anthropic Claude Desktop MCP help, and Anthropic Claude Code MCP configuration docs. MCP client support for remote transports, desktop extensions, and project files can change; use this generated JSON as a starter and confirm against the client you will run.
Frequently Asked Questions
What does this MCP config generator create?
It creates copy-ready JSON with an mcpServers object, server key, command or URL, args, optional environment variables, and validation notes for common MCP clients.
Should I paste real API keys here?
No. The tool runs in your browser, but production secrets should still be handled locally. Use placeholders here, then fill real values in your client config or secret manager.
Why are there separate Claude Desktop and project JSON outputs?
Claude Desktop local configs commonly use a compact server object, while project-style configs often include an explicit type field. Client schemas can change, so verify against current docs before rollout.
Can this connect to remote MCP servers?
It can generate streamable HTTP and SSE starters, but each client controls which remote transports it supports. Confirm support in your target client before deploying.
Does this validate the MCP server itself?
No. It validates the shape of the generated starter config. You still need to run the client, inspect logs, and confirm the server exposes the expected tools.