How do I generate an API Key for Heymarket?

Log in to your Heymarket account, navigate to **Administration** > **Integrations** > **API**, and click **Create Key** to generate your unique identifier.

Can the agent send images or media via SMS (MMS)?

Yes! If you provide a public media URL in the message tool, Heymarket will automatically deliver it as an MMS to the recipient.

How do I find the correct Member ID to send messages from?

Use the `list_team_members` tool. It will return all staff members in your workspace along with their unique `id`, which you can then use as the sender.

INSTANT PLUG AND PLAY

Heymarket MCP Server for CrewAIGive CrewAI instant access to 9 tools to Create Contact, Get Chat History, Get Message Details, and more

Name: Heymarket
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 9 Tools Framework

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

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Heymarket app connector for CrewAI is a standout in the Communication Messaging category — giving your AI agent 9 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Heymarket Specialist",
    goal="Help users interact with Heymarket effectively",
    backstory=(
        "You are an expert at leveraging Heymarket 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 Heymarket "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 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 Heymarket MCP Server

Connect your Heymarket account to any AI agent and take full control of your business text messaging and SMS workflows through natural conversation.

When paired with CrewAI, Heymarket becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Heymarket 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

SMS Orchestration — Send and receive text messages programmatically across your business numbers
Shared Inbox Management — Monitor active chat threads and manage team-based conversations in real-time
Contact Relationships — Create and update detailed contact profiles to maintain a high-fidelity customer database
Team Collaboration — Retrieve staff member directories and manage assignments for inbound message routing
Message Monitoring — Track outbound message delivery status and retrieve complete conversation histories for audit

The Heymarket MCP Server exposes 9 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.

All 9 Heymarket tools available for CrewAI

When CrewAI connects to Heymarket through Vinkius, your AI agent gets direct access to every tool listed below — spanning business-sms, mms-messaging, shared-inbox, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_contact

get_chat_history

Get conversation history

get_message_details

Get details for a message

list_active_chats

List active conversations

list_contacts

Supports filtering by phone number. List Heymarket contacts

list_team_members

List Heymarket workspace members

send_sms_message

Requires member_id and to_number. Send an SMS or MMS message

update_chat_status

Modify chat state or assignment

update_contact_profile

Modify an existing contact

Connect Heymarket to CrewAI via MCP

Follow these steps to wire Heymarket into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

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 9 tools from Heymarket

Why Use CrewAI with the Heymarket MCP Server

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

Heymarket + CrewAI Use Cases

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

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

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

Example Prompts for Heymarket in CrewAI

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

"Send an SMS 'Your order is ready!' to '+15551234567' using member 'M123'."

"List all active chat conversations from the shared inbox."

"Update contact 'C456' with first name 'John' and add a note."

Troubleshooting Heymarket MCP Server with CrewAI

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

Heymarket + CrewAI FAQ

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