Set up Vapi
Vapi’s developer platform for AI voice agents. Add Agentcy as an MCP tool so your voice assistants can pull live marketing data during calls — perfect for outbound campaigns, customer surveys, and sales discovery calls grounded in real client data.
- 01
Sign up at app.goagentcy.com and create an API key
- 02
Sign in to your Vapi dashboard
- 03
Go to Tools → Create Tool
- 04
Select MCP from the available tool types
- 05
serverUrl: https://data.goagentcy.com/mcp
- 06
Add a custom header — Name: Authorization, Value: Bearer YOUR_AGENTCY_API_KEY
- 07
Save the MCP tool
- 08
Go to Assistants → select your assistant → Tools tab
- 09
In the tools dropdown, select your Agentcy MCP tool
- 10
Save the assistant. Vapi connects to Agentcy at the start of each call, fetches available tools, and adds them dynamically to the assistant.
path: Tools → Create Tool → MCP
# Remote MCP Server (OAuth)
# No config file needed — connect through your client's UI
Server URL: https://data.goagentcy.com/mcp
Authentication: OAuth
When prompted, enter your Agentcy API key (agcy_...)
Find your key at: app.goagentcy.com → Settings → API KeysBEST FIT: focused, single-question queries. Agentcy returns plain-English answers (“Your bounce rate this month is 42%, up 3% from last month…”) which the voice agent’s LLM interprets and converts back to speech. Keep prompts narrow — verbose Agentcy responses can introduce perceptible voice latency. Vapi connects to your MCP server at the start of each call/chat using Streamable HTTP, fetches available tools, and adds them dynamically to the assistant. Each tool invocation creates a new connection with X-Call-Id and X-Chat-Id headers. Treat your MCP server URL as a credential. Vapi pricing is per-call-minute; check the Vapi dashboard for current pricing. AUDIENCE NOTE: This integration targets developers building voice agents — not marketers using Vapi directly. Agencies building voice automation for clients (outbound calls, surveys, support) can use Agentcy to give those voice agents real marketing context (“Is this caller a high-value customer?” “What campaign drove their last visit?”).
Stuck or want to verify these instructions yourself? These are the documentation sources we used. If something here doesn't match what you see in your client, the vendor may have updated their UI — and we'll get this page updated.