For Builders
MCP
Daguito's MCP (Model Context Protocol) server connects your coding assistant —Claude Code, Cursor or any other— to your account: manage flows, knowledge and agents without leaving your editor.
What you can do
The server exposes 18 tools, grouped by domain. From your coding assistant you can:
Get started
Tell your assistant what you want to build and in which language; it hands back a copy-paste recipe.
daguito_quickstart Flows
List, inspect, create, edit, delete, version and restore your conversational flows.
daguito_upsert_agentdaguito_upsert_flowdaguito_resolve_webhookdaguito_get_flowdaguito_list_flow_versionsdaguito_restore_flow_version Knowledge (RAG)
Manage bases and sources, ingest text or URLs, and run semantic search across your knowledge.
daguito_list_knowledge_basesdaguito_list_knowledge_sourcesdaguito_create_knowledge_sourcedaguito_ingest_textdaguito_ingest_urldaguito_search_knowledgedaguito_get_ingest_job Agents
Declare an agent as code and provision it —flow and webhook— in a single call.
daguito_get_node_catalogdaguito_template_preview Analytics
Read a usage snapshot: LLM spend, tokens, message volume and your organization's budget.
daguito_get_org_analytics Building with MCP
With the MCP installed, describe what you want and your assistant learns Daguito and installs the SDK that matches your project. Pick by how your app is set up:
Always through the official SDK for your language (JavaScript, Python or Go), never raw HTTP. The account key stays on the server; the browser gets a short-lived token or a public flow key.
Frontend + Backend
The lowest-latency option: your backend signs a scoped token and the browser attaches directly to the flow channel (input and output streaming), without routing data through your server.
API only
Everything on your server: resolve the flow's webhook and run it. Input and output both live in your API.
Frontend only
No backend: grant a flow a domain-locked public key and call it straight from the browser.
Each architecture is tested for real: an assistant builds the app from scratch with the MCP in an isolated sandbox and runs it against Daguito until the agent replies.
Your API key
Generate an account API key (prefixed dgsk_acc_) in the dashboard, under Settings → API keys. It's org-scoped: the server only acts on that organization.
Setup
Add the server to your MCP client config. It runs locally over stdio via npx:
Claude Code — one command
claude mcp add daguito --env DAGUITO_API_KEY=dgsk_acc_... -- npx -y @daguito/mcpReplace dgsk_acc_... with your account key. The command registers the server with Claude Code; reopen it and the assistant already knows Daguito.
Other clients (manual config)
{
"mcpServers": {
"daguito": {
"command": "npx",
"args": ["-y", "@daguito/mcp"],
"env": {
"DAGUITO_API_KEY": "dgsk_acc_..."
}
}
}
}Claude Code, Cursor and any other MCP client use the same stdio config: point them at npx -y @daguito/mcp with your DAGUITO_API_KEY.
Environment variables
DAGUITO_API_KEY Required. Your account API key; must start with dgsk_acc_. DAGUITO_API_URL Optional. API base URL (defaults to https://ingest.daguito.com). Override it only for self-hosted or staging environments. Security
The API key is org-scoped: the server only acts on the organization tied to that key, and the API rejects any cross-tenant access. It is read once at startup and never logged. Treat it like any credential: don't commit it to source control.