Connect your AI to Codeo3
Let a compatible AI agent read, edit, build and publish your Codeo3 projects — through one standard connection.
One MCP endpoint. Every compatible client connects to the same Codeo3.
02 — TWO WAYS TO BUILD
Two ways to build with AI.
Bring your AI into Codeo3, or stay entirely inside Codeo3.
AI Connections
EXTERNAL AIBring your AI.
Connect a compatible AI or coding agent to Codeo3 and let it work with your Codeo3 projects — designed for developers who already use an external AI, coding agent, or IDE.
- Use your preferred AI
- Connect through MCP
- Work with Codeo3 projects
- Switch between compatible AI clients
- Keep Codeo3 as the project workspace
AskCodeo
BUILT INTO CODEO3Build inside Codeo3.
Don't use an external IDE? AskCodeo is built into Edit Code Builder — describe what you want and build without leaving Codeo3. No API keys to manage.
- Ask mode— Learn, plan and troubleshoot — free to start
- Build mode— Edits your project with review-before-apply
- Pro— 30-day pass · one-time purchase · no renewal
Choose how you want to build.
03 — AI CONNECTIONS
Bring ChatGPT, Claude, Devin — or another compatible AI.
One remote MCP server speaks to every standards-compliant client. Add the Codeo3 endpoint, approve the branded sign-in, and your AI can see your projects.
Connect the MCP endpoint — OAuth sign-in runs in the browser.
Create a connector pointing at the Codeo3 MCP endpoint.
Add Codeo3 as a remote MCP server / connector.
Any client that supports remote MCP + OAuth can connect.
Compatibility reflects clients that implement the standard remote MCP flow — see the integration docs for the tested matrix. Nothing here is client-specific; they all use the same endpoint.
04 — ASKCODEO
Stay inside Codeo3.
AskCodeo is built into Edit Code Builder. Describe what you want to build, review the proposed changes, and accept them — no external AI application, IDE, or API key.
AskCodeo prepares a candidate — your saved build stays untouched until you accept.
The AskCodeo bar inside Edit Code Builder — changes are proposed for review, never applied silently.
Already use an AI coding agent?
Connect it to Codeo3 — ChatGPT, Claude, Devin, or another compatible client.
Want to stay inside Codeo3?
AskCodeo is built into Edit Code Builder — no external IDE or API key required.
External AI → Codeo3, or built-in AI → Codeo3. Both paths operate on the same projects.
05 — CAPABILITIES
What your AI can do.
Once connected, a compatible AI works with the same Codeo3 project surface the editor uses — under the same permissions.
Read projects
List your projects, open one, and read its files and blocks.
Create projects
Start a new draft — a game, site, prototype, or tool.
Edit blocks
Add, update, reorder or remove code blocks in a project.
Preview & debug
Run the build validation, read errors, and repair them.
Update metadata
Title, description, category and visibility.
Publish
Publish or unpublish — always with your explicit confirmation.
06 — ARCHITECTURE
Cloud vs Local.
A Codeo3 project can span two sources — Cloud Blocks stored in your account, and local files on your computer through Codeo3 Desktop. Your AI sees one project; each source keeps its own boundary.
Cloud Blocks
- • Live in your Codeo3 account — editable anywhere
- • Read and written through the Codeo3 API
- • Ownership and publish rules enforced server-side
Local files
- • Stay on your filesystem — never mirrored to the cloud
- • Exposed to AI tools via the Codeo3 Desktop bridge
- • Nothing grants access by itself — auth is still checked
07 — PORTABLE
Switch AI. Keep building.
The connection is a standard — not a lock-in. The same Codeo3 project can be opened by Devin today, Claude tomorrow, and the next compatible client after that.
08 — FOR DEVELOPERS
Built on MCP.
Codeo3 implements the Model Context Protocol over Streamable HTTP — JSON-RPC 2.0, one endpoint, standard OAuth 2.1 discovery. If your tool speaks MCP, it speaks Codeo3.
Server: https://codeo3.com/api/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Auth: OAuth 2.1 + PKCE — dynamic client registration
Discovery: /.well-known/oauth-protected-resource
/.well-known/oauth-authorization-server09 — SECURITY
Your account stays yours.
The same rules protect both workflows — authentication on codeo3.com, scoped permissions, and boundaries that never blur.
OAuth, not passwords
AI clients sign in through the branded Codeo3 consent page — your password is never shared with a client.
Scoped tokens
AI Connections use scoped OAuth tokens (read, write, publish) — revocable at any time.
Explicit publishing
Publishing and unpublishing always require your explicit confirmation — never silent.
Nothing to leak
AskCodeo runs on Codeo3-managed credentials — there are no user API keys to store or expose.
Ownership enforced
Every request checks project ownership server-side — a client can only touch your projects.
Local stays local
Desktop local files never leave your machine — the bridge only exposes them to tools you configure.
Bring your AI. Build in Codeo3.
Point a compatible client at the MCP endpoint, or open Edit Code Builder and ask AskCodeo — same projects, your choice.
https://codeo3.com/api/mcp