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