Auth behavior: - If `REQUESTREPO_TOKEN` is set, it is used. - Otherwise a new session is created, optionally with `REQUESTREPO_ADMIN_TOKEN`.
Auth behavior: - If REQUESTREPO_TOKEN is set, it is used. - Otherwise a new session is created, optionally with REQUESTREPO_ADMIN_TOKEN. Exposed over MCP by the requestrepo mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
Confirm — gated mutations (confirm=true)session_info — list_requestswait_for_request — delete_requestdelete_all_requests — share_requestget_shared_request — list_dnsadd_dns — remove_dnsupdate_dns — list_filesget_file — set_fileupdate_files — pingCodex — Autostart note: - Codex starts stdio servers automatically. - If startup fails, register with an absolute executable path:Cursor — The Cursor tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 3 environment variables: REQUESTREPO_TOKEN, REQUESTREPO_ADMIN_TOKEN, REQUESTREPO_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Requestrepo MCP's toolset — Confirm, session_info, wait_for_request and 8 more — is a fair guide to whether it matches your workflow. It is maintained by hofill; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Confirm | gated mutations (confirm=true) |
| session_info | list_requests |
| wait_for_request | delete_request |
| delete_all_requests | share_request |
| get_shared_request | list_dns |
| add_dns | remove_dns |
| update_dns | list_files |
| get_file | set_file |
| update_files | ping |
| Codex | Autostart note: - Codex starts stdio servers automatically. - If startup fails, register with an absolute executable path: |
| Cursor | The Cursor tool exposed by this server. |
### Claude Code / Claude Desktop
```json
{
"mcpServers": {
"requestrepo": {
"command": "requestrepo-mcp",
"args": ["--transport", "stdio"],
"env": {
"REQUESTREPO_TOKEN": "your-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| REQUESTREPO_TOKEN | Credential the server authenticates with. | Yes |
| REQUESTREPO_ADMIN_TOKEN | Credential the server authenticates with. | Yes |
| REQUESTREPO_HOST | Endpoint or connection string the server talks to. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.