APIGit MCP Server

APIGit has a Model Context Protocol server for your account. An AI agent connected to it reads what you can read on APIGit: repositories, OpenAPI files at any branch, tag or commit, pull requests, published documents, mock servers and your organization’s governance rules. With the write tools it can also propose a change on a branch and open a pull request for you to review.

Address	Tools
`https://app.apigit.com/api/v1/mcp/readonly`	The read tools only. Nothing can change.
`https://app.apigit.com/api/v1/mcp`	The read tools and the write tools

This page is about the server for your account. To let an agent read one published API document, with no account at all for a public document, see Use a published API document with AI agents.

Connect

A coding agent in a terminal

Install the APIGit CLI, sign in, and run this in your project:


apigit agent setup                    # Claude Code; or --client cursor, --client vscode

The agent then starts apigit mcp, which uses your CLI login, so no token is written to a configuration file. It adds tools for the OpenAPI files in your working directory (lint, bundle, outline) to the tools below, and it is read-only unless you run apigit agent setup --write.

A chat application or a one-click connector

Add https://app.apigit.com/api/v1/mcp/readonly (or /api/v1/mcp) as a remote MCP server. The application opens an APIGit page in your browser, where you see:

the name the application gives itself, marked as not verified, and the address it will return to
what it asks for, with the permission to change things set apart
the account you are signed in with

The page where you authorize an application

Click Authorize to connect or Deny to refuse. If you did not start the sign-in yourself, choose Deny.

A client that sends a header

Create a personal access token and send it as Authorization: token <your token>. A token of the kind CLI and automation reads everything below; a Git and repository API token reads repositories but not your plan or your organization’s rules.

Read tools

Tool	Returns
`get_me`	The signed-in user and plan
`search_repos`	Repositories you can read, by keyword
`list_spec_files`	The OpenAPI files and pages of a repository at a ref
`get_spec_outline`	Operations and schema names of the OpenAPI files, without bodies
`get_spec_operation`	One operation: parameters, request body, responses, examples
`get_spec_schema`	One schema with its fields
`get_file`	A file of the repository, or a range of its lines
`diff_spec`	What changed in an OpenAPI file between two refs, breaking changes first
`list_spec_changes`	The commits that changed a file
`get_spec_change`	What one commit changed in an OpenAPI file
`list_pull_requests`, `get_pull_request`	Pull requests and one pull request with its changed files
`list_published_docs`, `get_published_doc`	Published document versions and their addresses
`list_mocks`, `get_mock`, `get_mock_logs`	Mock servers and their recent requests
`get_governance_rules`	The governance rulesets that apply to a repository of your organization

A ref is a branch, a tag or a commit; without one the default branch is used. A repository you cannot read looks the same as one that does not exist.

Write tools

Tool	Does
`create_branch`	Creates a branch from a ref
`commit_files`	One commit that creates, updates or deletes up to 50 files on a branch
`patch_file`	Exact search-and-replace edits in one file, all or nothing, as one commit
`open_pull_request`	Opens a pull request from a branch
`publish_doc`, `unpublish_doc`	Publishes, moves or removes a document version
`publish_mock`, `delete_mock`	Publishes, moves or deletes a mock server

The write tools keep a person in the loop:

They never commit to the default branch or a protected branch, and there is no merge tool. You review and merge the pull request in APIGit.
They never make a document public and never turn a mock server’s access control off. Do those in the application.
Each tool is marked as changing or destructive, so your agent host can ask you before it runs one.
A call needs the permission the same action needs in the application, and a token or sign-in that allows writing.

Choose the tools an agent sees

Add ?toolsets= to the address with any of context, specs, pulls, docs, mocks, governance, changes and publish, separated by commas. For example …/api/v1/mcp?toolsets=specs,pulls lists only the tools for OpenAPI files and pull requests. changes and publish are the write tools.

Disconnect an application

Open Settings › Personal Access Token. Authorized applications lists every application you approved, with what it may do; Revoke ends its access at once. A token you created yourself is deleted in the list above it.

Limits

300 requests a minute per user.
A result is at most about 10,000 tokens; a longer one ends with a line saying it was cut.
A sign-in approved on the consent page works for the MCP server only, not for git or the rest of the API.