Skip to main content
Trama exposes an MCP (Model Context Protocol) server that lets you query your organization’s Operations Agent from external clients like Claude.ai and ChatGPT. Every query respects your role and the permissions you have inside the business.

​
What MCP is

MCP is an open standard that connects AI assistants to external tools and data. When you add Trama as an MCP connector, your AI client can ask the Trama Agent about your operation (opportunities, customers, follow-ups) using natural language, without copy-pasting between apps.

​
What you can do

The Trama MCP server exposes specific tools for each thing your assistant may need, and they return structured data (not text), so they compose with each other and with what your assistant already knows how to do:
  • Opportunities — list and filter, view the board, open the detail of one, create them, edit them, move them between columns, log follow-ups, archive and restore, and see the dormant ones.
  • Analytics — count and sum amounts grouped by seller, day, source, column, or temperature; plus seller performance.
  • Customers — list, search, view the full profile and everything the organization knows about each one; create and edit them.
  • Conversations — list them, open one with its messages, and see aggregate metrics.
  • Catalog — list products and view the detail of one.
  • Your pendings — pending follow-ups and reminders, with create, reschedule, and complete.
  • Organization — the operational overview: members, channels, inbox, and metrics.
On top of that, ask_trama remains: it asks the Operations Agent in natural language. It’s for whatever no specific tool covers: compound requests, chained actions, or questions about how Trama works. Examples:
  • “Show me this week’s qualified opportunities”
  • “How many new customers came in from the Bariloche campaign”
  • “Summarize Maria’s pending follow-ups”
Important: your role decides which tools you see. The server doesn’t offer you the ones you can’t use: a seller doesn’t see seller performance or team metrics, and without permission to take opportunities out of the funnel, archive and restore don’t show up. Editing the catalog, inviting people, and disputing opportunities aren’t exposed over MCP on purpose: they go through the dashboard.

​
Server URL

https://ai.trama.so/mcp That’s the only URL you’ll need. Authentication happens via OAuth 2.1: when you add the connector, your client redirects you to sign in to Trama and authorize access to the active organization.

​
Before you start

  • Have an active Trama account and have logged in to the dashboard at least once.
  • Have the organization you want to operate on selected as active (if you belong to several, the connector uses the active one at authorization time).
  • Use an MCP client that supports OAuth with Dynamic Client Registration. Claude.ai and ChatGPT already do.
The shortest path is to open Settings → Connect with AI in the Trama dashboard: there you’ll find a button that opens Claude with the connector already loaded, and the address ready to copy into ChatGPT.

​
Connect from Claude

  1. Open Settings → Connectors in Claude.ai or the desktop app.
  2. Click Add custom connector.
  3. Paste the URL https://ai.trama.so/mcp and confirm.
  4. Claude redirects you to Trama to sign in. Use the same account you log in to the dashboard with.
  5. Authorize access to your active organization.
  6. Done. In any conversation you can now ask Claude to use the Trama tool.
You need a paid Claude plan (Pro, Max, Team, or Enterprise): Free accounts can’t add connectors.

​
Connect from ChatGPT

  1. In ChatGPT, go to Settings → Connectors (available on paid plans).
  2. Open Advanced settings and turn on Developer mode. On team accounts, a workspace admin enables it.
  3. Choose Create and enter the URL https://ai.trama.so/mcp, with OAuth authentication.
  4. ChatGPT opens the OAuth flow against Trama. Sign in and authorize.
  5. Once connected, the ask_trama tool is available in any chat or as part of a custom GPT.

​
Permissions and security

  • Access uses OAuth 2.1: you never share your password with Claude or ChatGPT.
  • The token lives only inside the client you connected and can be revoked at any time from Trama settings.
  • Every response runs with your role on the active organization. If your permissions are reduced, the agent reflects it immediately.
  • If you’re invited to a new organization or switch active organizations, disconnect and reconnect the MCP to refresh the context.

​
Current limitations

  • Editing the catalog, inviting members, and disputing opportunities aren’t exposed over MCP: they’re high-blast-radius actions and go through the dashboard.
  • The MCP server doesn’t stream: each response arrives complete.
  • If your MCP client doesn’t support dynamic OAuth (Dynamic Client Registration), you won’t be able to connect. Claude.ai and ChatGPT already do.