DocLD MCP — Use DocLD in Your IDE
DocLD provides an MCP (Model Context Protocol) server so AI assistants in your IDE can search the official DocLD documentation and—with an API key—your own knowledge bases and documents.
What you get
One server with four tools:
| Tool | Description | API key |
|---|---|---|
| search_docld_docs | Search the official DocLD docs (guides, API reference, features) | Not required |
| list_knowledge_bases | List your DocLD knowledge bases | Required |
| search_my_documents | Semantic search over your documents | Required |
| chat_with_my_documents | RAG chat with your documents (non-streaming) | Required |
Use search_docld_docs when building with DocLD so your AI can pull accurate API and product info. Use the other three when you want the AI to query your own DocLD data (knowledge bases, documents, chat).
Setup by IDE
Cursor
- Open Cursor Settings → Features → MCP.
- Click Add New MCP Server.
- Configure the DocLD MCP server (stdio):
- Command:
npx - Args:
["-y", "@docld/mcp"]
- For “my data” tools (list knowledge bases, search documents, chat), set your DocLD API key in the server’s environment:
- In the same MCP server config, open Environment variables (or equivalent).
- Add:
DOCLD_API_KEY= your key (starts withdocld_).
You can also add the server via config. In .cursor/mcp.json or ~/.cursor/mcp.json:
{
"mcpServers": {
"docld": {
"command": "npx",
"args": ["-y", "@docld/mcp"],
"env": {
"DOCLD_API_KEY": "docld_your_api_key_here"
}
}
}
}Claude (claude.ai)
- Open Settings → Connectors.
- Add a custom connector that runs the DocLD MCP server (stdio:
npx -y @docld/mcp). - If your client supports env vars for the connector, set
DOCLD_API_KEYfor “my data” tools.
Claude Code and other MCP clients
Use the same stdio command and args as above. For general MCP setup:
Remote (hosted) — use a URL instead of npx
You can connect to DocLD’s hosted MCP endpoint so you don’t need to run npx or install the package.
- In Cursor (or your MCP client), add a remote MCP server.
- URL:
https://app.docld.com/api/mcp(or your DocLD app URL +/api/mcp). - For “my data” tools, the client must send your DocLD API key. Configure the client to send the key (e.g. in the remote server’s auth/header settings, if supported):
Authorization: Bearer docld_your_key.
If your client does not support sending a Bearer token for remote MCP, use the stdio setup with DOCLD_API_KEY instead.
Creating an API key
Create a key in DocLD so the MCP can access your knowledge bases and documents:
- In the DocLD app: Settings → API keys → create a key.
- See API keys for details and scopes.
Use this key only in your local MCP config; do not share it or commit it to a repo.
Optional: Claude Code plugin
If you use the DocLD Claude Code plugin, it can use the DocLD MCP when configured—so the DocLD skill can search docs and your data from Claude Code. For full setup, see Claude Code plugin.
Discovery & Registry
DocLD MCP is discoverable in MCP registries so Cursor and Claude users can find and add it quickly:
| Registry | How to add |
|---|---|
| Cursor | Cursor Settings → Features → MCP → Add server; search for “DocLD” or add manually |
| Claude Code | Add connector: npx -y @docld/mcp with DOCLD_API_KEY |
| MCP Directory | Listed as @docld/mcp on npm and in MCP server listings |
To add DocLD to your AI assistant, use the package name @docld/mcp or connect to the hosted endpoint at https://app.docld.com/api/mcp.
Summary
| Item | Detail |
|---|---|
| Package | @docld/mcp (stdio) |
| Command | npx -y @docld/mcp |
| Remote URL | https://app.docld.com/api/mcp — send API key in Authorization: Bearer docld_... for “my data” tools |
| Docs tool | search_docld_docs — no API key |
| My data tools | list_knowledge_bases, search_my_documents, chat_with_my_documents, parse_document, extract_from_document, summarize_document, compare_documents — set DOCLD_API_KEY (stdio) or Bearer header (remote) |
| API key | Create at Settings → API keys or API keys |