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

Source: https://elaichi.ai/connectors/conga/

## Facts

| | |
| --- | --- |
| Application | Conga |
| Category | CRM |
| AI tools | 1801 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Conga is connected

- 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

## Connect Conga in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Conga.
2. Optionally set Share with, then press Connect.
3. Paste your Conga app credentials. Conga authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Conga tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Conga MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Conga MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Conga tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Conga through Elaichi

### Set up a new rep in Conga

Sales Operations. Create the user, give them the right role, and send the welcome email in one ask instead of clicking through three screens.

### Load a whole cohort of users at once

IT. Hand over the list of new hires and have the users created or updated in bulk, with the roles and permission groups applied together.

### Check who holds which Conga role

Security. Ask for every user with an admin role, or every member of a permission group, and get the list back before the quarterly review.

### Build a user group for the contracts team

Legal Operations. Create the group, pull in the right people, and confirm who is in it when the team changes.

### See which templates are being downloaded

Revenue Operations. List the template downloads to find out which quote and contract templates reps actually use and which ones nobody touches.

### Bring back a user who was removed

IT. Restore a deleted Conga user, or clone an existing one, so a returning colleague or a new teammate starts with the right setup.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Conga connection?

Yes. One person connects Conga in Elaichi with the app credentials and shares the connection with a team, and nobody else ever handles the credential. Each teammate still signs in as themselves, so the audit log names the person who created or changed a Conga user, not the connection.

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

## All 1801 Conga tools

Every tool below is callable through https://api.elaichi.ai/mcp once Conga is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Conga user management users** (List). List all Conga Platform users that meet the given criteria. Returns: UserName, Id, PermissionGroups. Filter with criteria (e.g. IsActive = 'true'; the criteria field must be indexed) and sort with sortField and sortDirection.
- **Create a Conga user management user** (Create). Create a new Conga Platform user. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Supply the user model data in the body.
- **Conga user management users bulk create** (Create). Create multiple Conga Platform users with one request. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Existing users return their id with a validation error. Not supported for the Integration user type.
- **Conga user management users bulk update** (Update). Update multiple Conga Platform users with one request. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Each update object requires id. Not supported for the Integration user type.
- **Get single Conga user management user by ID** (Get). Get the details of a Conga Platform user by id. Returns the user record: FirstName, LastName, UserName, Email, Role, PermissionGroups, IsActive, CreatedDate, and more. Required: id.
- **Update a Conga user management user by ID** (Update). Update a Conga Platform user's details by id. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: id. Supported number, date, and currency formats are listed by the Timezone/Locale and Currency Format APIs.
- **Delete a Conga user management user by ID** (Delete). Deactivate a Conga Platform user by id. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: id. The user is deactivated rather than permanently deleted and can be restored.
- **Conga user management users clone** (Action). Clone a Conga Platform user by user_id and get the cloned user's id. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Cloning is not supported for users of the Integration type. Required: user_id.
- **Conga user management users restore** (Restore). Restore a deactivated Conga Platform user by user_id and notify the auth service. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: user_id.
- **Create a Conga users upload** (Create). Upload a .csv file of user records to bulk-create users in Conga. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Incorrect field names fail validation with an error message in the response; user upload is not supported for the Integration user type.
- **List all Conga templates downloads** (List). Download a CSV template for uploading users in Conga User Management. Fetches the latest user metadata and returns a .csv file containing all user fields as a binary file for upload. Requires no parameters.
- **List all Conga user roles** (List). Get the role assigned to a user in Conga. Returns Success, Data (the role name, e.g. SystemAdmin), and StatusCode. Required: user_id.
- **Update a Conga user role by ID** (Update). Update a user's role in Conga by assigning the role identified by id to the user. Returns Success, Data (the updated user record with FirstName, Email, Role, and IsActive), and StatusCode. Required: id, user_id.
- **Conga user roles exists** (Action). Check whether a user in Conga is assigned a specific role. Returns Success, Data (true or false), and StatusCode. Required: user_id and role_id.
- **Conga user permissiongroups bulk update** (Update). Assign permission groups to a Conga user by appending the given group names to the user's current permission groups. Returns the updated user object with Success, StatusCode, and a Data record including UserName, Email, Role, PermissionGroups, and IsActive. Required: user_id.
- **Conga user permissiongroups bulk delete** (Delete). Remove permission groups from a Conga user by deleting the given group names from the user's current permission groups. Returns the updated user object along with error messages for invalid records, including Success, StatusCode, and a Data record with UserName, Email, Role, PermissionGroups, and IsActive. Required: user_id.
- **Conga users bulk upserts bulk update** (Update). Create and update multiple Conga Platform users in one call: an existing user (matched on a Platform user record identifier) is updated, a missing one is created. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Requires a JSON array of user upsert records (UserUpsertRequest).
- **Create a Conga user send welcome email** (Create). Re-send the welcome email with login details and credentials to a Conga user. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Not supported for the Integration user type. Required: user_id.
- **Get single Conga user secret by ID** (Get). Get an integration user's client ID in Conga by user ID. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: id.
- **Conga user secrets bulk update** (Update). Generate the client secret for an integration user in Conga. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: integration_user_id.
- **Conga users bulk upsert syncs bulk update** (Upsert). Create and update multiple Conga users synchronously — existing users (matched on the Platform user record identifier) are updated instead of duplicated, and new users are created. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings.
- **List all Conga user management user groups** (List). List user groups in Conga that meet the search criteria. Returns each group's Id, UserName, and PermissionGroups. The criteria field must be indexed.
- **Create a Conga user management user group** (Create). Create a user group in Conga. Returns Success, Data (the new user group's ID), and StatusCode. Requires a request body with the user group details to create.
- **Get single Conga user management user group by ID** (Get). Get a user group's details by id in Conga. Returns the group's Id, Name, Email, IsSendEmailToMembers, CreatedDate, and ModifiedDate. Required: id.
- **Update a Conga user management user group by ID** (Update). Update a user group's information by id in Conga. Returns Success, Data (the updated user group's ID), and StatusCode. Required: id.
- **Delete a Conga user management user group by ID** (Delete). Delete a user group by id in Conga. Returns Success, Data (a 'deleted successfully' confirmation), and StatusCode. Required: id.
- **Conga user groups bulk upsert user groups bulk update** (Upsert). Create or update multiple Conga user groups in bulk by sending an array of user group model records; existing groups (matched on a Platform user record identifier) are updated and missing ones are created. Returns: Success, RecordCount, Data, Errors, Profile, StatusCode, and 4 more. Requires the body to be an array of user group records to upsert.
- **Create a Conga user group member** (Create). Add a member to a Conga user group. Returns the API response envelope with Success, Data (the newly added member's id), and StatusCode. Required: user_group_id, member_id.
- **Delete a Conga user group member by ID** (Delete). Delete a member from a Conga user group. Returns the API response envelope with Success, Data (a confirmation message that the member was deleted), and StatusCode. Required: user_group_id and id.
- **List all Conga user group members** (List). List all members of a Conga user group. Returns the API response envelope with Success, RecordCount, Data (member entries with Id, UserName, PermissionGroups), and StatusCode. Required: user_group_id.
- **Create a Conga user groups bulk create user group member** (Create). Create user group members in bulk in Conga. Adds new members to user groups and returns the IDs of the newly added members. Returns the API response with Success, Data (including the new member Id), and StatusCode. Takes a JSON array of user group member details as the body.
- **Get single Conga user groups member by ID** (Get). Get the details of a Conga Platform user group member by its id (an individual user or user group). Returns Success, Data (including UserGroupId, MemberId, MemberType, Name, CreatedBy, CreatedDate, ModifiedBy, ModifiedDate, ExternalId, and ETag), and StatusCode. Required: id.
- **List all Conga user groups members** (List). List all Conga Platform user group members that meet the criteria. Returns Success, RecordCount, StatusCode, and Data records with UserName, Id, and PermissionGroups. Optional filters: criteria (e.g. UserGroupId = 'abcd', must be an indexed field), sortField, and sortDirection (defaults to DESC when sortField is set).
- **List all Conga user management roles** (List). List all roles in Conga that meet the search criteria. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings.
- **Create a Conga user management role** (Create). Create a new role in Conga. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. The request body takes the role's Name and Description.
- **Conga user management roles bulk create** (Create). Create multiple roles in Conga in one request. The request body is an array of roles, each with a Name and Description. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings.
- **Get single Conga user management role by ID** (Get). Get a single Conga role by id. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: id.
- **Update a Conga user management role by ID** (Update). Update the name and description of a Conga role by id. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: id.
- **Delete a Conga user management role by ID** (Delete). Delete a role in Conga by id. Returns the API response including Success, Data (a confirmation message naming the deleted role id), and StatusCode. Required: id.
- **Conga user management roles clone** (Action). Clone a role in Conga by id and create a copy of it. Returns the API response including Success, Data (the cloned role's id), and StatusCode. Required: role_id.
- **Conga role permissiongroups bulk update** (Update). Assign permission groups to a role in Conga; the given permission group names are appended to the role's current permission groups. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: role_id.
- **Conga role permissiongroups bulk delete** (Delete). Remove permission groups from a role in Conga; the given names are dropped from the role's current permission groups. Returns: Success, Data (the updated role with Id, Name, Description, PermissionGroups), StatusCode, plus error messages for invalid records. Required: role_id.
- **Conga role admin permissions bulk update** (Update). Assign admin permissions to a role in Conga by appending them to the role's current admin permissions. Returns Success, Data (the updated role with Id, Name, AdminPermissions, PermissionGroups, CreatedDate, ModifiedDate), and StatusCode. Required: role_id.
- **Conga role admin permissions bulk delete** (Delete). Remove admin permissions from a role in Conga. Returns Success, Data (the updated role with Id, Name, AdminPermissions, PermissionGroups, ModifiedDate), and StatusCode. Required: role_id.
- **List all Conga user management admin permissions** (List). List the master set of admin permissions in Conga user management. Returns the response envelope with Success, Data (an AdminPermissionsList of Value, DisplayName, and Description), and StatusCode. Takes no parameters.
- **List all Conga user management permissiongroups** (List). List the master permission groups from Conga data storage. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings.
- **Create a Conga user management permissiongroup** (Create). Add permission group names to Conga's master list. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Requires a request body listing the permission groups to add; each name must be unique and no longer than 80 characters.
- **Conga user management permissiongroups clone** (Action). Clone a Conga permission group, copying its object and scope permissions, and add the copy to the master list. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Required: permissiongroup_id.
- **Conga user management permissiongroups bulk delete** (Delete). Delete permission groups from Conga's master list, also removing associated object, action, or scope permissions when no user or role is attached. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, HasMoreRecords, NextCursor, Warnings. Requires a request body listing the permission groups to delete.
- **List all Conga contact scope applicable objects** (List). List the objects applicable for contact scope in a Conga permission group — primary objects plus any object with a lookup or reference field pointing to a primary object, filtered by the objects available in that group. Returns: Success, RecordCount, Data, Errors, Profile, TotalTime, StatusCode, and 3 more. Required: permission_group_name.
- ...and 1751 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
