Twelfth

Read your Twelfth retail workspace through permission-scoped, read-only MCP tools.

View on twelfth.aiTry this MCPSponsored

Hosted MCP Server

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

Installs into Claude Code, Codex, Cursor and more

Documentation

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 a
read-only MCP endpoint at https://api.twelfth.ai/mcp. 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 and 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.

Available tools

The connection is read-only. 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, not a person: it reads the whole business, the way the owner or admin who created it does. It is not narrowed to any one buyer’s remit.

These tools cannot write data or make changes in Twelfth.

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.

Related