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