Before you start
The one thing you need before Stage 1 — an assistant connected to Dibbla — and the three steps that give you it.
The tutorial is done by an assistant: you describe each stage, it does the work. So the only thing to have in place before Stage 1 is an assistant that is connected to your Dibbla account. If you have already done this, skip to Stage 1.
Connect your assistant
-
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?
The stages also run through the dibbla command and the skill it installs for
Claude Code, Cursor, Gemini CLI and other code agents. Each stage shows the
CLI commands under the hood, so both routes arrive at the same app. Set it up
once with Get started with the CLI.
How you’ll know it worked
The third step’s answer names you, your organization and your role. That is the whole check: the assistant is connected as you, to the organization the tutorial’s app will live in. If it answers with an organization you did not expect, reconnect and pick the right one on the consent page.