MCP
Your org graph, available to any MCP client — under your ACLs.
How MCP fits into aanty
aanty ships an MCP server so Claude, ChatGPT, Cursor or any MCP client can read and act on your org graph within your access controls — and aanty is also an MCP client, so agents inside aanty can use any MCP server you approve. MCP is Linux Foundation-governed interop, not a proprietary bolt-on.
aanty as MCP server
Expose channels, threads, entity-linked context and search to any MCP client, scoped to the caller’s own permissions — never more than they could see in the app.
aanty as MCP client
Agents inside aanty can call any MCP server your org approves, with the same capability scopes and audit trail as every other agent action.
ACL-governed both ways
Every MCP read or write is resolved against the same tenant RLS and role/relationship checks as the product itself — no separate, looser permission model.
Bi-directional integration
Events flow both ways: MCP activity lands in aanty as a typed message in the right thread, and actions taken in aanty — approvals, replies, assignments — flow back out to MCP, kept in sync through the same tenant-scoped access controls as the rest of the product.
See it alongside
Other integrations and pages that pair naturally with this one.
See MCP inside a real aanty workspace
Bring the MCP events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.