Free Developer Utility

Model Context Protocol
Config Generator

Generate 100% valid, tested JSON configuration blocks for Cursor, Claude Code, Windsurf, Cline, and Zed. Zero signup required.

File Location: .cursor/mcp.json

How Model Context Protocol (MCP) Configuration Works

The Model Context Protocol (MCP) developed by Anthropic standardizes how AI coding agents communicate with external tools, APIs, and file systems. Whether you are using Cursor, Claude Code CLI, Windsurf, or Cline, your IDE looks for an mcpServers dictionary in its local JSON settings to establish live tool connections.

Cursor IDE Integration

Cursor supports project-level MCP servers. Placing an mcp.json inside the .cursor/ folder allows your agent to auto-discover SEO diagnostic tools whenever you prompt it inside Composer.

Claude Code Terminal Agent

Claude Code CLI reads from claude_desktop_config.json. Once configured, you can type /seo audit directly in your terminal to autonomously crawl pages and generate fixes.

Windsurf & Cline

Windsurf's Cascade agent and Cline for VS Code natively load MCP tools over HTTP/SSE, granting your assistant zero-latency access to web scrapers, SERP data, and schema generators.

Frequently Asked Questions

Do I need to restart my IDE after updating the MCP config?
Most modern editors (Cursor 0.40+, Windsurf, and Claude Code) automatically hot-reload MCP server changes. If your agent does not see the new tools immediately, reload the IDE window or restart the terminal session.
Is my API key exposed when using MCP?
No. MCP configurations reside locally on your machine in the configuration directory. With RankForge, all SEO processing runs server-side on Cloudflare Workers edge, and API headers are never transmitted into the agent's context window.