Agent-native Dilnaka Cloud
Model Context Protocol
MCP exposes Dilnaka as scoped tools and compact resources without introducing a separate business-logic layer.
Connect
Use the MCP 2026-07-28 Streamable HTTP endpoint with a Dilnaka service-account bearer token. The protocol layer is stateless and the tool catalog is deterministic.
- Endpoint: https://dilnaka.cloud.tsnc.tech/mcp/
- Authentication: Bearer service account
- Transport: Streamable HTTP
{
"url": "https://dilnaka.cloud.tsnc.tech/mcp/",
"headers": {"Authorization": "Bearer dlk_sa_…"}
}Tools and resources
Focused tools cover applications, deployments, databases, domains, mail-domain status, environment variables, logs, metrics, storage, usage, quotas, billing, and tasks. Read-only resources use dilnaka:// URIs. Each tool enforces scopes and tenant ownership in the shared gateway.
- apps_list, apps_get, apps_create, apps_update, apps_delete
- deployments_list, deployments_get, deployments_create, deployments_cancel, deployments_rollback, deployments_logs, diagnose_deployment
- databases_list, databases_get, databases_create, databases_delete
- domains_list, domains_get, domains_add, domains_verify, domains_remove
- email_domains_list, env_list, env_set, env_delete
- logs_get, metrics_get, health_get, storage_list, usage_get, quotas_get, billing_summary
- tasks_get, tasks_cancel
- dilnaka://docs/platform, dilnaka://docs/deployments, dilnaka://apps/{id}, dilnaka://deployments/{id}
Tasks and approvals
FastMCP exposes the current official Tasks extension. Infrastructure writes also return the durable Dilnaka task observed by REST, A2A, the dashboard, and webhooks. Destructive calls remain waiting until a human approves them.
Bounded diagnostics
logs_get and deployments_logs accept limit, cursor, severity, and search inputs. diagnose_deployment combines bounded build and runtime evidence without changing infrastructure.