AI & agents
Twelfth in your AI assistants
Your team already works in AI assistants. Twelfth lets those assistants read the commercial context behind the work — products, suppliers, sales, inventory, pricing, projects and open actions — so a question asked in Claude, ChatGPT, Copilot or Cursor is answered from your Twelfth workspace rather than from a pasted spreadsheet.
Assistants connect to one hosted endpoint, https://api.twelfth.ai/mcp, using the open Model Context Protocol (MCP). A person adds it as a connector, signs in to Twelfth, chooses the workspace and approves the read tools the assistant may use. No key is created or copied, and the connection reads as that person: their remits, their categories and nothing outside them.
Every connection is read-only and visible. Assistants cannot create, change or commit anything in Twelfth; decisions are still reviewed and committed by people inside the workspace. Owners and admins see every connection under Settings → AI & agents and can end any of them, and an ended connection is refused on its very next request.
Connect your assistant
Each guide covers the assistant's own connector screen. Any other MCP client connects the same way, by URL with OAuth, or with a workspace key an owner or admin creates for a server or script.
- Claude→
Add Twelfth as a custom connector in Claude.ai, then sign in and choose the workspace.
- ChatGPT→
Add Twelfth as a ChatGPT connector and approve the read tools.
- GitHub Copilot in VS Code→
Add Twelfth as an MCP server for GitHub Copilot in Visual Studio Code.
- Gemini→
Add Twelfth as a tool in Gemini and confirm the first request.
- Cursor→
Install the Twelfth plugin, or add Twelfth as an MCP server in Cursor.
- Any MCP client→
The endpoint, OAuth and bearer-key options, and the full list of read-only tools.
Built for enterprise control
Access follows your workspace, not the assistant. An OAuth connection inherits the member's role and remits and stops working the moment they leave the workspace, so there is no orphaned credential to hunt down. Workspace keys for servers and scripts are created only by owners and admins, labelled by environment, limited to the tools selected for them, stored hashed and shown once.
Every call is logged against its connection: the tool, whether it succeeded, when and how long it took. Tool results are never stored or sent to analytics; only their size is recorded. Each connection's row names the client and version that actually connected, so a key shared beyond its purpose is easy to spot and split.
- Twelfth Trust Centre→
Security controls, sub-processors and our SOC 2 and ISO 27001 programme, with security questionnaires on request.
- Managing AI connections→
How connections, keys, tool selection and revocation work for owners and admins.
- Privacy policy→
How Twelfth AI Pty Ltd handles personal information.
Where to find Twelfth
Twelfth's server is published in the Official MCP Registry as ai.twelfth/workspace, and its client configuration is open source, so your IT team can review exactly what an assistant is told to connect to.
- Official MCP Registry→
The verified ai.twelfth/workspace entry, published by Twelfth from the twelfth.ai domain.
- twelfth-ai/twelfth-mcp on GitHub→
MIT-licensed plugin and MCP configuration for Cursor and Claude Code, with install instructions.
- Twelfth developer resources→
MCP, authentication, signed webhooks and the OpenAPI description.
AI assistant questions
- Q01Which AI assistants work with Twelfth?
- Any assistant that supports the Model Context Protocol (MCP). Claude, ChatGPT, GitHub Copilot in VS Code, Gemini and Cursor have setup guides, and any other MCP client connects to
https://api.twelfth.ai/mcpthe same way: by URL with OAuth, or with a workspace key for servers and scripts. - Q02Can an AI assistant change data in Twelfth?
- No. Every tool an assistant can call is read-only. It cannot create, edit or commit anything in Twelfth; decisions are reviewed and committed by people inside the workspace.
- Q03What can an assistant see?
- Only one workspace, and only what the connection allows. An OAuth connection reads as the member who approved it, within their role, remits and categories, using the read tools they chose at sign-in. A workspace key reads with the tools an owner or admin selected for it.
- Q04Who controls which assistants are connected?
- Members can connect their own assistant, which reads only what they can already see. Owners and admins see every connection in the workspace, including which client and version connected, and can end any of them. An ended connection is refused on its next request.
- Q05Does Twelfth keep what an assistant reads?
- Twelfth logs each call's tool name, outcome, time and duration against its connection. The results themselves are never stored or sent to analytics; only their size is recorded.