get_methodology — DABYTE AI Visibility Index MCP Tool Read-only
get_methodology
(get methodology) is one of 5 tools on the
DABYTE AI Visibility Index
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_methodology from your client
- Claude Code DABYTE AI Visibility Index get_methodology run in your project directory
- Claude Desktop DABYTE AI Visibility Index get_methodology ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DABYTE AI Visibility Index get_methodology ~/.cursor/mcp.json
- VS Code DABYTE AI Visibility Index get_methodology .vscode/mcp.json
- Zed DABYTE AI Visibility Index get_methodology ~/.config/zed/settings.json
- Windsurf DABYTE AI Visibility Index get_methodology ~/.codeium/windsurf/mcp_config.json
- Cline DABYTE AI Visibility Index get_methodology ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DABYTE AI Visibility Index get_methodology ~/.gemini/settings.json
- Grok DABYTE AI Visibility Index get_methodology .mcp.json (in your project root)
- ChatGPT DABYTE AI Visibility Index get_methodology Settings → Connectors → Advanced → Developer mode
- Claude.ai DABYTE AI Visibility Index get_methodology Settings → Connectors → Add custom connector
- LangChain DABYTE AI Visibility Index get_methodology pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http visibility-index https://dabyte.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.