Skip to main content

​
Overview

Register your own MCP server and Gitar’s rules and agents get its tools while reviewing pull requests and running automations, alongside the built-in integrations like Jira, Linear, and Slack.

Remote MCP Servers

Connect a server that supports Streamable HTTP over HTTPS.

Skills for Guidance

For instructions with no server, commit a skill under .gitar/skills/.

Use in Rules

Name the integration in a rule and the agent picks it up.

Secrets

API tokens are stored securely, per organization.
Custom integrations are an Enterprise feature, with unlimited MCP connections.

​
Connect engineering knowledge

Custom integrations make internal documentation and enterprise tools available to Gitar’s agents and rules. They extend the knowledge sources Gitar can consult during a review. Configure the tools and credentials each connection needs. A documentation search tool can supply a design decision, while a workflow can use an issue tracker tool to record the follow-up work.

​
How It Works

A custom integration is an MCP server. Give Gitar its https URL and the agent gets your server’s tools. The URL is the only thing you supply. The name and description come from the endpoint host, so there is nothing else to fill in. For guidance with no server, commit a repo skill instead. A skill is versioned with the code it describes, where an org-level setting is not. An integration saved without an endpoint, from before the URL became required, still loads. Give it an endpoint or delete it.

​
Add a Custom Integration

1

Open the Integrations settings

In the Gitar dashboard, go to your organization’s Settings → Integrations, find Custom MCP servers at the bottom, and click Add MCP server.
2

Point Gitar at your MCP server

Enter the MCP server URL, for example https://mcp.example.com/mcp. It must use https and name a public host. A URL carrying credentials, a query string, a bare IP, or an internal hostname is rejected, and the dialog says why.The name comes from the host, so https://mcp.acme.com/mcp becomes Acme. Tool descriptions come from your server.
3

Add credentials

A credential reaches your server as an HTTP header. Leave Authentication on None if the server needs none, or pick Auth header and fill in one row.A row is a header name and its value. It starts as Authorization, and the value is whatever your server expects there, prefix included, so a bearer token goes in as Bearer sk-....Gitar stores the value securely and never reads it back into the form. Editing a server shows it as Unchanged, so type a new one only to rotate it. Never put a credential in the URL.
4

Narrow the allowed tools (optional)

Leave Allowed Tools empty and the agent gets every tool your server advertises. Name tools there to narrow it to those, spelled exactly as your server advertises them.Narrowing is how you withhold a tool. The dialog warns before you save a server narrowed to nothing.
5

Create the integration

Click Create. The integration appears on your Integrations page and can be enabled or disabled at any time.

​
Using a Custom Integration in Rules

Once an integration is enabled it is available to every rule. Name it in the rule and the agent uses it, the same way it handles Jira, Linear, or Slack:
Plain language is enough. Use the integration’s name and say what you want. See Repository Rules for the full rule format, and Skills for the no-server alternative.

​
Managing Integrations

​
Frequently Asked Questions

​
What transports are supported?

Remote MCP servers must support Streamable HTTP over HTTPS. JSON and streaming responses work. Legacy servers with separate SSE and message endpoints are unsupported. Locally-run servers are not supported. A server that only ships as a local package needs to be hosted at a URL Gitar can reach.

​
Where are my secrets stored?

Securely, scoped to your organization and to the server you added them to. They are not written to rule files or your repository, and the model never sees them. Two of your servers can hold different credentials on the same header without either receiving the other’s.

​
What can my MCP server access?

The server receives its configured authentication headers and the arguments Gitar sends when calling its tools. Those arguments can include repository content or information Gitar extracts from a pull request. The server has no direct access to the repository checkout or Gitar’s own configuration. It does not receive another integration’s credentials. Register only servers trusted to receive repository data. Gitar connects to public HTTPS endpoints, and the server’s hosting environment controls its own outbound access.

​
Can tools receive information Gitar has extracted or assessed?

Yes. A rule or skill can instruct Gitar to gather information and pass it as tool arguments. For example, a rule can ask Gitar to extract a ticket reference from the pull request description and assess whether the diff changes CI configuration, then pass those values to a risk-assessment tool. The returned risk level can guide the agent’s next steps.

​
Can auto-approve criteria call an MCP tool?

No. The auto-approve evaluator cannot call MCP tools, and results from earlier integration calls are not automatically passed into its decision. Naming a risk-assessment tool in auto-approve criteria does not make its result an approval condition.

​
Can I limit which tools a server exposes?

Yes. An empty Allowed Tools list gives the agent every tool your server advertises. Name tools there to narrow it to those. Gitar does not list your server’s tools for you, so take the names from the server’s own documentation.

​
Who can create custom integrations?

Enterprise plan, organization administrators only. Deleting stays available even if the entitlement is later removed, so an org can always clean up.