Accessing AiMe with MCP
The Model Context Protocol (MCP) is the industry standard that MCP-enabled AI assistants can use to connect to Conga products. Just as an API provides direct access to an application without engaging a user interface, MCP provides an agent-friendly interface that eliminates the need for both user interfaces and direct programmatic requests to APIs. You can consider it an "agent wrapper" to Conga's Advantage Platform APIs.
Accessing AiMe with Claude
Give Claude access to your Conga Advantage instance using Model Context Protocol
Accessing AiMe with Microsoft Copilot
Give Microsoft Copilot access to your Conga instance using Model Context Protocol
- Your administrator has configured a custom MCP connector to your Conga tenant as described in Configuring Conga Advantage MCP Server for Microsoft Copilot.
- You have access to the Copilot agent.
- Open the Microsoft Copilot agent your administrator created in Configuring Conga Advantage MCP Server for Microsoft Copilot.
- Submit a prompt that requires Conga data.
- You may be prompted to sign in using your Conga credentials to grant the agent access.
- It may be necessary to resubmit your prompt.
The agent can retrieve and update information from your Conga tenant. When you submit a request that requires Conga data, the agent successfully invokes a Conga tool and returns current information from your Conga instance.
