4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
FreeScout MCP Server

Bring Shared Inbox
to CrewAI

Learn how to connect FreeScout to CrewAI and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add NoteAdd ReplyCreate ConversationCreate CustomerDelete ConversationGet ConversationGet CustomerGet MailboxGet UserList ConversationsList CustomersList MailboxesList ThreadsList UsersUpdate ConversationUpdate Customer

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
FreeScout

What is the FreeScout MCP Server?

Connect your FreeScout helpdesk to any AI agent to streamline your customer support workflows. FreeScout is the leading open-source helpdesk, and this MCP server allows you to interact with it using natural language.

What you can do

  • Mailbox Management — List and inspect all mailboxes in your installation to organize incoming requests.
  • Conversation Handling — Create, update, and delete conversations, or list them by mailbox to stay on top of tickets.
  • Customer Interaction — Send replies directly to customers or add internal notes for team collaboration.
  • Customer & User Directory — Manage customer profiles and list team members (users) to assign tasks efficiently.
  • Thread Inspection — View the full history of messages and threads within any conversation for complete context.

How it works

  1. Subscribe to this server
  2. Enter your FreeScout API Key and your instance's Base URL
  3. Start managing tickets and customers from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Support Teams — quickly summarize long threads and draft replies without leaving your AI workspace.
  • Support Managers — monitor mailbox activity and reassign conversations to the right team members.
  • Developers — integrate support data into your workflow to track bugs and customer feedback directly.

Built-in capabilities (16)

add_note

Add an internal note to a conversation

add_reply

Send a reply to the customer in a conversation

create_conversation

Create a new conversation

create_customer

Create a new customer

delete_conversation

Delete a conversation

get_conversation

Retrieve conversation details

get_customer

Retrieve customer details

get_mailbox

Retrieve a specific mailbox

get_user

Retrieve agent details

list_conversations

List conversations in a mailbox

list_customers

List customers

list_mailboxes

List all mailboxes

list_threads

List threads in a conversation

list_users

List all users/agents

update_conversation

Update a conversation (status, assignee, etc.)

update_customer

Update customer information

Why CrewAI?

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

  • 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

See it in action

FreeScout in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

FreeScout and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect FreeScout to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for FreeScout in CrewAI

The FreeScout 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. All 16 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

FreeScout
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

The Vinkius Advantage

How Vinkius secures FreeScout for CrewAI

Every tool call from CrewAI to the FreeScout MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I reply to a customer conversation using the AI?

You can use the add_reply tool. Just provide the Conversation ID and the body of your message, and the agent will send it to the customer via FreeScout.

02

Can I update the status or assignee of a ticket?

Yes! Use the update_conversation tool. You can change the status (active, pending, closed, spam) or provide an assignee_id to route the ticket to a specific team member.

03

Is it possible to add internal notes that the customer won't see?

Absolutely. Use the add_note tool to post internal comments on a conversation. These are visible to your team in FreeScout but are never sent to the customer.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →