MCP Config Generator
Generate MCP server configuration for Claude Desktop, Cursor, VS Code, and other clients.
Last updated Mar 2026
{
"mcpServers": {
"my-server": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/path/to/dir"
]
}
}
}How MCP Configuration Works
Each MCP client (Claude Desktop, Cursor, VS Code Copilot, Windsurf) uses a slightly different JSON configuration format to define which MCP servers to connect to. The configuration specifies the server name, transport type (stdio for local processes, SSE or Streamable HTTP for remote servers), the command to launch the server (for stdio), and optional environment variables like API keys. This tool generates the correct JSON format for your chosen client, so you can paste it directly into the config file without memorizing each client's schema differences.
Configuration File Locations
- Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows) - Cursor:
.cursor/mcp.jsonin your project root - VS Code (Copilot):
.vscode/mcp.jsonin your project root - Windsurf:
~/.codeium/windsurf/mcp_config.json
Transport Types
stdio launches a local process and communicates via stdin/stdout. Best for local tools like filesystem access, database queries, or CLI integrations. SSE (Server-Sent Events) connects to a remote HTTP endpoint with server-push capabilities — used for cloud-hosted MCP servers. Streamable HTTP is the newer transport that replaces SSE, supporting bidirectional streaming over standard HTTP — recommended for new remote server implementations.
Common MCP Servers
Popular MCP servers include: @modelcontextprotocol/server-filesystem (file system access), @modelcontextprotocol/server-github (GitHub API), @modelcontextprotocol/server-postgres (PostgreSQL queries), and @modelcontextprotocol/server-brave-search (web search). Browse the full list at the official MCP servers repository.