Bring Business Sms
to Claude Code
Learn how to connect Heymarket to Claude Code and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the 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.
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
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Heymarket Dashboard (Administration > Integrations > API)
3. Start managing your SMS communications from Claude, Cursor, or any MCP client
No more manual texting from a mobile device or switching tabs to check your inbox. Your AI acts as your dedicated communication coordinator.
Who is this for?
- Sales Teams — automate lead qualification and follow-ups via SMS using natural language queries
- Customer Support — manage high-volume text queues and update contact details without leaving your workspace
- Operations Managers — monitor team response times and coordinate staff assignments across shared inboxes
Built-in capabilities (9)
Register a new contact
Get conversation history
Get details for a message
List active conversations
Supports filtering by phone number. List Heymarket contacts
List Heymarket workspace members
Requires member_id and to_number. Send an SMS or MMS message
Modify chat state or assignment
Modify an existing contact
Why Claude Code?
Claude Code registers Heymarket as an MCP server in a single terminal command. Once connected, Claude Code discovers all 9 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Heymarket data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Heymarket tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Heymarket in Claude Code
Heymarket and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Heymarket to Claude Code 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Heymarket in Claude Code
The Heymarket 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 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code 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.

* 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
How Vinkius secures
Heymarket for Claude Code
Every tool call from Claude Code to the Heymarket MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
