Corply — Start and run your company MCP server

Corply

Incorporate your company through conversation. Corply connects the AI interface you use to your saved application, formation documents, founder signatures, and human-reviewed Delaware filing.

This is the cross-agent plugin wrapper. Company state and execution live on Corply's hosted MCP server. Corply is software, not a law firm.

ChatGPT on the web

The intended public experience is: enable Corply in ChatGPT, choose Connect, sign in and authorize on Corply's page, then return to the conversation. ChatGPT handles OAuth credentials; no CLI or local agent installation is needed.

Directory availability requires OpenAI review and publication. A public repository does not itself make Corply searchable in ChatGPT. The draft uses https://corply.dev/mcp/openai, whose capabilities are narrower than general MCP. See submission status and review notes.

Claude, Codex, Cursor, and other MCP clients

Reuse an existing installation and its native authentication control; do not duplicate connections. The general endpoint is:

https://corply.dev/mcp

For a Claude marketplace installation:

claude plugin marketplace add corply-dev/corply-plugin
claude plugin install corply@corply

In Claude Code, open /mcp, select Corply, and choose Authenticate. Other marketplace hosts use their available Connect or Reconnect control. Direct MCP setup remains available through the current setup guide. After linking, verify email and organization through the connected whoami.

Just ask

• "Incorporate my startup."
• "Where is my incorporation blocked?"
• "Help me review my Corply formation documents."

The agent asks for the next relevant fact, saves progress, and follows canonical results. It never invents signatures, payment, filing acceptance, or deadlines. Each founder acts as themselves. A new conversation does not mean starting a duplicate application.

The standard flow records disclosed pre-filing authority for enumerated automatic post-acceptance work. Secure identity fields stay in the browser. Corply Ops handles applicable 83(b) mailing.

Distribution

• General plugin: skills/corply/, Claude/Codex/Cursor manifests, and .mcp.json.
• OpenAI directory skill: submission/openai/skills/corply/, bound to /mcp/openai.
• Registry metadata: server.json, independently versioned from the plugin.
• No company data, credentials, backend code, or private workflow catalog belongs here.

The server owns schemas and business state. Plugin instructions are snapshots; updates require the client's plugin update/reinstall mechanism. OpenAI uploads require a reviewed snapshot. A GitHub push does not publish an OpenAI listing or replace its previously imported skills.

Validation and packaging

CORPLY_SKIP_LIVE_MCP=1 node scripts/check-mcp-sync.mjs
node scripts/check-mcp-sync.mjs
node --test scripts/package-openai-plugin.test.mjs
node scripts/package-openai-plugin.mjs
node scripts/check-mcp-sync.mjs --submission

Ordinary checks verify formation requirements and live OAuth/discovery without business mutations. Extra server tools are reported, not misrepresented as removed. The submission check separately reports directory blockers and must pass before final submission.

The packager creates corply-openai-skill-bundle.zip for the portal and corply-openai-plugin-full.zip for general cross-agent inspection. It uses explicit inventories and byte-validates both. The full general plugin is not a substitute for the directory skill.

More: Corply · Setup · Security · Support

License

Shortened. The full README is on GitHub.