How to Use the Help Scout MCP in CrewAI

Q: How do I connect the Help Scout MCP to my CrewAI agents?

Pass the server URL directly into the mcps array when defining your Agent. CrewAI automatically discovers and maps the tools.

Q: Can CrewAI agents collaborate on a single Help Scout ticket?

Yes. One agent can run getconversation and pass the context into shared memory, allowing a second agent to write a response.

Q: How do I restrict Help Scout MCP tools to specific CrewAI agents?

Use MCPServerHTTP from crewai.mcp and apply a toolfilter. This ensures your researcher agent only reads data, while only your execution agent can update statuses.

Q: What happens to customer emails during CrewAI processing?

Agents reading tickets via listconversations process live email bodies and sender addresses. The server operates ephemerally. Your crew holds the context in shared memory to resolve the issue, but the transport layer retains absolutely nothing.

Deploy autonomous support crews in CrewAI via MCP to read, route, and resolve Help Scout tickets.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Help Scout MCP to CrewAI

Create your Vinkius account to connect Help Scout 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 Help Scout with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Deploy autonomous triage crews

One agent cannot handle a busy support queue alone. CrewAI lets you build a dedicated team for incoming requests. Your monitor agent continuously polls the MCP Server using `list_mailboxes` and `list_conversations` to spot new activity. When a fresh ticket hits, the monitor hands the ID to an analyst agent. This separation of duties keeps your pipeline moving fast without bottlenecking a single LLM process. The crew works in parallel to clear the inbox.

Research past issues with the CrewAI MCP Server

Context requires digging. Your analyst agent takes the new ticket and fires `search_conversations` to find similar historical problems. It reads the previous resolutions to formulate a plan. If the issue requires a standard operating procedure, the agent checks `list_workflows`. The crew shares this memory, ensuring the final response aligns with your established support protocols rather than guessing.

Resolve and audit tickets autonomously

Action is the final step. A moderator agent reviews the proposed solution. If approved, an execution agent drops an internal summary using `create_convo_note`. The same agent then triggers `update_convo_status` to close the loop. You get a completely hands-off support operation where specialized agents handle everything from discovery to resolution without human intervention.

Setup guide

Set up Help Scout 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 Help Scout tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Help Scout 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="Help Scout Analyst",
        goal="Access and analyze Help Scout data via MCP.",
        backstory="Expert analyst with direct Help Scout access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Help Scout 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 Help Scout. 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 Help Scout 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 Help Scout MCP in CrewAI

Pass the server URL directly into the `mcps` array when defining your Agent. CrewAI automatically discovers and maps the tools.

Yes. One agent can run `get_conversation` and pass the context into shared memory, allowing a second agent to write a response.

Use `MCPServerHTTP` from `crewai.mcp` and apply a `tool_filter`. This ensures your researcher agent only reads data, while only your execution agent can update statuses.

Absolutely. You can set a manager agent to delegate Help Scout API tasks to subordinate agents based on the ticket complexity.

Agents reading tickets via `list_conversations` process live email bodies and sender addresses. The server operates ephemerally. Your crew holds the context in shared memory to resolve the issue, but the transport layer retains absolutely nothing.

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