OtoCo MCP Overview

Connecting an AI agent to OtoCo lets you form and manage on-chain legal entities from Cursor, Claude, Codex, ChatGPT, Grok, and other MCP-compatible clients. You connect once through the OtoCo MCP (Model Context Protocol), then your agent can use OtoCo tools on your behalf — with public discovery available without a key, and private entity actions unlocked by your API key.

What's an MCP?

Model Context Protocol (MCP) is an open standard that lets AI agents connect to external apps and services. Instead of only answering questions, an AI with MCP access can take actions through OtoCo's capability registry — the same tools exposed over REST /v1.

OtoCo exposes a Streamable HTTP MCP server at /mcp and a versioned REST API at /v1. MCP tool names are capability names with dots replaced by underscores (entities.list → entities_list).

What your agent can do

Your agent can discover OtoCo products and jurisdictions, check name availability, start Instant or Standalone formation checkout, list entities you own, download documents and files, check banking/EIN status, and manage payments or subscriptions you authorize.

Examples of prompts you can give a connected agent:

"Show me Instant vs Standalone Delaware LLC options and prices."
"Check whether Acme LLC is available in Wyoming."
"List my entities on Polygon."
"What's the EIN status for my Wyoming Series on Base?"
"Create a checkout link for Tax ID on my entity — preview first, don't charge yet."

You stay in control

Money-moving and destructive tools are confirmation-gated. Your agent must show a preview and wait for your explicit yes before calling again with confirm: true.

What your agent can access

Public tools (no API key)

Without a key, the MCP server registers public tools only. These cover discovery and email-based checkout:

Jurisdictions, products, and getting-started guides
Name checks and public entity lookup
Instant Series checkout and Standalone email checkout (payment links are emailed — never returned to the agent)

API key tools

With an API key (Authorization: Bearer otoco_sk_…), your agent can also access your entities, documents, files, payments, subscriptions, finance notes, points, forms, and banking tools — limited by the scopes on that key. See How to get an API key.

Endpoints

Environment	MCP (Streamable HTTP)	REST base
Production	`https://api.otoco.io/mcp`	`https://api.otoco.io/v1`
Staging	`https://api-staging.otoco.io/mcp`	`https://api-staging.otoco.io/v1`

Current live MCP host

Use staging (https://api-staging.otoco.io/mcp) while production api.otoco.io is not yet serving /mcp. Production URLs are the target once rollout completes. On docs.otoco.io, the playground and connect snippets follow NEXT_PUBLIC_MCP_API_URL or NEXT_PUBLIC_API_URL when set.

Instant vs Standalone

If you ask an agent to “create a company” without specifying the path, it should show both Instant and Standalone options (from public_checkout_options / public_getting_started) and ask which you want before checkout.

Path	What it is	Typical tool
Instant	On-chain Series LLC under OtoCo’s master — faster/cheaper	`public_instant_checkout` (email + entity name, no API key) or `entities_creation_checkout` (API key)
Instant + EIN/VMA	Series in a Box (Instant + Tax ID + Virtual Mailing + Mercury)	`public_instant_checkout` with `bundle:"series-box"` (no API key) or authenticated `entities_series_box_checkout`
Standalone	Independent state-filed LLC	`public_entity_checkout` (email link; optional `bundle:"startup-box"`)

Authenticated Instant checkout uses defaultNetwork from public_checkout_options.formationPaths.instant when you omit network (basesepolia on staging, main in production).

Not offered via MCP

Standalone Master LLC is not an MCP formation product. “Series” / “instant” means Instant Series LLC, not Standalone Master.

Risks and spending safety

You are responsible for actions your AI agent takes with your API key. Before money-moving or destructive tools execute:

The first call returns a preview (no charge / no mutation).
Your agent should show the preview summary in plain English.
You explicitly approve in a later message.
Only then should the agent call again with confirm: true (and paymentAttemptId / confirmationToken for charges).

Never share API keys in public channels. Create separate keys per integration and revoke unused keys from DashPanel → Developer.

Next steps

How to get an API key — create a key in DashPanel
Connect your AI agent — Cursor, Claude, Codex, ChatGPT, Grok
API playground — categorized tools with copyable curl / Node.js

Canonical machine-readable reference: https://otoco.io/mcp.md