Model Context Protocol · built in
Your roadmap, in your agent's context.
CatchLoop ships a first-party MCP server, maintained with the product. Point an AI agent at your board and it can read what your users want most, import feedback it gathered elsewhere, and move requests forward, right from the editor you already work in.
Ask what to build next
real accounts, not noise
Your agent queries the most-wanted requests, ranked by the votes of your customers' accounts. "What are our five most-wanted open requests?" is one prompt away. The data your prioritization already runs on, now readable by the tools that draft your specs.
Import it, then move it forward
no glue code, no connector
Ask your agent to pull the relevant threads from Intercom, support or sales calls and drop them onto the board. CatchLoop never touches those tools; the agent brings the data. Import is free, so your whole backlog can land on day one. A status change emails nobody: everyone who voted hears once, when you publish the changelog entry that ships their request.
Authenticated and scoped
one workspace key
One workspace key authenticates every call, over TLS, and it is the only credential involved: no OAuth dance, no session cookie, nothing to revoke in three places. Reading, importing and changing a request's status are all free. Every call is scoped to the workspace that key belongs to, so an agent can never reach another tenant's data.
Connect in two minutes
Three steps, nothing to install.
-
01
Sign up or sign in
Open a free workspace with your email: one link, no password. Already have one? The same page signs you in.
Open your portal, free -
02
Copy your API key
Your workspace key is on the Integration page of your dashboard, under MCP server. Export it as
Open the Integration pageCATCHLOOP_API_KEY, so no config file holds it. -
03
Paste the snippet
One entry for your client, below. Then ask it: "What are our five most-wanted open requests?"
Read the MCP docs
claude mcp add --transport http catchloop https://mcp.catchloop.co \
--header "Authorization: Bearer $CATCHLOOP_API_KEY"{
"mcpServers": {
"catchloop": {
"url": "https://mcp.catchloop.co",
"headers": {
"Authorization": "Bearer ${env:CATCHLOOP_API_KEY}"
}
}
}
}{
"inputs": [
{
"type": "promptString",
"id": "catchloop-api-key",
"description": "CatchLoop workspace API key",
"password": true
}
],
"servers": {
"catchloop": {
"type": "http",
"url": "https://mcp.catchloop.co",
"headers": {
"Authorization": "Bearer ${input:catchloop-api-key}"
}
}
}
}{
"mcpServers": {
"catchloop": {
"serverUrl": "https://mcp.catchloop.co",
"headers": {
"Authorization": "Bearer ${env:CATCHLOOP_API_KEY}"
}
}
}
}Their custom connectors sign in with OAuth, which CatchLoop does not offer yet. If your organization has Anthropic's request headers beta, add a custom connector with the server URL, choose No sign-in, and add an authorization header whose value is Bearer, a space, then your key.
Four tools
What your agent can call.
list_requests
Reads the most-wanted requests, ranked by the votes of your customers' accounts, from every status or only the ones you name.
create_request
Records one request from feedback gathered elsewhere, such as a support ticket or a sales call.
import_requests
Imports up to 50 requests in one call, with their past vote totals, original dates and statuses.
set_request_status
Moves a request to another status. It emails nobody: the people who asked hear once, when you publish the changelog entry.
Parameters, status values and how the votes are counted are in the MCP docs.
Where the roadmap lives
The roadmap stops being a place you visit.
CatchLoop exposes the board to your agent, inside the workflow you already have. Prioritization stops being something you go and look up, and becomes context the tools that draft your specs can act on.
Give your agent the roadmap.
Free, status changes included, with no volume caps. Your workspace key is on the Integration page.