Echo AI vs Prompts.chat MCP
A side-by-side look at the Echo AI and Prompts.chat MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Echo AI for conversational ai work over a hosted endpoint; choose Prompts.chat MCP for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Echo AI when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_echos, get_echo, get_embed_snippet.
Choose Prompts.chat MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROMPTS_API_KEY, PROMPTS_QUERY. - You want tools like
search_prompts, get_prompt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 48/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PROMPTS_API_KEYPROMPTS_QUERY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 36 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | 2 |
| Full listing | View Echo AI | View Prompts.chat MCP |
Tools & capabilities
Echo AI tools 8
list_echoslist the Echos the connected account can accessget_echofull configuration for one Echoget_embed_snippetcopy-paste widget embed code for an Echoget_headless_integrationfull headless build guide: REST API, streaming chat, commerce, booking, tickets, voice and a ready React componentget_echo_analytics_summaryconversations, messages and usage summarylist_recent_conversationsrecent chat sessions for an Echoget_conversation_historymessages in one conversationsend_message_to_echochat with an Echo (consumes the owner's Echo AI credits)
Prompts.chat MCP tools 2
search_promptsSearch for AI prompts by keyword. Returns matching prompts with title, description, content, author, category, and tags.get_promptGet a prompt by ID. If the prompt contains template variables (like ${variable} or ${variable:default}), you may need to provide values for them.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Echo AI
{
"mcpServers": {
"echo-ai": {
"url": "https://auth.echoai.so/functions/v1/mcp"
}
}
}
Prompts.chat MCP
{
"mcpServers": {
"prompts-chat-mcp": {
"command": "npx",
"args": [
"-y",
"@fkadev/prompts.chat-mcp"
],
"env": {
"PROMPTS_API_KEY": "YOUR_PROMPTS_API_KEY_HERE",
"PROMPTS_QUERY": "YOUR_PROMPTS_QUERY_HERE"
}
}
}
}
Frequently asked questions
Echo AI is categorized under Conversational AI and uses a remote HTTP/SSE transport. Prompts.chat MCP belongs to Conversational AI and uses a local stdio subprocess. Pick Echo AI for conversational ai work and Prompts.chat MCP for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Echo AI has no declared pricing — check the project's own site. Prompts.chat MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add echo-ai and prompts-chat-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Echo AI has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Prompts.chat MCP has 55/100 (Good) with 3 views, 0 installs and 36 GitHub stars.