Routara
MCP · CLAUDE DESKTOP / PRACTICAL GUIDE

Connect Routara MCP to Claude Desktop

Claude Desktop can launch a local MCP process and expose its tools to a conversation. The Claude account continues to provide the host model; Routara provides the tools you explicitly call. Keep these two accounts and their billing separate.

01

Prepare the runtime

Install a supported Node.js runtime so npx is available. Create a Routara API key and keep the full value in a local secret store. Check that your Routara account has an eligible text trial or wallet balance.

02

Configure a local stdio server

Add a Routara entry in Claude Desktop’s MCP configuration. Exact settings location varies by client release; use the client’s current MCP settings screen. Replace the placeholder locally and never publish the configuration file.

{
  "mcpServers": {
    "routara": {
      "command": "npx",
      "args": ["-y", "routara-mcp"],
      "env": { "ROUTARA_API_KEY": "your-key" }
    }
  }
}
03

Check the tools, then call one

Restart Claude Desktop so the configuration loads. First confirm that Routara tools are listed. Then run a short routara_chat call. A missing tool indicates process or configuration trouble; a failed tool result indicates a key, policy, model, or balance problem.

Before you ship

  • Check the MCP process log if the server fails to start.
  • Keep the API key out of conversation transcripts and repositories.
  • Test text first; image and video jobs can have different costs and permissions.