Vercel Connect

Vercel Connect

Vercel Connect can hold a twelfth connection for a Vercel app or agent. twelfth’s developer-facing resource is an MCP server that reads by default at:

https://api.twelfth.ai/mcp

It offers workspace context and analysis tools for products, sales, inventory, suppliers, pricing and projects. The tools available depend on the workspace’s capabilities and the connection’s permissions. twelfth’s separate public REST API currently exposes workspace identity and current tasks; the app’s /api/... routes are not a substitute for either supported surface.

Connect as a person with OAuth

Use https://api.twelfth.ai as the OAuth server URL in Vercel Connect. twelfth publishes OAuth server metadata and MCP protected-resource metadata. Vercel can discover the authorization and token endpoints and register its client dynamically.

Authorize with a user token. twelfth asks you to sign in, choose one workspace, and select the read tools this connection may use. Calls then follow your membership and readable remits. A connection for another workspace requires another authorization. You can end the connection under Settings → AI & agents in twelfth.

Connect a server with a workspace key

For unattended access, a workspace owner or admin can create a key under Settings → AI & agents → Create an API key. Give it a name, environment tag and allowed read tools. twelfth displays the key once. Store it in Vercel Connect as an API-key credential and send it to the MCP endpoint as Authorization: Bearer <key>.

A workspace key reads the workspace data permitted by its selected tools, independently of an individual member’s remits. Give each automation its own key so it can be revoked without affecting others.

API support and limits

  • The MCP connection reads by default. A user-token connection can also create, complete or snooze the person’s own actions and run their own routines, only if they turn on Allow changes; a workspace key never changes anything. No connection can change settings, create projects, issue keys or connect other services.
  • OAuth access requires a signed-in member. twelfth’s MCP tools cannot use an app-only OAuth token because it has no chosen workspace.
  • MCP tools are available at /mcp and the historical compatibility alias /v1/mcp; they are protocol endpoints, not a REST resource catalog. New integrations should use /mcp.

See AI & agents for the tool catalog and permissions, Generic MCP for client configuration, and API keys for key management.