burnlore_get_assignment — Burnlore MCP Tool
burnlore_get_assignment
(burnlore get assignment) is one of 3 tools on the
Burnlore
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call burnlore_get_assignment from your client
- Claude Code Burnlore burnlore_get_assignment run in your project directory
- Claude Desktop Burnlore burnlore_get_assignment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Burnlore burnlore_get_assignment ~/.cursor/mcp.json
- VS Code Burnlore burnlore_get_assignment .vscode/mcp.json
- Zed Burnlore burnlore_get_assignment ~/.config/zed/settings.json
- Windsurf Burnlore burnlore_get_assignment ~/.codeium/windsurf/mcp_config.json
- Cline Burnlore burnlore_get_assignment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Burnlore burnlore_get_assignment ~/.gemini/settings.json
- Grok Burnlore burnlore_get_assignment .mcp.json (in your project root)
- ChatGPT Burnlore burnlore_get_assignment Settings → Connectors → Advanced → Developer mode
- Claude.ai Burnlore burnlore_get_assignment Settings → Connectors → Add custom connector
- LangChain Burnlore burnlore_get_assignment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://burnlore.com/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.