Skip to main content

Cursor, VS Code & Windsurf

Connect SuperDocs to your code editor for AI-powered document editing alongside your development workflow.

Cursor

1. Create the config file

Create .cursor/mcp.json in your project root (or global config):
.cursor/mcp.json

2. Restart Cursor

The SuperDocs tools will appear in Cursor’s AI capabilities. Tools load at startup; if the tools panel says “Loading tools” for more than 10 seconds, restart Cursor again.

VS Code

1. Create the config file

VS Code reads MCP servers from a dedicated mcp.json file, not settings.json. Create .vscode/mcp.json in your workspace, or open the user-level file (shared across all workspaces) from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) with MCP: Open User Configuration. You can also run MCP: Add Server and pick HTTP.
.vscode/mcp.json
Note the shape: VS Code uses a top-level servers key and a type field ("http" for SuperDocs), unlike Cursor’s mcpServers + transport.

2. Start the server

Save the file, then start the server from the inline hint VS Code shows in mcp.json (or run MCP: List Servers and start it there). The tools appear in Copilot’s agent mode. If SuperDocs doesn’t show up, check the MCP server status in the Output panel, or restart VS Code.

Windsurf

Add the same configuration as Cursor to Windsurf’s MCP settings:

Test your connection

In your editor’s AI chat, type:
“Check the SuperDocs API health”
If configured correctly, the AI will call the health tool and report the API status.