Document card — docbin MCP Resource

Document card is one of 2 resources on the docbin MCP server. Connect the server and your client can attach it as context.

by client

How to attach Document card from your client

• Claude Code docbin Resource/Document card run in your project directory
• Claude Desktop docbin Resource/Document card ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor docbin Resource/Document card ~/.cursor/mcp.json
• VS Code docbin Resource/Document card .vscode/mcp.json
• Zed docbin Resource/Document card ~/.config/zed/settings.json
• Windsurf docbin Resource/Document card ~/.codeium/windsurf/mcp_config.json
• Cline docbin Resource/Document card ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI docbin Resource/Document card ~/.gemini/settings.json
• Grok docbin Resource/Document card .mcp.json (in your project root)
• ChatGPT docbin Resource/Document card Settings → Connectors → Advanced → Developer mode
• Claude.ai docbin Resource/Document card Settings → Connectors → Add custom connector
• LangChain docbin Resource/Document card pip install langchain-mcp-adapters

Other resources on this server

• Document list

docbin also offers 4 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.