ToolBudget Router MCP

com.clauxel.toolbudgetrouterPublished by toolbudgetrouter.clauxel.comOfficial publisherv0.1.0Updated Oct 24, 2026

Paid remote MCP for context-budget routing, schema cost estimates, usage audits, and readiness.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A paid remote MCP server that lets an assistant route context budgets, estimate schema costs, audit usage, and check readiness.

What you can do
Route context budgets for tool and schema usage through a remote endpoint. Estimate the token or context cost of schemas before use. Audit usage so spending and consumption can be reviewed. Check readiness of the routing setup. Access is gated by a bearer token obtained after checkout and token claim.
When to use it
Consider it when you want an assistant to manage context budgets across tools and schemas, estimate schema costs ahead of time, and review usage. It suits setups where a paid, hosted routing layer is acceptable.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A bearer token is required in the Authorization header, issued after checkout and MCP token claim. Network access to the provider's endpoint is required.
Before you install
This is a paid service: a token is issued only after checkout, so expect a purchase or billing step. The Authorization bearer token is a secret and should be kept private. Usage audits and routing data are sent to the third-party provider.

Installation

In SourceWeft

  1. Open ToolBudget Router MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.clauxel.toolbudgetrouter%2Ftoolbudgetrouter-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "toolbudget-router": {
      "type": "http",
      "url": "https://toolbudgetrouter.clauxel.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.