What Poly-Glot MCP does, its tools, setup documentation and compatible client requirements.
Poly-Glot provides a hosted Streamable HTTP Model Context Protocol server with tools for template discovery, prompt building, comparison preparation, BYOM, language and audio processing, and subscription status. Read-only discovery does not start a trial; Send and restricted tools use verified server-side entitlements.
The current MCP server code registers 15 tools: seven core tools, four BYOM tools, and four language and audio tools. Discovery depends on client support and permissions; some tool actions require an authenticated trial or Pro account.
get_language_optionsget_subscription_statusopen_workspacesearch_templatesget_templatebuild_promptprepare_compareget_custom_model_capabilitiesvalidate_custom_modelrun_custom_modelprepare_custom_comparetranscribe_audiodetect_languagetranslate_textlocalize_textNot necessarily. A client must support the appropriate MCP transport and authentication or connection configuration. Consult the client-specific setup instructions.
See the MCP setup section on the Poly-Glot homepage for the production endpoint and integration overview.
MCP connection support
Step-by-step fixes for remote Streamable HTTP connections in ChatGPT, Claude, Cursor, Goose, VS Code, Windsurf and other compatible MCP clients. All clients use the same Poly-Glot server, with 15 tools across templates, comparison, custom models, and languages.
https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcp
/mcp; do not paste a Glama, MCP.so or GitHub directory URL.get_language_options or search_templates; then use get_subscription_status to check trial and Pro availability.In a Claude chat, click + → Connectors, enable Poly-Glot, then ask Claude to use a named tool. Review and approve tool requests when prompted.
Use Poly-Glot's search_templates tool to find LinkedIn templates for AI productivity.Find an accessible LinkedIn template in Poly-Glot and use build_prompt to write about AI productivity.Use Poly-Glot's prepare_compare tool to prepare this prompt for ChatGPT, Claude, and Gemini.Searching templates is read-only. build_prompt and prepare_compare are Send actions; Compare Mode requires an active trial or Pro. prepare_compare returns a prompt and destinations, not completed AI responses.
Illustrative Claude response — not a live resultPoly-Glot prepared your prompt for ChatGPT, Claude, and Gemini. It has not opened the workspace or generated any model responses. Use the returned destinations to send the prompt and compare answers.
Use the Apps or developer/custom MCP configuration available to your account or workspace. Add the remote URL, complete any authorization, scan tools and select the app in your chat. App and developer-mode availability varies by plan and workspace permissions.
Official client help ↗In Claude, open Customize → Connectors, select + Add → Add custom connector, enter Poly-Glot and the production URL, and approve requested permissions. Enable Poly-Glot using the + → Connectors menu in a chat.
Official client help ↗Open your MCP server settings, add a remote Streamable HTTP server using the endpoint above, and enable it. If no tools are listed, refresh the MCP servers, approve permissions and verify the client supports this transport.
Add Poly-Glot as a remote MCP extension using Streamable HTTP rather than a local command. Enable the extension, restart its session if necessary and test a read-only tool before trying Send or custom-model tools.
In an MCP-capable VS Code setup, add the URL as an HTTP remote MCP server, not a local stdio process. Check workspace trust and tool approvals, then refresh the server and confirm tool discovery.
Confirm your client's version supports remote Streamable HTTP MCP servers. Use the production URL and enable its tools; if your client supports only stdio or legacy SSE, consult its current remote-MCP documentation.
Verify the full https://…/mcp URL and remote HTTP transport. Re-add the connection and try again. A browser GET to an MCP endpoint is not a valid tool test; the client must use the MCP protocol. Check the client network and the server health endpoint; do not mistake a directory listing for the server.
Use the client's account authorization flow and reconnect if the session expires. Check the server's authentication requirements and client permissions. Never paste Apple passwords, API tokens or subscription receipts into public chats, screenshots or issue reports.
Confirm the client granted this connector permission to use the requested tool. Ask the workspace admin about policies if necessary. A 403 may also reflect an authentication or origin-policy restriction—not necessarily an expired subscription.
Enable the connector and refresh or rescan tools. The current server documents 15 tools. Outdated directory summaries do not change the live tool registry. Try get_language_options; check that your MCP client can discover remote tools.
Use get_subscription_status to inspect current access. The app-managed three-day trial starts on the first qualifying Send; after expiry, free access includes 25 featured templates and one single-AI Send per rolling 24 hours. Compare Mode, BYOM and other Pro features require appropriate access. To resolve a paid-access mismatch, sign in with the linked account and verify or restore your Apple subscription in the app.
Retry after a short delay and check the client's network, any proxy or firewall, and server status. Avoid repeating a paid or Send action until you have checked whether the previous request completed. Include the time, MCP client and error code in a support request—never include secrets.
Use get_language_options to choose a supported language, then verify input and output language settings. For transcribe_audio, confirm the audio format, size and permissions match tool requirements. Try detect_language or translate_text separately to isolate the issue.
First call get_custom_model_capabilities, then validate_custom_model. Use a reachable HTTPS model endpoint, the correct adapter and model identifier, and a valid temporary credential. Check your model provider's API response. Do not share API keys in logs or support messages.
Test the smallest read-only operation before a Send action. These groups cover all 15 Poly-Glot MCP tools.
get_language_options, get_subscription_status, open_workspace, search_templates, get_template, build_prompt, prepare_compareget_custom_model_capabilities, validate_custom_model, run_custom_model, prepare_custom_comparetranscribe_audio, detect_language, translate_text, localize_textStill need help? Share your MCP client, transport type, tool name, exact error code and approximate time—never passwords or API keys. Contact Poly-Glot support → View setup and compatibility → Read the RAG-friendly Markdown guide →
Four client-specific setup paths. Add the same hosted Streamable HTTP URL; directory listings are discovery pages, not server endpoints.
Open Cursor → Customize → MCPs, or edit the JSON file shown. Add this remote server, then refresh MCP tools.
Configuration: ~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
{
"mcpServers": {
"poly-glot": {
"url": "https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcp"
}
}
}Use Goose Extensions → Add custom extension, or the CLI command shown; select remote Streamable HTTP (not stdio).
Configuration: goose configure → Add Extension → Remote Extension (Streamable HTTP)
goose session --with-streamable-http-extension "https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcp"Run MCP: Add Server, select HTTP, or save the JSON file shown. Start the server and approve trust/tool permissions.
Configuration: .vscode/mcp.json (VS Code-specific workspace config)
{
"servers": {
"poly-glot": {
"type": "http",
"url": "https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcp"
}
}
}In Cascade, open the MCP/Plugins configuration and edit the global JSON file shown. Save and refresh MCP tools.
Configuration: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"poly-glot": {
"serverUrl": "https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcp"
}
}
}Verification: configuration syntax and client documentation have been reviewed; these are not claims of successful end-to-end testing in each installed desktop app. After connecting, test the read-only get_language_options or search_templates tools. Sign-in, tool approvals, and paid-feature access can vary by client and account.