Skip to main content

​
Overview

Custom integrations let you extend Gitar with your own tools. Alongside the built-in integrations (Jira, Linear, Slack), you can register an MCP server and Gitar’s rules and agents can use it while reviewing pull requests and running automations.

Any Remote MCP Server

Connect any MCP server reachable over https, including one you built yourself

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. Contact your Gitar account team to have it enabled for your organization.

​
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. Integrations saved before instructions-only was retired still load. Give one 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-....We store the value securely and never read 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

  • Enable / disable - toggle an integration off to remove it from agents without deleting its configuration.
  • Edit - update the URL, its credentials, or its allowed tools from the integration card. A card narrowed to no tools is badged No tools allowed and that server is not started.
  • Delete - remove the integration entirely. Deletion stays available even if the Enterprise entitlement is later removed.

​
Frequently Asked Questions

​
What transports are supported?

Remote MCP servers over https, whether they speak Streamable HTTP or SSE. 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?

Nothing of yours beyond the headers it sends. It cannot read the repository checkout, Gitar’s own configuration, or anything belonging to another integration. Network access is unrestricted, because an MCP server exists to talk to an external system. Only register servers you trust with your own data.

​
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 cannot list your server’s tools for you yet, so take the names from the server’s own documentation. A discovery button is on the roadmap.

​
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.