Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Conga to Claude Code

Have Claude generate documents and send them for signature in Conga. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Conga to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Conga, you add a Conga MCP server: a small hosted service that exposes Conga's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Conga account. No API keys pasted into config files.

claude mcp add --transport http conga https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Conga once connected?

Full read-write Conga access lets Claude generate a document from a template, merge in the right account and pricing data, add recipients and a signing order, and send it for signature through Conga Sign once you approve. The agreement prep that used to mean clicking through Conga or Salesforce happens where the request already started.

  • Generate a document from a Conga Composer or Sign template and merge in its data
  • Populate pricing, line items, and account fields on a quote or agreement
  • Add recipients and set a signing order on a Conga Sign envelope
  • Send a prepared document for signature after you approve it
  • Set an automatic reminder schedule so unsigned signers are reminded after N days when the package is sent
  • Update a draft agreement's fields or content before it goes out

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Conga access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Conga API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Conga changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Conga connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Conga connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Conga account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Conga's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Conga?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Conga account it signs in with. Revoking access is one click in Conga.

More on the Conga connector

Conga connector for claude.aiSignNow + Claude CodeSignRequest + Claude CodeProposify + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us