How do I get an API Token for Front?

Log in to your Front account, click the gear icon (Settings), go to 'Developers' > 'API Tokens', and create a new token with 'Shared Resources' scope.

Can I search for specific types of conversations?

Yes, use the 'search_conversations' tool. It accepts standard Front search syntax, such as 'is:open' or 'inbox:support'.

Is it possible to reply to an email via the agent?

Yes! Use the 'send_inbox_reply' tool. You must provide the Conversation ID, the message body, and the Teammate ID of the sender.

How do I archive a conversation?

Use the 'update_conversation_status' tool and set the status parameter to 'archived'. This updates the global status for the shared inbox.

Front MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Front
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

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

Connect your Front account to any AI agent to automate your customer communication and shared inbox workflows through the Model Context Protocol (MCP). Front is a customer operations platform that enables teams to manage shared emails, SMS, and chats collaboratively. This MCP server enables you to track active conversations, assign messages, and fetch thread histories directly through natural conversation.

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

Key Features

Shared Inbox Management — List all accessible shared inboxes and retrieve the specific conversations routed to them.
Conversation Tracking — Search and list all customer conversations, checking their current status (open, archived) and assigned owners.
Message Threading — Fetch the complete message history for any specific conversation to maintain context before replying.
Collaborative Replies — Draft and send replies to active conversations directly from your chat interface on behalf of a teammate.
Status Automation — Programmatically update conversation statuses (e.g., archiving resolved issues) to keep inboxes clean.
Team & Contact Discovery — List all workspace teammates and customer contacts to ensure accurate routing and messaging.

The Front MCP Server exposes 12 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 Front to CrewAI via MCP

Follow these steps to integrate the Front 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 12 tools from Front

Why Use CrewAI with the Front MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Front 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

Front + CrewAI Use Cases

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

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

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

Front MCP Tools for CrewAI (12)

These 12 tools become available when you connect Front to CrewAI via MCP:

get_conversation_details

Get conversation metadata

get_inbox_details

Get inbox metadata

list_address_book

List contacts

list_all_conversations

List all conversations

list_conversation_messages

List thread messages

list_inbox_teammates

List Front teammates

list_inbox_threads

List inbox conversations

list_shared_inboxes

List shared inboxes

search_conversations

g. "inbox:inb_123 is:open"). Search all conversations

send_inbox_reply

Send a reply

update_conversation_status

g., archived, open) or assignee of a conversation. Update conversation

verify_api_status

Verify connection

Example Prompts for Front in CrewAI

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

"List all shared inboxes in my Front account."

"Search for open conversations in the Support inbox."

"Archive conversation 'cnv_987'."

Troubleshooting Front MCP Server with CrewAI

Common issues when connecting Front 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.

Front + CrewAI FAQ

Common questions about integrating Front 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.