Skip to main content
Autter exposes an MCP server so a coding agent such as Claude Code, Cursor, or another MCP-capable client can act on Autter data directly, without a person relaying it through the dashboard.
MCP is a machine interface for coding agents. If you want to browse reviews yourself, use the Autter platform. If you want line-level AI authorship in Git, use the Autter CLI.

​
Why connect an agent

A coding agent that can reach Autter over MCP can:
  • read a pull request’s review findings, including the file, line, and a ready-to-use fix suggestion
  • reply to a review comment and mark it resolved once it fixes the issue
  • re-run the review after pushing changes
  • check whether a package it is about to add has known vulnerabilities
  • look up blast radius and test coverage before editing a file
  • ask a natural-language question about the codebase
  • start or check a codebase security scan
  • read and add team conventions (“learnings”) so future code passes review the first time
This closes the loop between “Autter found a problem” and “the agent fixed it,” instead of a person copying findings between the pull request and the agent.

Connect your agent

Create an access token and connect Claude Code, Cursor, or another MCP client.

​
How it works

The MCP server is part of the Autter platform. A client connects with an HTTP request, authenticated with an Autter personal access token, and calls tools scoped to your organization.
1

Create an access token

Create a personal access token in Org Settings → Access Tokens. Restrict it to MCP scopes if you only want agent access, not CLI login.
2

Point your MCP client at Autter

Configure your client with the Autter MCP endpoint and the token as a bearer credential. See Connect your agent for exact client configuration.
3

Call a tool

Every tool operates on the token’s organization. Most tools accept a repo argument as either the full owner/repo name or the short repository name.
Every tool call is authenticated by the token, scoped to one organization, and logged to that organization’s access token activity so you can see what an agent did and when.

​
Available tools

query_codebase answers from generated repository documentation. Generate docs for a repository from its Wiki tab before an agent relies on this tool for that repository. See Repository wiki.

​
Access and scopes

A token used with MCP can be unrestricted, meaning it works for both CLI login and every MCP tool, or restricted to specific scopes so an agent can only do what you allow: A token restricted to MCP scopes cannot sign in to the Autter CLI. Create an unrestricted token if you need CLI login and MCP access on the same token.
Treat an Autter access token like a password. Give an agent only the scopes it needs, and revoke a token in Org Settings → Access Tokens if it is exposed.

​
Usage limits

Each token has its own request budget so a runaway agent loop cannot exhaust the connection: 60 read calls, 10 write calls, and 6 query_codebase calls per minute. A tool call that exceeds its budget returns a rate-limited error; wait a few seconds and retry. Codebase scans still count toward your plan’s included scan volume when started with trigger_scan, the same as starting one from the dashboard.

​
Next steps

Connect your agent

Create a token and configure Claude Code, Cursor, or another MCP client.

Manage access tokens

Review, scope, and revoke tokens for the CLI and MCP.