Trama and AI
Three ways to put Trama and an AI assistant together — and which one is yours.
Trama already runs on AI inside the product: the Inquiry Agent answers your customers, and the Trama Agent is your team's copilot. This section is about the other direction: connecting your own AI to Trama.
There are three doors, and they're for different jobs.
The MCP connector
Ask and operate your Trama from Claude or ChatGPT, in plain language. No code.
The REST API
For an integration you write yourself, or an agent you're building.
These docs as context
Point any assistant at the documentation so it answers about Trama correctly.
Which one you want
| If you want to… | Use |
|---|---|
| Ask "what's pending today", move a card, draft a follow-up — from your own assistant | MCP |
| Sync Trama with another system, or build a product on top | The API |
| Have Claude, Cursor or ChatGPT answer questions about Trama | The docs |
MCP and the API are not the same door
They look interchangeable and they aren't:
- The MCP server goes through the Trama Agent, so it carries the product's rules with it: your role decides which tools you even see, and writing an opportunity goes through the same path the dashboard uses. It's meant for a person driving an assistant.
- The API is a raw contract. No role, no agent, no interpretation — the key reads the whole organization. It's meant for code.
That's also why the two have different reach: MCP can create and move opportunities, MCP can log follow-ups, and the API can't.
What neither of them does
Neither one can reply to a customer. Not through MCP, not through the API. There is exactly one exception, and it's narrow: answering a question the agent asked your team. Everything else that reaches a customer goes out from Trama.
Both are available on every plan, at no extra cost, the free one included. The one thing that draws on your plan's daily allowance is the ask_trama tool, because that one runs the Trama Agent. The rest don't.