Connect your assistant.
Ship an app.
Claude, ChatGPT, Claude Code or Codex — the assistant you already use can build, change and deploy apps on Dibbla once it is connected. One URL, one approval, nothing to install. Search the whole site with ⌘ K.
Three steps, then you are in
-
Copy the connector URL
Copy the exact URL
https://mcp.dibbla.com/platform. It is the only thing you take with you to Claude. -
In Claude, add it as a custom connector
Here is what you will do there, so you know before you leave this page: choose Add custom connector, name it Dibbla, paste the URL and choose Continue. Leave every other field empty. 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 Claude should deploy, not only read.
-
Go to Claude Connectors
Open Claude Connectors in a new tab and do the above. Then 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?
-
Copy the connector URL
Copy the exact URL
https://mcp.dibbla.com/platform. Cowork uses the connectors of your Claude account, so this is the only thing you take with you. -
In Claude, add it as a custom connector
Here is what you will do there: choose Add custom connector, name it Dibbla, paste the URL and choose Continue. Leave every other field empty. 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 so Cowork can deploy, not only read.
-
Go to Claude Connectors
Open Claude Connectors in a new tab, or Settings → Connectors in the Claude desktop app, and do the above. Then 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?
-
Copy the connector URL
Copy the exact URL
https://mcp.dibbla.com/platform. It is the only thing you take with you to ChatGPT. -
In ChatGPT, add it as a custom MCP server
Here is what you will do there, so you know before you leave this page: choose +, then Add custom MCP server. Name it Dibbla, paste the URL as the Server URL and leave authentication on OAuth. Tick I understand and want to continue and choose Create as a plugin. 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. Custom MCP servers need a paid ChatGPT plan, on chatgpt.com.
-
Go to ChatGPT Plugins
Open ChatGPT Plugins in a new tab and do the above. Then 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?
One app — Lumen, an incident desk — carried from nothing through deploy, a database, AI, a workflow and a nightly pipeline.
What a connected assistant can and cannot do, consent, the app card in the chat, and how to revoke it.
Apps, orgs, the console and the portal — the vocabulary the rest uses.
Deepenings for the common things — deploys, domains, SSO, databases, logs.
Once your app is running, let it do things on its own.
Run the whole platform on your own cluster.