Can the AI automatically find a person's profile by their email address?

Yes! Use the `get_person` tool with the target email address. Your agent will return the full profile metadata, including custom fields and account associations.

How do I specify which region my Ortto account is hosted in?

When configuring the server, use the `ORTTO_REGION` field. Supported values are 'Global' (default), 'AU' (Australia), or 'EU' (Europe), ensuring your agent connects to the correct data center.

Does the integration allow for triggering custom activities for engagement?

Yes. The `create_activity` tool allows you to programmatically trigger any custom activity defined in your Ortto instance, perfect for real-time automation and journey entry.

Ortto (formerly Autopilot) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Ortto (formerly Autopilot)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Ortto (formerly Autopilot) through Vinkius, pass the Edge URL in the `mcps` parameter and every Ortto (formerly Autopilot) 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="Ortto (formerly Autopilot) Specialist",
    goal="Help users interact with Ortto (formerly Autopilot) effectively",
    backstory=(
        "You are an expert at leveraging Ortto (formerly Autopilot) 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 Ortto (formerly Autopilot) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Ortto (formerly Autopilot) MCP Server

Connect your Ortto account to any AI agent and unify your customer data and marketing automation workflows through natural conversation.

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

What you can do

Unified Profiles — Create, update, and search for person and organizational account records across your CDP
Activity Orchestration — Programmatically trigger custom activities to engage users based on real-time events
Campaign Auditing — List audience segments and retrieve performance metrics for your marketing campaigns and journeys
Regional Compliance — Native support for Global, AU, and EU data centers to ensure your data stays where it belongs

The Ortto (formerly Autopilot) MCP Server exposes 10 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 Ortto (formerly Autopilot) to CrewAI via MCP

Follow these steps to integrate the Ortto (formerly Autopilot) 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 10 tools from Ortto (formerly Autopilot)

Why Use CrewAI with the Ortto (formerly Autopilot) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Ortto (formerly Autopilot) 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

Ortto (formerly Autopilot) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Ortto (formerly Autopilot) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Ortto (formerly Autopilot) 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 Ortto (formerly Autopilot), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Ortto (formerly Autopilot) 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 Ortto (formerly Autopilot) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Ortto (formerly Autopilot) MCP Tools for CrewAI (10)

These 10 tools become available when you connect Ortto (formerly Autopilot) to CrewAI via MCP:

create_activity

Create a custom activity for a person

create_person

Add a new person to Ortto

delete_person

Permanently archive/delete a person

get_person

Get details for a specific person

get_subscription

Get subscription status for an email

list_accounts

List accounts/organizations in Ortto

list_audiences

List audience segments

list_campaigns

List marketing campaigns

list_people

List people in Ortto

update_person

Update an existing person

Example Prompts for Ortto (formerly Autopilot) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Ortto (formerly Autopilot) immediately.

"Find the person profile for '[email protected]'."

"List all active marketing campaigns in our EU region."

"Trigger the 'product-demo-requested' activity for [email protected]"

Troubleshooting Ortto (formerly Autopilot) MCP Server with CrewAI

Common issues when connecting Ortto (formerly Autopilot) 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.

Ortto (formerly Autopilot) + CrewAI FAQ

Common questions about integrating Ortto (formerly Autopilot) 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.