RouteMyAgent Model Helper

dev.routemyagentPublished by routemyagent.devOfficial publisherv0.9.2Updated Oct 24, 2026

Discover available AI models and delegate analysis or code review from your existing agent.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant discover available AI models and delegate analysis or code review to them through a RouteMyAgent router.

What you can do
Discover the AI models available through the RouteMyAgent router and pick one for a task. Delegate analysis work to a model from within the existing agent session. Hand off code review to a delegated model. Access is authenticated with a RouteMyAgent router access token.
When to use it
Useful when you already route model calls through RouteMyAgent and want your assistant to find suitable models or offload analysis and code review to them without leaving the session.
Requirements
A remote streamable HTTP endpoint at routemyagent.dev; no local package or runtime is needed. A RouteMyAgent router access token is required and sent in the Authorization header; the token is created at routemyagent.dev. Network access to the endpoint is required.
Before you install
The server requires a RouteMyAgent router access token in the Authorization header, so treat it as a secret and avoid exposing it in logs or shared configuration. Delegated analysis and code review send your content to the models behind the router, a third party; check what data leaves your session before using it on sensitive code.

Installation

In SourceWeft

  1. Open RouteMyAgent Model Helper 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/dev.routemyagent%2Fmodel-helper/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": {
    "routemyagent-model-helper": {
      "type": "http",
      "url": "https://routemyagent.dev/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.9.2LatestOct 14, 2026

Score

67% 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
  • 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.