Platform · MCP
Your operating system speaks MCP.
Gane runs an MCP server, so the AI assistants your team already uses can query your data and run your workflows directly, with the same permissions and governance as everything else in Gane.
Three enterprise-fit accounts engaged, each showing intent this week:
Open by protocol
Your operating data, not locked in a walled garden.
MCP is the open standard for connecting AI assistants to real systems. Gane speaks it, so the work Gane coordinates is reachable from wherever your team already thinks.
Ask
Query any object in plain language.
Your assistant reads your accounts, contacts, programs, content, labels, and performance the same way your team does. Ask a question, get an answer grounded in live Gane data, not a stale export.
Work
Do the work in the conversation. Keep the record in Gane.
Open a program and your assistant already knows the brief it has to fill, the audience you are aiming at, and what the last one taught you. It asks the questions that pin the scope down, pushes back on the vague answers, and drafts from there. What comes back is not just the finished work.
You have scoped this to demand generation managers. The last two reports converted at twice the rate with VP Marketing and above. Widen the seniority, or keep the narrower audience?
Governed
Scoped, permissioned, and audited.
MCP access is a scoped token tied to one user and one workspace, with read and write controlled per object. Nothing is exposed that you have not granted, every call is logged, and access is revocable in one click.
MCP access
Activegane_pat_••••••••4a2fEvery object, one endpoint
One connection to the whole operating system.
Gane is a configurable data core, so MCP does not stop at a few objects. It reaches across the whole system, and more of it opens up every release.
Two ways in
Marketing works the plan. Sales works the account.
Same endpoint, same permissions, two very different jobs. What each person can read is broad. What they can change is not.
Marketing
Works a program from scope to finished content, one phase at a time.
Sales
Works the account, and tells Gane what it could not have known.
That last one matters most. Your reps know things your systems never see, and today it dies in a notebook. Told once to an assistant, it lands in Gane and shapes the next campaign.
Works with the assistants you use
Any MCP client. One connection.
Claude, Cursor, or any assistant that speaks MCP connects to the same Gane endpoint. Point it at your workspace, and your operating system is one of its tools.
{
"mcpServers": {
"gane": {
"url": "https://app.gane.ai/mcp",
"token": "gane_pat_..."
}
}
}Questions
Frequently asked questions
What is Gane MCP?
Gane supports the Model Context Protocol, so the AI assistants your team already uses can read your plan, your programs and your signal, and do the work with you through a scoped, secure surface.
Which assistant do I need?
Any client that speaks MCP, including Claude and Cursor. Gane does not run the model. You bring your own, connect it to your workspace, and the thinking happens where your team already works.
What does Gane keep when the assistant does the work?
The finished work, versioned and approved by a named person, plus the reasoning that produced it. That includes the questions asked, the answers given, and every time you overruled the assistant. A brief on its own is a document. A brief with the argument attached is what makes the next one better.
Can it send campaigns on its own?
No. Campaign sends are always drafted and staged, never dispatched. A person reviews and approves them in Gane, exactly as they do today.
How is access controlled?
Access is a scoped token tied to one user and one workspace, with read and write set per object. Reading is broad and writing is narrow, so a sales rep can read the growth plan but cannot change it. Every call is audited and access is revocable at any time.