OpenRouter (usage and credits) MCP server

What the model can do

OpenRouter account administration through a management key: credits bought, used and remaining, spend, requests and tokens by model, provider and day over the last 30 days, the account's API keys by name with their spend and limits, and workspaces with their spend limits. When asked, sets or removes a workspace's spend limit and creates, renames or deletes a workspace. Never calls a model, never changes a key and never returns a key value.

Reads

• openrouter_creditsOpenRouter credits for the account in USD: total bought, total used and what remains.
• openrouter_activityOpenRouter spend in USD, requests and tokens over the last 30 completed UTC days (OpenRouter keeps no more), summed by model, by day…
• openrouter_keysThe OpenRouter account's API keys by name and hash only: whether disabled, spend in total and this month, credit limit and what remains of it…
• openrouter_workspacesOpenRouter workspaces: id, name, slug, description, default text and image models, default provider sort and when created.
• openrouter_workspace_budgetsA workspace's OpenRouter spend limits in USD by interval (daily, weekly, monthly, lifetime) and whether bring-your-own-key spend counts towards them.

Acts, when you ask

These change something in OpenRouter (usage and credits). The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• openrouter_set_workspace_budgetSets the USD spend limit of an OpenRouter workspace for one interval (daily, weekly, monthly or lifetime), creating or replacing it.
• openrouter_delete_workspace_budgetRemoves an OpenRouter workspace's spend limit for one interval, so spend through that workspace is no longer capped at it.
• openrouter_create_workspaceCreates an OpenRouter workspace with a name and slug, and optionally its description, default text and image models and default provider sort.
• openrouter_update_workspaceRenames an OpenRouter workspace or changes its slug, description, default text or image model or default provider sort.
• openrouter_delete_workspacePermanently deletes an OpenRouter workspace with its budgets and guardrails, and disables its classifiers and broadcast destinations.

Connect it

First connect OpenRouter (usage and credits) on Dashboard → Connections, then add Memtro to your client once. The OpenRouter (usage and credits) tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared OpenRouter (usage and credits) connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How much OpenRouter credit is left?
• › Which model cost most this week?
• › Which key spent most this month?
• › Which keys has nobody used?
• › Cap the staging workspace at 50 dollars a day.

Questions

Is this an official OpenRouter (usage and credits) MCP server?

No. It is Memtro's MCP server with Memtro's OpenRouter (usage and credits) connector behind it: the connector reads OpenRouter (usage and credits) through its API with the credentials you connect on Dashboard → Connections, and OpenRouter (usage and credits) publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in OpenRouter (usage and credits)?

Only when you ask, and only what it has been granted: set a workspace's USD spend limit for a day, week, month or lifetime; remove a workspace's spend limit for one interval; create a workspace; rename a workspace or change its slug, description or default models; delete a workspace with its budgets and guardrails. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server