MCP server
What exists today — a workflow-listing MCP server that is built but not exposed, and five WebMCP tools on dibbla.com behind a browser flag.
There is no reachable MCP endpoint. Everything below describes what exists in the code and why it does not help you yet — so that you can stop looking, and so it is clear what is left to do.
The hosted MCP server: built, not exposed
workflow-server contains a real MCP implementation. It serves one tool,
list_workflows, and authenticates with a DIBBLA_API_KEY header. The process
listens on port 8081.
Nothing routes to it. The Helm chart’s service publishes the HTTP and gRPC ports and not 8081, so the port is not reachable from outside the pod — there is no URL to point a client at.
So the honest status is not “not built”. It is: built, single-tool, and one service definition away from being reachable. Whether that is worth exposing as it stands — one read-only tool — is a product question rather than a missing implementation.
Not the same thing: WebMCP on dibbla.com
dibbla.com registers WebMCP tools on document.modelContext. This is a
different mechanism from the server above: it serves an agent that is driving a
browser on the marketing site, not an MCP client connecting to an API.
| WebMCP on dibbla.com | The hosted MCP server | |
|---|---|---|
| Who it serves | an agent driving a browser on the marketing site | Claude Desktop, ChatGPT connectors, any MCP client |
| What it can do | read the site’s own content; open the intro-booking flow | list workflows |
| Auth | none — the site is public | DIBBLA_API_KEY header |
| Status | shipped, but only active behind a Chrome flag | running, but no service port exposes it |
Five tools are registered: search_dibbla_faq, get_dibbla_overview,
get_dibbla_skills, get_install_command, and book_intro. The first four
are read-only. book_intro is not — it changes what is on screen, and declares
itself as such.
No origin-trial token is registered for the site, so these tools do not
activate for ordinary visitors. They appear only in a browser started with
chrome://flags/#enable-webmcp-testing. That is the difference between a
feature real users can reach and one only you can demo.
What to do instead
An agent that needs to understand Dibbla rather than operate it can fetch the skill directly — no MCP involved, and it is the path the platform actually supports today. See Fetching the skill without the CLI.
For operating the platform, an agent runs the CLI. That is what the
dibbla skill teaches it to do, and it is a larger surface
than any MCP tool catalogue currently on offer here.