Twelfth

npx add-mcp 'https://api.twelfth.ai/mcp'

Generic MCP

Any assistant that speaks the Model Context Protocol (MCP) can connect to a
Twelfth workspace, even if it isn’t in the named list. Twelfth exposes an MCP
endpoint at https://api.twelfth.ai/mcp, read-only unless you allow changes. It accepts an OAuth
user token or a workspace bearer key. Reach the setup guide from Settings →
AI & agents → Generic MCP.

Use this when your client isn’t Claude,
ChatGPT,
Gemini,
Grok,
Glean,
Cursor,
Claude Desktop, or
VS Code / Copilot. The pattern is
the same for every MCP client.

Connect with OAuth

If your client supports OAuth for a remote MCP server, add
https://api.twelfth.ai/mcp as the server URL. Twelfth’s discovery metadata
starts the sign-in flow. Choose a workspace and allowed read tools on the
consent screen. This connection reads as you, within your workspace role and
remits; no key needs to be copied. End it from Settings → AI & agents.

If you are signed out, Twelfth asks you to sign in before showing consent. The
connection requires an existing account and a workspace you belong to. If you
do not have an account, choose Book a demo from the sign-in page to request
access. If you have an account but no workspace, accept an invitation, create a
workspace, or book a demo for help getting started.

Connect with a workspace key

1. In Twelfth, open Settings → AI & agents, go to the Settings tab and, under API keys, choose Connect an agent → Generic MCP. Twelfth creates a key for this connection, copies it to your clipboard, and starts waiting for Generic MCP’s first request. Copy the key now if you need it again. Twelfth shows it only once.
2. In your client’s MCP configuration, add a server with:
   • URL / endpoint: the Twelfth endpoint shown on the connection’s row.
     • Authorization: a bearer token set to the key you generated.
3. Reload the client’s MCP servers, then ask it to list Twelfth’s tools to confirm the connection.

Allow changes

The consent screen also offers Allow changes, off unless you turn it on. With it on, an OAuth connection is offered the write tools you approve at consent, acting as you:

• twelfth_complete_action: mark one of your open actions done. A price review or price change closes as reviewed, no action: prices are only changed in Twelfth.
• twelfth_snooze_action: hide one until tomorrow or next week.
• twelfth_create_action: create a task for you, with a title and details.\n- twelfth_run_routine: run one of your own routines.\n- twelfth_update_agent_policy: owners/admins can update workspace chat defaults, including models and soft turn budgets. Requires workspace MFA when enforced.

They follow the same rules as the app’s Tasks page, and every call is recorded against the connection. Figures, prices, orders and other workspace settings cannot be changed over MCP. Existing connections keep their previous permissions; reconnect and approve the updated grant to enable chat-policy changes. A connection made without Allow changes, or before it existed, never sees these tools. Workspace keys never make changes. To turn it on or off, connect again; Extensions has the details.

Available tools

The connection reads, unless you allowed changes. Its available tools depend on its saved selection,
the workspace’s capabilities and, for OAuth, the member’s permissions. They
include:

• Get workspace identity and operating defaults.
• List workspace members and their roles.
• List open actions, including due dates, assignees, and available source context.
• Read-only analysis tools for the visible work-unit snapshot and the caller’s readable catalogue: sales metrics, product ranking, inventory position, product master, similar products, supplier constraints, supplier lookup, entity profiles and context, and methodology. Connected workspaces can also offer competitor price intelligence. Arbitrary warehouse SQL is reserved for Twelfth’s staff-only diagnostic workspace.

Tools that only make sense inside the in-app chat (asking the buyer a clarifying question, rendering a table or chart) are not offered over MCP. Tool results include source_evidence_ids; a later call can pass them back to refer to the same rows.

An MCP key is a workspace credential and belongs to no one person. It reads the whole business, the way the owner or admin who created it does, and is not narrowed to any one buyer’s remit.

Apart from the approved Allow changes tools, these tools cannot write data or make changes in Twelfth.

Prompts and resources

Clients that support MCP prompts can offer Twelfth’s ready-made briefs, often as
slash-commands: Weekly trading brief, Explain a recommendation,
Competitor price check, Supplier review and Project status. Each one
walks the assistant through the read-only tools above.

Clients that support MCP resources can pin standing context: the workspace,
open actions, members and, where the workspace has them, project
workflows, category settings, tracked pricing sets and integrations. A
resource shows only what its matching tool would, so a connection limited to
certain tools sees only those resources.

Events

An assistant can also watch the workspace and act when something changes:
new recommendations, competitor price moves, project changes, or a fresh day of
data. See Events.

What Twelfth records about a connection

Every call is logged against its connection: the tool name, whether it succeeded,
when, and how long it took. Tool results are never stored or sent to analytics;
only their size is. Workspace keys are stored hashed and shown once, at creation.
Repeated failed authentication from one address is refused for a cooling-off
period.

Plugins and listings

Where Twelfth is, or will be, listed:

• Claude (Claude Connectors Directory): listing in review. Until then, add Twelfth as a custom connector.
• ChatGPT and Codex (OpenAI Plugins Directory, one listing for both): in review. Until then, add Twelfth as a connector in ChatGPT, or by command in Codex (below).
• Microsoft Copilot, for Copilot Studio and Microsoft 365 Copilot: coming soon.

In Codex:

codex mcp add twelfth --url https://api.twelfth.ai/mcp && codex mcp login twelfth

Twelfth’s server is published in the
Official MCP Registry
as ai.twelfth/workspace, from the twelfth.ai domain. Clients and directories
that read the registry can find it there.

The open-source twelfth-ai/twelfth-mcp
repository holds the client side: the MCP configuration, a plugin for
Cursor and
Claude Code, and a skill that helps an assistant use the tools well. In Claude
Code:

/plugin marketplace add twelfth-ai/twelfth-mcp
/plugin install twelfth@twelfth

The repository contains configuration only. The server itself is hosted by
Twelfth, and every connection still signs in and follows your workspace
permissions.

Support

Email hello@twelfth.ai with any question about
connecting an assistant, a tool that returns something unexpected, or access to
your workspace. You can also use the form at
twelfth.ai/contact. Include the assistant you are
using (for example Microsoft Copilot, Claude or ChatGPT), the workspace name and
roughly when it happened, so we can find the request.

To use the connector you need an active Twelfth account in a Twelfth workspace.
To get one, book a demo.

Related

• AI & agents overview: the shared connect flow and available tools
• Events: let an assistant watch for changes
• API keys: create, name, tag, and revoke keys
• Vercel Connect: use Twelfth MCP from a Vercel app or agent