GitHub MCP connector
The GitHub connector brings repositories, issues, pull requests, branches, commits and releases to Claude, ChatGPT, Cursor and any MCP client, so each person works in GitHub as themselves with every action logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
46 tools
How to connect
How to connect GitHub to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect GitHub once
-
Open Connections, choose Add connection, and pick GitHub.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in GitHub. GitHub's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
GitHub MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
GitHub MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
GitHub MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect GitHub to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with GitHub through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Open a pull request from a plain request
Describe the change you want and the agent creates the branch, updates the file and opens the pull request for review. You stay in the conversation while the work lands in GitHub under your name.
-
Engineering
Answer review comments without switching tabs
Reply to a reviewer's note on a pull request, or add your own comments to a pending review, while you are still reading the diff in chat.
-
Product
Turn a customer request into a filed issue
Explain the request and the agent opens the issue with the right type and fields, or updates the existing one so nothing is filed twice.
-
Support
Check whether a fix shipped in the latest release
Ask what the latest release contains and which commits went into it before you tell a customer their problem is solved.
-
Docs
Fix a typo and send it up for review
Correct a file in the docs folder, open the pull request and leave a note for the owner, all from one request.
-
Engineering management
See what changed on a branch this week
List recent commits, read the details of any one of them, and find out which team members were involved before standup.
Try asking
- “Open a pull request that fixes the typo in README”
- “What went into the latest release of the api repo?”
- “File an issue for the login timeout bug with the bug type”
Native MCP
Why connect GitHub's MCP server through Elaichi
GitHub builds and runs this MCP server. Elaichi sits in front of it, so GitHub's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to GitHub's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT and Cursor reach GitHub's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds GitHub's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own GitHub sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches GitHub's server. By default, a tool GitHub does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to GitHub
GitHub builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the GitHub team.
Compare
Elaichi vs Zapier MCP vs Composio for GitHub
All three can connect GitHub to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over GitHub tools | Allow or restrict single GitHub tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per GitHub call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
GitHub tools for your AI agents
46 tools are ready to call through Elaichi's MCP endpoint the moment you connect GitHub, governed by the same roles, restrictions, and audit log as everything else in Elaichi. GitHub builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting GitHub gets you
6 screens from the product, each doing one job for your GitHub account.
The agent
Ask GitHub questions in plain language.
What changed on main this week and which release carries it, answered from live commits.
- pull requests
- issues
- branches
- commits
Ask Elaichi to work across your apps.
Open a pull request that fixes the typo in README
What went into the latest release of the api repo?
File an issue for the login timeout bug with the bug type
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint for Claude, ChatGPT and Cursor.
Connect GitHub once and every MCP client signs in over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
46 GitHub tools, no code to write.
Issues, pull requests, branches, commits, files and releases, covered without an engineer building anything.
- Add review comment to the requester's latest pending pull request review
- Add comment to issue or pull request
- Add reply to pull request comment
- Create branch
ElaichiToolsToolboxes
Every team gets its own GitHub toolbox.
Engineering, Product and Support each see only the GitHub tools scoped to their work.
- Engineering
- Product
- Support
- Docs
ElaichiToolboxesShared connections
Teammates work in GitHub without the token.
One person connects GitHub, shares it with teams, and nobody else handles a credential.
- Core Platform
- Mobile
- Open Source
- Docs
ElaichiConnectionsAudit log
Know who touched which repository and when.
Every pull request, comment and file change is logged with the person who made it.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns GitHub issues into digests.
Every Monday new issues are fetched, grouped, drafted into a digest, approved, then posted to GitHub.
GitHub digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch pull requests
GitHub
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
GitHub
Queued
Collections and dashboards
GitHub health, computed on a schedule, no model.
Pull requests opened, issues filed and commits per team, refreshed without anyone asking.
GitHub health
Refreshed 4 minutes ago · every 15 minutes · from the pull requests collection
Pull requests
1,284 ↓ 12%
Issues
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Pull requests created
Last 14 days
By team
Share of activity
Core Platform 34%
Mobile 27%
Open Source 21%
Docs 18%
FAQ
Frequently asked questions
How do I connect GitHub to Claude?
In Elaichi, choose GitHub and sign in to your GitHub account in the window that opens, then approve access. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and GitHub is ready.
Does GitHub work with ChatGPT and Cursor as well as Claude?
Yes. Once GitHub is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect GitHub once and every client you use picks it up.
What can an AI agent actually do with my GitHub data?
With GitHub connected, an agent can read files, commits, branches, issues, pull requests, releases and teams, and it can act: open an issue, update one, create a branch, change a file, open a pull request, add comments and reply to reviews. Short, concrete asks work best, such as "open a pull request that fixes the typo in README" rather than a long paragraph of instructions.
Does connecting GitHub give the AI access to every repository?
No. Access follows the person who signed in to GitHub, so an agent sees only the repositories, issues and pull requests that person can already see, and private repositories they are not a member of stay out of reach. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what GitHub itself allows that person.
Can I stop an agent from deleting or changing things in GitHub?
Yes. Restrictions in Elaichi work per action, so you can block deleting files, creating repositories or changing files while still allowing issues and pull requests to be read and commented on. A restricted action is left out of the AI client's tool list for GitHub entirely and cannot be called, whatever the prompt says.
What happens to a GitHub connection when someone leaves?
Offboarding a person in Elaichi ends their access to GitHub through every client at once, including Claude, ChatGPT and Cursor. If they had shared a GitHub connection with a team, it keeps working for everyone else. Disconnecting GitHub once in Elaichi removes it from every client, with no per-client cleanup.
Does the GitHub MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. GitHub is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for GitHub?
Yes. Both let Claude, ChatGPT or Cursor use GitHub. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every GitHub call.
How is Elaichi different from Composio for GitHub?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to GitHub: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put GitHub in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.