Alimenter votre agent
L'URL propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
https://api.tenpace.com/v1/review-router/mcpLe bouton Claude ci-dessus ouvre Claude avec le nom et l'URL préremplis. Il vous reste à confirmer sur place.
claude mcp add --transport http io.github.tenpace-app-review-router https://api.tenpace.com/v1/review-router/mcpRun in a terminal.
{ "mcpServers": { "io.github.tenpace-app-review-router": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.tenpace.com/v1/review-router/mcp" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
Create a GitHub-to-Slack Review Router connection from a workflow or AI coding session. The Action produces one short-lived browser link. Open it and sign in to Tenpace to claim and lock the exact repository, Slack destination, routing preset, and reviewer mention policy.
The Action never receives GitHub App credentials, Slack OAuth tokens, provider authorization codes, or the human's Tenpace session.
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
Create .github/workflows/review-router-setup.yml:
name: Set up Review Router
on:
workflow_dispatch:
permissions:
contents: read
id-token: write
jobs:
setup:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: tenpace-app/review-router-setup@v1
with:
slack-channel: pull-requests
preset: repo-watch
reviewer-mentions: all
Run the workflow. The same GitHub user who started it opens the Continue Review Router setup link in the job summary, signs in to Tenpace, completes the GitHub and Slack steps, and lets the page reconcile and verify the route with a real Slack delivery.
Instead of inputs, commit .tenpace/review-router.yml:
version: 1
route:
slack-channel: pull-requests
preset: repo-watch
reviewer-mentions: all
You can also set slack-workspace when the Tenpace team has more than one connected workspace. Explicit Action inputs override the file.
slack-channel: Slack channel name, with or without #. Required unless present in the config file.slack-workspace: Optional exact workspace name, Slack team ID, or Tenpace workspace ID.preset: repo-watch, full-coverage, or team-activity. Default: repo-watch.reviewer-mentions: all, connected-only, or none. Default: all.config: Config path. Default: .tenpace/review-router.yml.setup-id: Public setup-session ID.setup-url: Short-lived human authorization URL.status: Initial status, normally awaiting_human.The machine setup token is masked and deliberately not exposed as an Action output. The displayed URL contains no claim secret: it is bound to the GitHub actor in the signed OIDC token, and that same GitHub user must open it. The browser flow can finish setup without putting a secret into another workflow step.
GitHub Actions OIDC proves the repository and actor for the workflow run. It does not grant provider authority. Tenpace verifies the OIDC issuer, signature, audience, time window, repository and owner IDs, actor ID, subject, and repository binding. Action URLs contain no claim secret and can only be claimed by that GitHub actor.
The server creates an inert intent. A Tenpace user signs in and claims the setup URL, which atomically locks that exact intent version. The machine token cannot edit after claim; the person who claimed the setup can edit it, and saving creates and locks the new version in the same action. Provider OAuth stays in the browser and encrypted credentials stay on Tenpace.
Setup creation and application are idempotent. The final check sends one message through the same Slack delivery path used for pull request notifications.
See SECURITY.md for reporting and operational details.
Read AGENTS.md before automating setup. Canonical machine-readable surfaces:
No AI-discovery convention is universal, so the same workflow is described in the Action metadata, README, AGENTS.md, linked HTML/Markdown docs, OpenAPI, MCP, and well-known descriptor.
The remote MCP server is also published to the official MCP Registry as
io.github.tenpace-app/review-router
MIT
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
{ "mcpServers": { "io.github.tenpace-app-review-router": { "url": "https://api.tenpace.com/v1/review-router/mcp", "headers": {} } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration http pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Tenpace Review Router est accessible via HTTP.
Dernière vérification : 2026-11-10. Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
