Connect the Speechify MCP server

Ask grounded questions about the Speechify API, SDKs, and docs from inside your editor or agent

Speechify hosts a Model Context Protocol (MCP) server at https://mcp.speechify.ai/mcp. Connect it to your AI coding tool to ask grounded questions about the Speechify API, SDKs, code samples, and docs — with citations — without leaving your editor.

This server answers questions about Speechify. It exposes two tools — ask (grounded answers with citations) and search (ranked source passages) — and the search half is also reachable over plain HTTP with no MCP client. It does not generate speech: for text-to-speech, use the API or the official SDKs.

Connect the Speechify MCP server
Connect Speechify’s hosted MCP server ([https://mcp.speechify.ai/mcp](https://mcp.speechify.ai/mcp)) to my coding tool, then verify it by asking how to stream text-to-speech audio with the Speechify API and confirming the answer cites the Speechify docs. Follow [https://docs.speechify.ai/build/guides/get-started/connect-mcp.md](https://docs.speechify.ai/build/guides/get-started/connect-mcp.md).

What you get

Endpointhttps://mcp.speechify.ai/mcp
TransportStreamable HTTP
AuthNone required — the server is public. An API key is optional and only forwarded for future authenticated tools.
Toolsask, search
Plain HTTPhttps://mcp.speechify.ai/v1/search?q=<question> — the search tool without an MCP client. No key. 30 requests per minute per IP.

Set up with the Speechify CLI

If you use the Speechify CLI, it detects your installed clients and writes the config for you:

speechify mcp install --client claude-code # or: cursor | vscode | windsurf | claude-desktop
speechify mcp install --all # every detected client
speechify mcp install --print # print the config, write nothing

To configure a client by hand, use the sections below.

Claude Code

claude mcp add --transport http ask-speechify https://mcp.speechify.ai/mcp

Cursor

Add the server to ~/.cursor/mcp.json:

{
"mcpServers": {
"ask-speechify": {
"type": "http",
"url": "https://mcp.speechify.ai/mcp"
}
}
}

VS Code

Add the server to your VS Code mcp.json (used by Copilot):

{
"servers": {
"ask-speechify": {
"type": "http",
"url": "https://mcp.speechify.ai/mcp"
}
}
}

Windsurf

Add the server to ~/.codeium/windsurf/mcp_config.json:

{
"mcpServers": {
"ask-speechify": {
"type": "http",
"url": "https://mcp.speechify.ai/mcp"
}
}
}

Claude Desktop

Add the server to your Claude Desktop config (claude_desktop_config.json):

{
"mcpServers": {
"ask-speechify": {
"type": "http",
"url": "https://mcp.speechify.ai/mcp"
}
}
}

Config file locations:

OSPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json

For a client without native remote (Streamable HTTP) support, the speechify mcp command runs a local stdio relay that forwards to the hosted server. Point the client at the command instead of the URL:

{
"mcpServers": {
"speechify": {
"command": "speechify",
"args": ["mcp"]
}
}
}

Plain HTTP, no MCP client

If your agent can make an HTTP request but is not wired to speak MCP, query the retrieval engine directly. A GET to https://mcp.speechify.ai/v1/search returns the same ranked source passages the search tool returns, as JSON. There is no synthesis — you get the grounding, and your own model does the reasoning. No key is needed, and the endpoint is rate-limited to 30 requests per minute per IP.

Query parameter
qrequiredThe question, 1–500 characters.
limitoptionalPassages to return, 1–20. Default 8.
import requests
response = requests.get(
"https://mcp.speechify.ai/v1/search",
params={"q": "which output_format should I use for telephony?", "limit": 5},
timeout=30,
)
response.raise_for_status()
for hit in response.json()["hits"]:
print(f"{hit['score']:.2f} {hit['title']} {hit['url'] or '(reference)'}")
print(hit["body"][:200], "\n")

The response echoes the query and returns the passages best first:

{
"query": "which output_format should I use for telephony?",
"hits": [
{
"id": "",
"title": "Create Speech (Build › API Reference › Text to Speech)",
"url": "https://docs.speechify.ai/build/api-reference/v1/audio/speech",
"source": "db",
"score": 0.72,
"body": ""
}
]
}

Each hit carries a url you can cite when the passage comes from a public page. Reference passages drawn from the API specification have no page of their own, so their url is null — quote the body, and cite the API reference instead. Bodies are truncated at 1,200 characters; fetch the url (append .md for clean Markdown) when you need the whole page.

When the engine answers an ask question, it closes with a Sources list. Those are the same passages this endpoint returns for the same question, so an agent that already has HTTP access can reproduce the grounding without installing anything.

Verify the connection

Restart your client, then ask it something only the docs would know, for example:

How do I stream text-to-speech audio with the Speechify API?

The client should call the ask tool and answer with citations to the Speechify docs.