2,500+ MCP servers ready to use
Vinkius

Smithery MCP Server for Google ADK 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools SDK

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

Vinkius supports streamable HTTP and SSE.

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="smithery_agent",
    instruction=(
        "You help users interact with Smithery "
        "using 11 available tools."
    ),
    tools=[mcp_tools],
)
Smithery
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 Smithery MCP Server

What you can do

Connect AI agents to the Smithery Registry for comprehensive MCP server discovery and management:

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

  • Search MCP servers — find servers by name, description, or tags with semantic search
  • Get server details — review metadata, verification status, and user counts
  • Discover tools — list all tools (functions) exposed by any registered MCP server
  • Discover resources — list all data resources available from MCP servers
  • Discover prompts — list all prompt templates exposed by MCP servers
  • Create connections — connect to MCP servers via Smithery Connect with automatic OAuth handling
  • Manage connections — list, inspect, and remove MCP server connections
  • Generate service tokens — create scoped, time-limited tokens for frontend/agent access
  • View analytics — monitor server usage, adoption trends, and performance metrics

The Smithery MCP Server exposes 11 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Smithery to Google ADK via MCP

Follow these steps to integrate the Smithery MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 11 tools from Smithery via MCP

Why Use Google ADK with the Smithery MCP Server

Google ADK provides unique advantages when paired with Smithery through the Model Context Protocol.

01

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

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Smithery

03

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

04

Seamless integration with Google Cloud services means you can combine Smithery tools with BigQuery, Vertex AI, and Cloud Functions

Smithery + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Smithery MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Smithery and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Smithery tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Smithery regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Smithery

Smithery MCP Tools for Google ADK (11)

These 11 tools become available when you connect Smithery to Google ADK via MCP:

01

create_connection

Smithery handles OAuth, tokens, and sessions automatically. Requires the server namespace and connection configuration (mcpUrl, optional headers, metadata). Returns the connection ID, status, and server info. Use this to integrate MCP servers into your applications without managing authentication complexity. Create a new connection to an MCP server via Smithery Connect

02

create_service_token

The token has limited permissions defined by the policy (namespaces, resources, operations, metadata, TTL). Returns the token string. Use this to provide secure, time-limited access to MCP servers without exposing your main API key. Generate a scoped service token for frontend/agent access to MCP servers

03

delete_connection

This action cannot be undone. Requires namespace and connection ID. Use this to clean up unused connections or revoke access. Remove an MCP server connection

04

get_connection

Requires namespace and connection ID. Use this to review connection details or troubleshoot connectivity issues. Get detailed information about a specific MCP connection

05

get_server_analytics

Requires the server qualified name. Use this to monitor server adoption, identify usage trends, or troubleshoot performance issues. Get usage analytics for a specific MCP server

06

get_server_details

Requires the qualified name (e.g., "smithery/hello-world" or "github/github") from search_servers results. Use this to review server capabilities before connecting. Get detailed information about a specific MCP server from the Smithery registry

07

get_server_prompts

Returns prompt names, descriptions, and argument definitions. Requires the server qualified name. Use this to discover reusable prompt workflows available from the server. List all prompt templates exposed by a specific MCP server

08

get_server_resources

Returns resource URIs, names, descriptions, and MIME types. Requires the server qualified name. Use this to understand what data the server provides read access to. List all resources exposed by a specific MCP server

09

get_server_tools

Returns tool names, descriptions, input schemas, and annotations. Requires the server qualified name. Use this to understand what actions the server can perform before connecting it to your agents. List all tools exposed by a specific MCP server

10

list_connections

Returns connection IDs, names, statuses, creation dates, and metadata. Use this to audit which connections are active, review connection configurations, or identify unused connections. List all connections for a specific MCP server namespace

11

search_servers

Returns matching servers with qualified names, descriptions, verification status, user counts, and deployment info. Use optional filters to narrow by namespace, verified status, or deployment state. Results include pagination metadata. Use this as the first step to discover available MCP servers before connecting or installing them. Search the Smithery registry for MCP servers by name, description, or tags

Example Prompts for Smithery in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Smithery immediately.

01

"Search for verified GitHub-related MCP servers"

02

"Show me all tools exposed by the Stripe MCP server"

03

"Create a connection to the Slack MCP server for my workspace"

Troubleshooting Smithery MCP Server with Google ADK

Common issues when connecting Smithery to Google ADK through the Vinkius, and how to resolve them.

01

McpToolset not found

Update: pip install --upgrade google-adk

Smithery + Google ADK FAQ

Common questions about integrating Smithery MCP Server with Google ADK.

01

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

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

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.

Connect Smithery to Google ADK

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.