Corpo MCP Server

Give any MCP-compatible AI agent access to explore and prototype Wyoming DAO LLC formation workflows.

Local serverstdioPython

What is the Corpo MCP MCP server?

Give any MCP-compatible AI agent access to explore and prototype Wyoming DAO LLC formation workflows. Exposed over MCP by the corpo mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Corpo is a sandbox platform for AI agents and their operators to prototype the formation, governance, and operation of legal entities. AI agents are becoming economic actors — Corpo lets them explore the full lifecycle in a safe sandbox environment before production integrations go live.

Its toolset

Everything the assistant can do here goes through one of these:

  • get_pricing — —
  • get_entity_types — —
  • get_structures — —
  • get_capital_structures — —
  • get_operating_agreements — —
  • get_registered_agents — —
  • get_addons — —
  • get_actions_catalog — —
  • get_recipes — —
  • get_legal_faq — —
  • get_quote — —
  • get_directors — —

Configuration

You will need one environment variable: CORPO_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Corpo MCP's toolset — get_pricing, get_entity_types, get_structures and 11 more — is a fair guide to whether it matches your workflow. It is maintained by corpollc; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Corpo MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Corpo MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the corpo mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
get_pricing
get_entity_types
get_structures
get_capital_structures
get_operating_agreements
get_registered_agents
get_addons
get_actions_catalog
get_recipes
get_legal_faq
get_quote
get_directors
register_account
confirm_account

How to install the Corpo MCP MCP server

{
  "mcpServers": {
    "corpo": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/corpollc/corpo-mcp", "corpo-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CORPO_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Corpo MCP to get pricing.
  • Use Corpo MCP to get entity types.
  • Use Corpo MCP to get structures.

Frequently asked questions

It connects Corpo MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_pricing, get_entity_types, get_structures, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Corpo MCP directly.