MCP Server
Use MisarCoder from any MCP client via the misarcoder_ask and misarcoder_complete tools.
MisarCoder ships an MCP (Model Context Protocol) server that exposes the gateway to MCP-compatible clients (Claude Code, IDE agents, and other hosts). It provides two tools — misarcoder_ask and misarcoder_complete — that wrap the gateway's chat-completions engine.
Two different MCP surfaces
Don't confuse these client tools with the gateway's MCP management REST endpoints (/mcp/configure, /mcp/servers, /mcp/tools, /mcp/call, /mcp/remove), which let MisarCoder connect out to other MCP servers. The tools on this page are what MisarCoder exposes to an MCP client.
When to use each tool
misarcoder_ask
Q&A and explanation — ask a question or have code/behavior explained. Best for short, conversational answers.
misarcoder_complete
Code generation — generate longer code (recommended for >30 lines) routed through the MoE engine.
How it maps to the gateway
Both tools ultimately call the OpenAI-compatible chat completions engine — misarcoder_ask for a concise reply, misarcoder_complete for a fuller code generation. Because they run through the gateway, they inherit its authentication and MoE routing.
Re-submitting MCP changes
Per Misar policy, the MCP server is published to external directories/marketplaces. Any change to its tool definitions requires re-submitting the server to all directories — prefer fixing behavior in the gateway (server-side) over changing the MCP tool surface.
See Tools for the tool reference.