Connect your assistant
Three steps from the assistant you already use — Claude, Cowork, ChatGPT, Claude Code or Codex — to a connection that can read, change and deploy your apps on Dibbla. Nothing to install, nothing to ask us for.
Dibbla runs your apps. The assistant you already talk to — Claude, ChatGPT, Claude Code, Codex — can read their code, change it and deploy it, once it is connected to your Dibbla account. That connection is one URL and one approval in your browser. There is no token to paste, no allowlist to join and nothing to ask us for.
Pick your assistant. The three steps below are the whole setup.
-
Add the connector
In Settings → Connectors, choose Add. Name it Dibbla, paste the exact URL
https://mcp.dibbla.com/platformas the Remote MCP server URL, and choose Continue. Leave every other field empty. -
Connect and approve
Choose Connect. Dibbla’s consent page opens in your browser: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access if Claude should deploy, not only read.
-
Check who you are
Start a chat, enable Dibbla under Connectors in the + menu, and ask. The answer names you, your organization and your role.
Say this to ClaudeConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
-
Add the connector
Cowork uses the connectors of your Claude account. In the Claude desktop app, open Settings → Connectors and choose Add. Name it Dibbla, paste the exact URL
https://mcp.dibbla.com/platformas the Remote MCP server URL, and choose Continue. Leave every other field empty. -
Connect and approve
Choose Connect. Dibbla’s consent page opens in your browser: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access so Cowork can deploy, not only read.
-
Check who you are
Open Cowork, make sure Dibbla is enabled under Connectors, and ask. The answer names you, your organization and your role.
Say this to CoworkConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
-
Add the connector
In Settings → Plugins, choose Add → Add MCP Server. Name it Dibbla, choose Streamable HTTP, paste the exact URL
https://mcp.dibbla.com/platformin the URL field that appears, and Save. (No Add MCP Server? Turn on Developer mode in the same settings first — custom servers need a paid ChatGPT plan.) -
Connect and approve
Choose Connect. Dibbla’s consent page opens: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access if ChatGPT should deploy, not only read.
-
Check who you are
Start a chat, add Dibbla from the + menu, and ask. The answer names you, your organization and your role.
Say this to ChatGPTConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
-
Install the plugin
Inside Claude Code, add Dibbla’s public plugin repository and install the plugin. It brings the connector, the skill and two commands in one step.
$/plugin marketplace add https://github.com/dibbla-agents/dibbla-platform-connector $/plugin install dibbla@dibbla-platform-connector
-
Connect and approve
Run
/dibbla:connect. Your browser opens on Dibbla’s consent page: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access so Claude Code can deploy, not only read.$/dibbla:connect -
Check who you are
/dibbla:connectalready reports which user and organization it acts as. To hear it in plain words, ask. The answer names you, your organization and your role.Say this to Claude CodeConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
-
Add the server
One command. No token, no header: the endpoint takes neither.
$codex mcp add dibbla --url https://mcp.dibbla.com/platform -
Connect and approve
Log in once. Your browser opens on Dibbla’s consent page: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access so Codex can deploy, not only read.
$codex mcp login dibbla -
Check who you are
Start Codex and ask. The answer names you, your organization and your role.
Say this to CodexConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
-
Add the server
Any client that speaks remote MCP works. Give it three facts: the exact URL
https://mcp.dibbla.com/platform, streamable HTTP transport, and OAuth on. Do not configure an API token or a bearer-token variable — the endpoint takes neither. -
Connect and approve
Authorize from the client. Your browser opens on Dibbla’s consent page: it names the client asking, the organization the connection will act in, and what it wants to do. Choose Allow full access if the assistant should deploy, not only read.
-
Check who you are
Ask. The answer names you, your organization and your role.
Say this to your assistantConfirm the connection, and what it may do.
Which Dibbla organization am I connected as, and what can this connection do?
Sign up free on the pricing page — it starts a new organization on a 30-day trial. Then come back to the three steps above.
Then put something live
The connection can deploy from nothing. This asks for a one-page site and reports the address when it is running — the first thing worth saying to a connection made a minute ago.
Deploy a first app, and get its address.
Using the Dibbla connector, deploy a one-page site that says hello, and tell me its address when it is live.Already have apps? Three things to ask for first covers seeing what is there, reading the code that is running, and changing it.
Where to go next
One real app, carried from nothing through deploy, a database, AI, a workflow and a nightly pipeline.
What the assistant can and cannot do, how consent works, the app card, and troubleshooting.
The dibbla command and the skill that teaches Cursor, Gemini CLI and other
code agents to drive it.
Cut a connected assistant off yourself, at any time, without contacting support.