Conga MCP connector
The Conga connector brings Conga users, roles, permission groups and user groups to Claude, ChatGPT, Cursor and Microsoft Copilot through one endpoint, with each person signed in as themselves and every action logged.
- App credentials
- Free 14-day trial
- No credit card
Which Conga users have the admin role?
Working in Conga with Elaichi
-
List all Conga user management users
-
Get single Conga user management user by ID
-
List all Conga templates downloads
How to connect Conga to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Conga 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.
Conga MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Conga 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. The plugin directory lives at chatgpt.com/plugins.
Conga 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.
Conga MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Conga 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.
What teams do with Conga through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Conga is logged.
-
Sales Operations
Set up a new rep in Conga
Create the user, give them the right role, and send the welcome email in one ask instead of clicking through three screens.
-
IT
Load a whole cohort of users at once
Hand over the list of new hires and have the users created or updated in bulk, with the roles and permission groups applied together.
-
Security
Check who holds which Conga role
Ask for every user with an admin role, or every member of a permission group, and get the list back before the quarterly review.
-
Legal Operations
Build a user group for the contracts team
Create the group, pull in the right people, and confirm who is in it when the team changes.
-
Revenue Operations
See which templates are being downloaded
List the template downloads to find out which quote and contract templates reps actually use and which ones nobody touches.
-
IT
Bring back a user who was removed
Restore a deleted Conga user, or clone an existing one, so a returning colleague or a new teammate starts with the right setup.
Try asking
- “Which Conga users have the admin role?”
- “Create a Conga user for Priya and send her welcome email”
- “List Conga user groups with no members”
What connecting Conga gets you
6 screens from Elaichi, each doing one job for your Conga account.
Ask Elaichi to work across your apps.
Which Conga users have the admin role?
Create a Conga user for Priya and send her welcome email
List Conga user groups with no members
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Conga users in plain language.
Get answers from live Conga users, roles and permission groups, no screens to click through.
Copy the endpoint
AI apps
One endpoint, every client, no shared key.
Claude, ChatGPT and Cursor reach Conga through one governed endpoint, each person signed in.
Tool catalog
1801 Conga tools, no code to write.
Users, roles, permission groups, user groups and template downloads, covered without custom code.
Toolboxes
Every team gets its own Conga toolbox.
Sales operations, IT and legal operations each see only the Conga tools they need.
Shared connections
Share Conga access, never the credential.
One person connects Conga, teammates work through it without seeing the app credentials.
Audit log
Know who changed which Conga user.
Every user created, role updated or group changed lands in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Conga digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Conga
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 Jake Morgan
Approve Deny -
Post the digest
Conga
Queued
Workflows
A schedule starts the work, a person approves.
New Conga users are fetched, grouped, drafted into a digest, approved, then posted back.
Conga health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Roles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Sales Ops 34%
IT Admin 27%
Legal 21%
Revenue Ops 18%
Collections and dashboards
Conga health, computed on a schedule, no model.
Users created over 14 days, broken down by team, refreshed without anyone asking.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Conga
All three can connect Conga 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 Conga tools | Allow or restrict single Conga 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 Conga 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 | Free for one person; $15 per user per month on Gold. | 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.
Conga tools for your AI agents
1801 tools are ready to call through Elaichi's MCP endpoint the moment you connect Conga, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 232 of 1801 Conga tools here. Connect Conga and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Conga to Claude?
Connect Conga in Elaichi first, by entering your Conga app credentials; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Conga is ready to use.
Does Conga work with ChatGPT and Cursor as well as Claude?
Yes. Once Conga is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Conga once and every client picks it up.
What can an AI agent actually do with my Conga data?
It can create, update, clone, restore or delete Conga users, set their roles and permission groups, build user groups, send welcome emails, and list template downloads. You ask in plain language, such as "give Priya the sales user role in Conga", and the agent does it inside your own Conga access. Short, concrete asks work better than long sentences.
Does connecting Conga give the AI access to every user and role?
No. Every call into Conga runs as the person who signed in, so the agent can only see and change what that person can already see and change in Conga. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Conga?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Conga users, or bulk updating permission groups, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Conga connection when someone leaves?
Offboarding that person in Elaichi ends their access to Conga through every client at once. A shared Conga connection keeps working for everyone else on the team. If you disconnect Conga in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Conga MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Conga 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, Microsoft Copilot, 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 Conga?
Yes. Both let Claude, ChatGPT or Cursor use Conga. 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 Conga call.
How is Elaichi different from Composio for Conga?
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 Conga: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Conga in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot