Where do I find my MCP URL?

On the MCP tab of your project. Every project has its own endpoint ending in the project slug, which is why the tools need no project argument and cannot reach a project you did not configure.

Is it safe to commit the config to my repository?

Yes. There is no token in it — only a URL — because access runs through OAuth in the browser. That is the main practical difference from MCP servers that ask you to paste an API key into a JSON file.

Why can my agent not change a status?

Because the status tool is only registered for owners and admins. If your role is member it was never offered, so the agent does not plan around a call it would be refused. Ask an owner to change your role.

What are the rate limits?

Three hundred calls an hour per person and six hundred per hour per project. That is deliberately generous, because an agent working through a list of reports in one burst is exactly the intended use.

MCP · Setup

One URL, one approval. No token anywhere.

The whole configuration is an HTTP endpoint. There is nothing to generate, nothing to rotate and nothing to keep out of version control, because the authorisation happens in your browser rather than in a file.

Get your endpointNo credit card required.

Step 1

Copy your project endpoint

It is on the MCP tab of your project, and it ends in the project slug. The project lives in the URL rather than in a credential, which is what lets the tools take no project argument at all.

your endpoint

https://userwants.app/api/mcp/your-project-slug

Step 2

Add it to your editor

Every HTTP MCP client takes the same object. What changes is which file reads it.

mcp config

{
  "mcpServers": {
    "userwants": {
      "type": "http",
      "url": "https://userwants.app/api/mcp/your-project-slug"
    }
  }
}

Claude Code: .mcp.json in the project root, so it travels with the repository and every contributor gets it. Or add it from the terminal in one line.
Cursor: .cursor/mcp.json inside the project, or ~/.cursor/mcp.json to make it available in every project you open.
VS Code and Zed: Both speak HTTP MCP and take the same URL, each nested under its own key. Check your editor MCP documentation for the exact shape.

claude code, from the terminal

claude mcp add --transport http userwants \
  https://userwants.app/api/mcp/your-project-slug

Step 3

Approve it once in the browser

The first connection opens a browser and asks you to approve the editor. After that the agent acts as you: it sees the projects you belong to, and it can change a status only if your role already allows it — the same rule the dashboard applies. MCP access is a paid feature, and the plan that counts is the project owner’s. The complete reference, including refs and rate limits, is in the MCP docs.

FAQ

Questions

Where do I find my MCP URL?: On the MCP tab of your project. Every project has its own endpoint ending in the project slug, which is why the tools need no project argument and cannot reach a project you did not configure.
Is it safe to commit the config to my repository?: Yes. There is no token in it — only a URL — because access runs through OAuth in the browser. That is the main practical difference from MCP servers that ask you to paste an API key into a JSON file.
Why can my agent not change a status?: Because the status tool is only registered for owners and admins. If your role is member it was never offered, so the agent does not plan around a call it would be refused. Ask an owner to change your role.
What are the rate limits?: Three hundred calls an hour per person and six hundred per hour per project. That is deliberately generous, because an agent working through a list of reports in one burst is exactly the intended use.

Connect your editor in about a minute.

Copy the endpoint from the MCP tab, paste it into your config, approve it once.

Start free Read the docs