Dagger (Programmable CI) MCP Server for Google ADKGive Google ADK instant access to 10 tools to Execute Graphql Query, Query Cache Volume, Query Container, and more

Name: Dagger (Programmable CI)
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Dagger (Programmable CI) as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Ask AI about this MCP Server for Google ADK

Open in ChatGPT Open in Claude Open in Perplexity

The Dagger (Programmable CI) MCP Server for Google ADK is a standout in the Loved By Devs category — giving your AI agent 10 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="dagger_programmable_ci_agent",
    instruction=(
        "You help users interact with Dagger (Programmable CI) "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

Google ADK natively supports Dagger (Programmable CI) as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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.

The Dagger (Programmable CI) MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 10 Dagger (Programmable CI) tools available for Google ADK

When Google ADK connects to Dagger (Programmable CI) through Vinkius, your AI agent gets direct access to every tool listed below — spanning ci-cd, container-orchestration, pipeline-automation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

execute

Execute graphql query on Dagger (Programmable CI)

You can chain fields to create a Directed Acyclic Graph (DAG) of operations. Execute a raw GraphQL query against the Dagger engine

query

Query cache volume on Dagger (Programmable CI)

Constructs a cache volume

query

Query container on Dagger (Programmable CI)

Creates a scratch container and returns its ID

query

Query current module on Dagger (Programmable CI)

Queries the current module

query

Query directory on Dagger (Programmable CI)

Creates an empty directory and returns its ID

query

Query git on Dagger (Programmable CI)

Queries a Git repository

query

Query host on Dagger (Programmable CI)

Queries the host environment

query

Query http on Dagger (Programmable CI)

Returns a file from a URL

query

Query secret on Dagger (Programmable CI)

g., env://VAR_NAME, file://PATH, cmd://COMMAND). Creates a new secret

query

Query version on Dagger (Programmable CI)

Get the Dagger Engine version

Connect Dagger (Programmable CI) to Google ADK via MCP

Follow these steps to wire Dagger (Programmable CI) into Google ADK. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 10 tools from Dagger (Programmable CI) via MCP

Why Use Google ADK with the Dagger (Programmable CI) MCP Server

Google ADK provides unique advantages when paired with Dagger (Programmable CI) through the Model Context Protocol.

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Dagger (Programmable CI)

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

Seamless integration with Google Cloud services means you can combine Dagger (Programmable CI) tools with BigQuery, Vertex AI, and Cloud Functions

Dagger (Programmable CI) + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Dagger (Programmable CI) MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Dagger (Programmable CI) and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Dagger (Programmable CI) tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Dagger (Programmable CI) regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Dagger (Programmable CI)

Example Prompts for Dagger (Programmable CI) in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Dagger (Programmable CI) immediately.

"Check the current version of the Dagger engine."

"Initialize a scratch container and return its ID."

"Get the state of the git repository at https://github.com/dagger/dagger."

Troubleshooting Dagger (Programmable CI) MCP Server with Google ADK

Common issues when connecting Dagger (Programmable CI) to Google ADK through Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Dagger (Programmable CI) + Google ADK FAQ

Common questions about integrating Dagger (Programmable CI) MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.