Review Router MCP

Ask your assistant to set up PR routing.

Connect a GitHub repository to the right Slack channel from your coding session. Your assistant proposes the route. You confirm the exact plan and connect GitHub and Slack in your browser.

Before you start

• A GitHub repository and permission to install the GitHub App for it.
• A Slack workspace where you can authorize the app, or someone who can complete that step.
• A Tenpace account and active workspace access. Try 30 days free with a card, then $5 per developer/month or $50 per developer/year. MCP is included.

1. Connect your MCP client

The hosted server uses Streamable HTTP. There is nothing to host and no provider token to paste into your assistant.

Endpoint: https://api.tenpace.com/v1/review-router/mcp

Claude Code

Run this in your terminal, then use /mcp in Claude Code to check the connection.

claude mcp add --transport http review-router https://api.tenpace.com/v1/review-router/mcp

Cursor

Add this entry to .cursor/mcp.json in your project, or merge it into an existing configuration. Enable Review Router in the client's MCP settings.

{
  "mcpServers": {
    "review-router": {
      "url": "https://api.tenpace.com/v1/review-router/mcp"
    }
  }
}

Client interfaces can change. Claude Code documentation · Cursor documentation

2. Ask for the route you want

Replace OWNER/REPO with your repository. Name the Slack workspace too if you use more than one.

Set up Review Router for OWNER/REPO in #code-reviews, with reviewer mentions.

The assistant returns a short-lived setup link. Open it, sign in, check the repository, workspace, channel and reviewer policy, and connect the providers. Claiming the plan locks it against further agent edits; you can still change it in the browser. If billing is required, an owner completes secure checkout. Never give card details to an assistant. Cancel before the trial ends to avoid the automatic renewal charge.

3. Verify it, then route a real PR

Complete the browser checklist. Review Router applies the route and sends a verification message. Then open or mark a matching pull request ready for review and check that its Slack message arrives in the intended channel.

A test message confirms the connection; your first real routed PR confirms the workflow. Explore the illustrated workflow demo or learn how notification rules work.

What the five tools do

• start_review_router_setup: propose a route and return the browser handoff.
• get_review_router_setup_status: read progress and the next human step.
• preview_review_router_setup: inspect the current locked plan.
• apply_review_router_setup: apply the human-confirmed route.
• send_review_router_test: send one idempotent verification message.

GitHub and Slack credentials stay server-side. The assistant's session-scoped setup token is still a secret: keep it out of commits, screenshots and public logs. See the full setup and authorization contract.

If setup stops

• 401 at connection: check the full endpoint above. The shorter /mcp address is reserved for a separate directory gateway.
• Waiting for a person: open the setup link and finish the listed sign-in/provider step. Do not paste provider credentials into chat.
• Private Slack channel: invite the Review Router app to that channel.
• Expired link: ask for a new setup. Unclaimed links expire after one hour.
• Test works but no PR: check repository access, draft status and the channel's routing filters.

Try the free audit first

Check a public repository without signing up. For private repositories, use the Audit Action inside your repository; it sends no repository data to Tenpace by default.

Official registry entry · Public setup repository