Can I route conversational streams directly via the AI agent using the Universal Gateway?

Yes! You can orchestrate inferences parsing `run_gateway_chat` providing dedicated string formats mapping natively any enabled model.

Is it possible to monitor crashed services or container states?

Absolutely. Target the instance ID and emit `get_deployment_status` explicitly bounding execution limits and fetching live log matrices.

Are the deployment configuration variables isolated upon server launch?

Yes, using `deploy_mcp_server` dynamically provisions encapsulated boundaries. You stringify environment tokens seamlessly obscuring values into active runtimes only.

TrueFoundry MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: TrueFoundry
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to TrueFoundry through Vinkius, pass the Edge URL in the `mcps` parameter and every TrueFoundry tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="TrueFoundry Specialist",
    goal="Help users interact with TrueFoundry effectively",
    backstory=(
        "You are an expert at leveraging TrueFoundry tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in TrueFoundry "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

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

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 TrueFoundry MCP Server

What you can do

Connect AI agents to TrueFoundry's dual-architecture matrix encompassing both an AI Gateway and a Deployment Orchestrator:

When paired with CrewAI, TrueFoundry becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TrueFoundry tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Route LLM prompts securely utilizing a unified endpoint connecting to OpenAI, Anthropic, Gemini, Llama, and more
Manage LLM Embeddings mapping strings flawlessly through secure unified channels
Discover Gateway Models identifying exact runtime limitations and contexts
Orchestrate MCP Containers deploying new AI server topology straight onto infrastructure limits
Monitor Active Deployments generating status, usage array metrics, and isolation limits natively
List MCP Schemas utilizing the managed TrueFoundry MCP discovery engine array
Execute Chat streams dynamically routing user contexts purely bound without touching distinct API keys

The TrueFoundry MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI 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 TrueFoundry to CrewAI via MCP

Follow these steps to integrate the TrueFoundry MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from TrueFoundry

Why Use CrewAI with the TrueFoundry MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TrueFoundry through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

TrueFoundry + CrewAI Use Cases

Practical scenarios where CrewAI combined with the TrueFoundry MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries TrueFoundry for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries TrueFoundry, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain TrueFoundry tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries TrueFoundry against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

TrueFoundry MCP Tools for CrewAI (8)

These 8 tools become available when you connect TrueFoundry to CrewAI via MCP:

truefoundry_deploy_mcp_server

Spawn a new backend container logical process using TrueFoundry service mesh

truefoundry_generate_embeddings

Calculate semantic vectors securely using the unifed abstraction

truefoundry_get_deployment_status

Emit detailed metric states on the orchestration matrix bounds

truefoundry_get_mcp_server_info

Extract exact JSON metadata of one registered TrueFoundry tool schema

truefoundry_list_deployments

Monitor the existing array of running backend topologies mapped to the team

truefoundry_list_gateway_models

List all accessible foundation models from the TrueFoundry unified AI gateway

truefoundry_list_mcp_servers

Extract registry mapping of all available logical MCP Tools in TrueFoundry

truefoundry_run_gateway_chat

g., openai/gpt-4o) mapping the true chat parameter to the gateway. Perform inference explicitly pushing a model query string through TrueFoundry

Example Prompts for TrueFoundry in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with TrueFoundry immediately.

"List all active AI models supported natively inside my TrueFoundry gateway access instance."

"Trigger a chat payload pushing to 'openai-gpt4o' via TrueFoundry querying semantic structures bounding limits."

"Deploy the 'supabase-mcp' node-image natively mapping strict variables onto my cluster runtime boundaries."

Troubleshooting TrueFoundry MCP Server with CrewAI

Common issues when connecting TrueFoundry to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

TrueFoundry + CrewAI FAQ

Common questions about integrating TrueFoundry MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.