How to Use the Equinix Metal MCP in CrewAI

Deploy a crew of AI agents with CrewAI to autonomously manage your Equinix Metal API keys, users, and project invitations.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Equinix Metal MCP to CrewAI

Create your Vinkius account to connect Equinix Metal to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Equinix Metal with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous API Key Management

This toolset allows a CrewAI team to manage your Equinix Metal API keys. You can assign one agent the role of 'Security Auditor' to periodically check for old keys. A second agent, the 'Credentials Manager', can then be tasked with using `create_project_api_key` and `delete_api_key` to rotate them. The agents share context, so the Auditor can pass the specific key ID to the Manager for deletion. This creates a complete, autonomous rotation system that operates without human intervention. It's a real set-it-and-forget-it security process.

An Agent Crew for User Onboarding

Use these tools to build a CrewAI team that handles new user setup on Equinix Metal. An 'HR Liaison' agent could monitor a new-hire list, then task a 'Provisioning' agent to use `create_email` to set up their account email. The Provisioning agent can then monitor the invite status using `get_invitation`. If the invite is declined via `decline_invitation`, a third 'Support' agent can be triggered by the CrewAI framework to open a ticket and investigate why. This divides the labor just like a human team would.

Build a Security Response Crew with this MCP Server

This MCP Server lets you build a security-focused crew. For instance, a 'Monitor' agent can watch audit logs for suspicious activity. If it spots a compromised account, it can delegate to a 'Responder' agent. The Responder agent's only job is to immediately revoke access by calling `delete_user_api_key` for the affected user. This creates an automated incident response system that acts faster than any human could. You can even filter tools so the Monitor agent can only read data, while the Responder has destructive permissions.

Setup guide

Set up Equinix Metal MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Equinix Metal tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Equinix Metal Analyst",
    goal="Access and analyze Equinix Metal data via MCP.",
    backstory="Expert analyst with direct Equinix Metal access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Equinix Metal transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Equinix Metal Analyst",
        goal="Access and analyze Equinix Metal data via MCP.",
        backstory="Expert analyst with direct Equinix Metal access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Equinix Metal transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Equinix Metal. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Equinix Metal now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Equinix Metal MCP in CrewAI

Define two separate agents in CrewAI. Give the 'Creator' agent the `create_project_api_key` tool and the 'Destroyer' agent the `delete_api_key` tool. You can use `tool_filter` in the `MCPServerHTTP` configuration to enforce this separation of duties.

Yes. One agent can be responsible for sending invites (a process outside this MCP server), while another uses `get_invitation` to monitor the status. A third agent can then take action based on the result, like logging a declined invitation found via `decline_invitation`.

It depends on your setup. CrewAI's role-based structure is key. You can create a 'Janitor' agent with permission to use `delete_api_key` but only allow it to act on keys passed to it by a 'Supervisor' agent, which runs validation checks first. This layered approach adds safety.

The simplest way is to pass your Vinkius URL directly into the `mcps` list when defining your Agent. For more control, use the `MCPServerHTTP` tool from `crewai.mcp`, which lets you filter which tools each specific agent can access.

This server handles Equinix Metal API keys, email addresses, and invitation details. All tool execution happens within Vinkius's secure, single-use sandboxes. The environment is torn down after your agent's task is complete, ensuring no sensitive data is ever stored at rest on the MCP server.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript