Configure a Streamable HTTP MCP connection with:
URL: https://evasay.com/api/v1/voice/mcp
Authorization: Bearer <your EvaSay API key>
In Claude Code, for example:
claude mcp add --transport http evasay https://evasay.com/api/v1/voice/mcp --header "Authorization: Bearer $EVASAY_API_KEY"
The connection tells the tool how to build an agent: read the catalog, create a draft, add knowledge, functions and word lists, write tests and run them, fix the draft until they pass, give you the agent's dashboard_url to try it, and publish and route a number only once you approve. Tools that read docs can start from https://evasay.com/llms.txt, which links this page, the OpenAPI contract and the MCP address.
Use the client's secure token or environment-variable setting. The endpoint uses API-key authentication, not an OAuth login flow. It exposes the catalog, Agent creation and configuration, tests, library tools, knowledge, word lists, number routing, webhooks and call records. Publishing and placing real calls are write actions; outbound calls consume Credits and carrier fees. Every tool call rechecks workspace permissions. Enable your client's confirmation controls for write actions. The endpoint uses stateless JSON responses; it does not offer a background notification stream.
An example instruction for the coding tool is: “Build an EvaSay agent that answers my salon's phone in English and Spanish and books haircuts with my booking API. Write tests for booking, moving and cancelling, run them until they pass, then show me the agent's page to try it.” Review and explicitly authorize publication and real calls.