domain-card — domaindrift MCP Resource
domain-card
is one of 1 resource on the
domaindrift
MCP server. Connect the server and your client can attach it as context.
by client
How to attach domain-card from your client
- Claude Code domaindrift Resource/domain-card run in your project directory
- Claude Desktop domaindrift Resource/domain-card ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor domaindrift Resource/domain-card ~/.cursor/mcp.json
- VS Code domaindrift Resource/domain-card .vscode/mcp.json
- Zed domaindrift Resource/domain-card ~/.config/zed/settings.json
- Windsurf domaindrift Resource/domain-card ~/.codeium/windsurf/mcp_config.json
- Cline domaindrift Resource/domain-card ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI domaindrift Resource/domain-card ~/.gemini/settings.json
- Grok domaindrift Resource/domain-card .mcp.json (in your project root)
- ChatGPT domaindrift Resource/domain-card Settings → Connectors → Advanced → Developer mode
- Claude.ai domaindrift Resource/domain-card Settings → Connectors → Add custom connector
- LangChain domaindrift Resource/domain-card pip install langchain-mcp-adapters
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.