INTEGRATIONS + MCP

Your AI client is not the system of record.

Claude, ChatGPT, and MCP clients provide an interface. Symbia remains the standalone application platform: it defines the AI Agent, application version, capabilities, and chain of custody behind an action.

Connect at the edge. Keep the application in Symbia.

An integration brings a client to a Symbia host. It does not move the authority boundary or the activity record into the client.

MCP · ANY COMPATIBLE CLIENT

Direct MCP

Connect a client to a Symbia MCP server when you control the host and client configuration. Symbia retains the application objects, authority rules, and records in the deployment you operate.

Use this when: an existing client needs to invoke a defined Symbia application before it reaches external systems.

CLAUDE · LOCAL PLUGIN

Claude plugin

The Claude plugin starts a local Symbia host. Claude uses the capabilities exposed by that host; Symbia retains the session record and can produce a seal. It can also connect to a durable host you operate.

Use this when: you want Claude to work through Symbia without a Symbia account or cloud relay on the ephemeral path.

CHATGPT · REMOTE INTEGRATION

ChatGPT integration

ChatGPT requires a remote MCP endpoint, OAuth identity, and a tenant boundary before it can inspect a host, session, activity, or result. That integration is not shipped yet.

Why wait: the first remote integration must establish a read and inspection boundary before it is allowed to perform writes.

What remains true regardless of the client

The client can present an answer in natural language. It cannot create the signed application definition, delegated capability, observed outcome, or cryptographic chain of custody after the action occurred.

See the boundary before you connect a client.

The Explorer runs the model in a browser. Run the Stack when you are ready to define and operate a real application.

Open the Explorer

hello@symbia-labs.com