home

AiMe

Adobe Sign ServicesAdvantage Platform AdministrationAgreementsAiMeApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Contribution Management SystemCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforcePrice ManagementPrice OptimizationPricing Solution SuiteQuote GenerationReal Time Pricing EngineSign for Advantage PlatformSign for SalesforceSmart CPQSmart SearchSubscriptionsTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for Advantage PlatformX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerConga Tech Pubs PlaygroundRelease NotesGeneralDocs by Release
Adobe Sign ServicesAdvantage Platform AdministrationAgreementsAiMeApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Contribution Management SystemCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforcePrice ManagementPrice OptimizationPricing Solution SuiteQuote GenerationReal Time Pricing EngineSign for Advantage PlatformSign for SalesforceSmart CPQSmart SearchSubscriptionsTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for Advantage PlatformX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerConga Tech Pubs PlaygroundRelease NotesGeneralDocs by Release

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Contents

Show Page Sections

AiMe

Setting Up AiMe

Model Context Protocol (MCP)

Model Context Protocol (MCP) is the standard protocol that AI assistants use to connect to external tools and data. AiMe supports this protocol, offering qualified AI agents MCP access to AiMe’s tools. Just as an API provides direct access to an application without engaging a user interface, MCP provides an agent-friendly interface that does not require a user interface or user intervention. You can consider it an "agent wrapper" to the application and platform APIs running on the Advantage Platform.

Connecting Claude to the Conga Advantage MCP Server

Connect Claude directly to your Conga instance using an OAuth-authenticated MCP custom connector.

  • You are a Claude.ai Team or Enterprise Owner, Primary Owner, or another user authorized to add custom connectors for the organization.
  • Your Salesforce org ID (if integrating with a Salesforce-connected tenant)
  • An external integration configured for your Salesforce org
Claude authenticates against your tenant using an OAuth Client ID generated through a UI-to-API connection. Because the MCP client uses the platform’s authentication service for user authentication and authorization, you do not need a dedicated client ID for Claude. You can reuse a compatible UI-to-API OAuth client by registering Claude's callback URI and CORS origin with that client. Otherwise, create a dedicated client.
  1. If you don't have an OAuth client ID, get one as described in Connecting the Advantage Platform UI to the Salesforce API, entering these values:
    1. Enter https://claude.ai/api/mcp/auth_callback as the Redirect URI value. If you use other Conga applications (e.g., RLP Cart, My Approvals), include their redirect URIs, separated by commas.
    2. Enter https://claude.ai in the Cors Origins field.
      Tip: One client ID per tenant. The authentication system supports multiple comma-separated redirect URLs per client ID. All authorized users in the Conga tenant can use the same OAuth client ID when configuring their Claude accounts. Users connect to their organization's connector with their own Conga account, and Conga applies that user's authentication and access permissions.
    1. Copy the generated client ID.
  2. If your tenant has a UI-to-API connection, you can reuse the existing client ID — you just need to register the Claude redirect URL against it.
    1. Go to the Conga API Connections tab as described in Connecting the Advantage Platform UI to the Salesforce API.
    2. Append https://claude.ai/api/mcp/auth_callback to the existing comma-separated Redirect URI list.
    3. Append https://claude.ai to the Cors Origins list with a comma separation.
    4. Save the configuration.
    5. Copy the client ID.
  3. Configure the connector in Claude.
    1. Open Claude.
    2. Click Organization Settings > Connectors > Add.
    3. Hover over Custom, and select Web.
    4. Enter a name for the connector. This is the name users see in the connectors list. Enter your connector's remote MCP server URL, in the form https://<instanceurl>/mcp. For example, https://rls.congacloud.com/mcp. Click Continue.
      Available Conga services are:

      • North America: https://rls.congacloud.com/mcp

      • Europe: https://rls.congacloud.eu/mcp

      • Australasia: https://rls.congacloud.au/mcp

    5. Under Authentication, choose Sign in now.
    6. Under OAuth client, choose Use your own OAuth client.
    7. Click Advanced settings and enter the OAuth client ID.
    8. Click Add to save the connector.
Your users can access the Conga custom connector. Each must connect the custom connector to their own Conga account before using it. See Accessing AiMe with Claude for more.

Configuring Conga Advantage MCP Server for Microsoft Copilot

  • You have access to Microsoft Copilot Studio and Power Apps.
  • You have permission to create UI-to-API connections in the Conga tenant and to create agents and custom connectors in the target Microsoft Power Platform environment.

Request a confidential client (Conga task)

Customers cannot create a client ID and secret. Create a Conga Professional Services ticket to request a new confidential client credentials set. Your request must contain your customer account name and org ID.

  1. Ask Conga Professional Services to generate a confidential client, providing your customer account name and org ID.

    Professional Services will create a support ticket to generate the client secret, and will send the resulting client ID and the client secret using a secure email link.

    Note: Once opened, the secure email link expires after 24 hours. Copy this value and store it securely.
    CAUTION: Handle the client secret with care! Never send the client secret over unsecured email or chat.
Create a new agent
  1. Open Microsoft Copilot Studio.
  2. Click Agents in the left navigation bar and then click the New agent button.
  3. From the pop-up, click Tools > + Add and select Model Context Protocol (MCP) from the drop-down menu.
    This raises the Add MCP server pop-up.
  4. Enter a server name, description, and the URL for the Conga MCP server (https://rls.congacloud.com/mcp) in the required fields. Do not add spaces to the server name. Write a meaningful server description, describing what the server does.
    Note: The agent orchestrator relies on this description to decide whether to call or pass up the server at runtime. Make sure your description is accurate and on point. One of the most common reasons for a tool not working is that a vague description has prevented the orchestrator from calling it.
  5. Under Authentication, click the radio buttons for OAuth 2.0, then Manual as they pop up.
    More fields are exposed.
  6. Enter the client ID and client secret that Conga Professional Services gave you in step 1. Enter these values for the remaining fields:
    Note: Enter the scopes verbatim, no matter which region you are configuring. Don't add other scopes and don't add commas between entries.
    North America:
    • Authorization URL: https://login-rls.congacloud.com/api/v1/auth/connect/authorize
    • Token URL: https://login-rls.congacloud.com/api/v1/auth/connect/token
    • Refresh token URL: https://login-rls.congacloud.com/api/v1/auth/connect/token
    • Scopes: openid offline_access
    Europe:
    • MCP server URL: https://rls.congacloud.eu/mcp
    • Authorization URL: https://login.congacloud.eu/api/v1/auth/connect/authorize
    • Token URL: https://login.congacloud.eu/api/v1/auth/connect/token
    • Refresh token URL: https://login.congacloud.eu/api/v1/auth/connect/token
    Australasia:
    • MCP server URL: https://rls.congacloud.au/mcp
    • Authorization URL: https://login.congacloud.au/api/v1/auth/connect/authorize
    • Token URL: https://login.congacloud.au/api/v1/auth/connect/token
    • Refresh token URL: https://login.congacloud.au/api/v1/auth/connect/token
  7. Click Add.
    Microsoft creates the MCP connector and generates its redirect URL.
  8. Copy the redirect URL and return it to Conga Professional Services. Ask them to update this parameter in the confidential client configuration requested in step 1.
Connect the MCP server to your agent

Create an authenticated connection between the Copilot Studio agent and the Conga MCP server.

  1. In Copilot Studio, open the agent you created in the steps above.
  2. Click Tools.
    This raises the "Add a tool" pop-up window.
  3. Select the Conga MCP tool you configured.
  4. Click Add.
    A Conga sign-in window opens.
  5. Sign in with your Conga credentials, then Add and configure.

Microsoft Copilot is connected to your Conga service instance and ready to use when:

  • The tool appears under "Tools", listing the tools it pulled from the server.

  • A prompt in the test pane triggers one such tool.

  • The activity map shows the tool returning data, rather than the model answering on its own.

Accessing AiMe with Microsoft Copilot
Administrator Guide
AiMe Agent

October 10, 2026