Compatible with every major AI agent and IDE
What is the Dagger (Programmable CI) MCP Server?
Connect to the Dagger Engine to orchestrate your delivery pipelines using a powerful, programmable GraphQL API. This server allows your AI agent to interact directly with Dagger's Directed Acyclic Graph (DAG) of operations.
What you can do
- Container Orchestration — Initialize scratch containers, pull images, and manage OCI-compatible states.
- GraphQL Workflows — Execute raw GraphQL queries to compose complex build and test logic dynamically.
- Source Control — Query Git repositories and host environments to pull source code into your pipelines.
- Resource Management — Handle secrets securely, manage persistent cache volumes, and fetch remote files via HTTP.
- Module Inspection — Query the current module state and engine version to ensure environment consistency.
How it works
- Ensure a Dagger Engine is running in your environment.
- Provide the session port and token generated by the Dagger CLI.
- Start building and deploying through natural language commands.
Who is this for?
- DevOps Engineers — Automate pipeline debugging and execution without leaving the chat interface.
- Software Developers — Run builds, tests, and container operations directly from the code editor.
- SREs — Inspect engine states and orchestrate infrastructure tasks using programmable CI logic.
Built-in capabilities (10)
You can chain fields to create a Directed Acyclic Graph (DAG) of operations. Execute a raw GraphQL query against the Dagger engine
Constructs a cache volume
Creates a scratch container and returns its ID
Queries the current module
Creates an empty directory and returns its ID
Queries a Git repository
Queries the host environment
Returns a file from a URL
g., env://VAR_NAME, file://PATH, cmd://COMMAND). Creates a new secret
Get the Dagger Engine version
Why Claude Desktop?
Claude Desktop is the definitive way to connect Dagger (Programmable CI) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Dagger (Programmable CI) in Claude Desktop
Dagger (Programmable CI) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Dagger (Programmable CI) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Dagger (Programmable CI) in Claude Desktop
The Dagger (Programmable CI) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Dagger (Programmable CI) for Claude Desktop
Every tool call from Claude Desktop to the Dagger (Programmable CI) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I run a specific build command using Dagger?
You can use the execute_graphql_query tool to send a raw GraphQL query to the Dagger engine, allowing you to chain container operations like from, withExec, and stdout.
Can I access files from my local machine in the pipeline?
Yes, the query_host tool allows you to retrieve the state ID for your host environment, which can then be used to mount local directories into your Dagger containers.
How are secrets handled in this integration?
Use the query_secret tool to load secrets from URIs (like env:// or file://). This returns a secret ID that can be safely passed to other Dagger operations without exposing the plaintext value.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Jitbit
6 toolsTrack and resolve IT support tickets with a fast helpdesk that includes automation rules, knowledge base, and SLA monitoring.

Creatomate
9 toolsEquip your AI agent to automate video generation, rendering, and asset management via the Creatomate API.

Epic Online Services & Social Analytics
8 toolsThe definitive server for Epic Games social intelligence — track player profiles, friends, and achievements via AI.

FOIA.gov (Freedom of Information)
4 toolsAccess US government FOIA data — list agency components, retrieve request forms, and fetch annual reports directly from FOIA.gov.
