/
Documentation

Meldoc MCP

Your AI assistant can read, search, create, and update your documentation — directly from the tools you already use. Meldoc exposes a native MCP server, so any client that speaks the Model Context Protocol connects in minutes.

Supported clients

  • Cursor — AI-powered code editor
  • Claude Code — Terminal-based Claude integration
  • VS Code — With MCP extensions
  • Windsurf — Codeium’s AI IDE
  • Claude Desktop — Via custom connectors (OAuth) or mcp-remote bridge
  • Claude.ai — Via custom connectors (OAuth; scoped token for restricted access)

How it works

Your AI assistant sends requests to the Meldoc MCP server at https://api.meldoc.io/mcp. The server authenticates your token, fetches your documentation, and returns results directly into your conversation. No local proxy, no npm, no Node.js required.

In this section

Getting Started with MCP — Set up MCP for your client in a few minutes.

IDE Setup — Configure the CLI-based MCP server for your IDE.

Authentication — Login methods and token management.

MCP Tools Reference — Available tools and what they do.

Workspace Management — Switch between workspaces in MCP.

Advanced Usage — Configuration files and environment variables.

Troubleshooting — Common issues and fixes.