find_data_source — Agent Demand Registry MCP Tool Read-only
find_data_source
(find data source) is one of 4 tools on the
Agent Demand Registry
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_data_source from your client
- Claude Code Agent Demand Registry find_data_source run in your project directory
- Claude Desktop Agent Demand Registry find_data_source ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Demand Registry find_data_source ~/.cursor/mcp.json
- VS Code Agent Demand Registry find_data_source .vscode/mcp.json
- Zed Agent Demand Registry find_data_source ~/.config/zed/settings.json
- Windsurf Agent Demand Registry find_data_source ~/.codeium/windsurf/mcp_config.json
- Cline Agent Demand Registry find_data_source ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Demand Registry find_data_source ~/.gemini/settings.json
- Grok Agent Demand Registry find_data_source .mcp.json (in your project root)
- ChatGPT Agent Demand Registry find_data_source Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Demand Registry find_data_source Settings → Connectors → Add custom connector
- LangChain Agent Demand Registry find_data_source pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-demand-registry https://agent-demand-registry.agent-demand-registry.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.