Overview
Poly-Glot AI Workspace is an AI productivity and localization platform for creating prompts, working across multiple AI providers, and comparing model responses. The product includes more than 1,000 prompt templates, multiple input methods, and a localized interface across 38 languages.
For developer and agentic workflows, Poly-Glot exposes functionality through the Model Context Protocol (MCP). An MCP-compatible assistant can discover templates, build prompts, select languages, check subscription state, prepare multi-model comparisons, and open the broader workspace.
Availability & Distribution
The Poly-Glot MCP server is deployed and available across multiple distribution surfaces:
Official MCP Registry
Listed on the Model Context Protocol Registry for discovery by MCP-compatible clients.
MCP.so
Published on MCP.so, a community directory of MCP servers and integrations.
Glama
Available on Glama for AI workflow orchestration and server discovery.
Hugging Face
Hosted on Hugging Face for model and tool ecosystem integration.
Awesome Remote MCP Servers
Listed on Awesome Remote MCP Servers, the curated community list of hosted MCP servers. PR #115.
This is not a hypothetical integration. The Poly-Glot MCP server is deployed, registered across multiple discovery surfaces, and actively serving requests.
Architecture
Poly-Glot separates the user-facing workspace from the MCP integration layer. The integration exposes focused tools that can be composed into agent workflows.
Developer / User
|
v
MCP-Compatible AI Assistant
|
| Model Context Protocol
v
Poly-Glot MCP Server
|
+---- search_templates
+---- get_template
+---- build_prompt
+---- prepare_compare
+---- get_language_options
+---- get_subscription_status
+---- open_workspace
+---- transcribe_audio
+---- detect_language
+---- translate_text
+---- localize_text
+---- get_custom_model_capabilities
+---- validate_custom_model
+---- run_custom_model
+---- prepare_custom_compare
|
v
Poly-Glot AI WorkspaceThis design reduces manual steps. Instead of locating a template, copying it, filling variables, and then setting up multiple model sessions, an agent can orchestrate those actions as tool calls.
MCP Endpoint
Poly-Glot publishes the following MCP endpoint for compatible clients:
https://br-steep-leaf-ae2o29qz-mcp.compute.c-2.us-east-2.aws.neon.tech/mcpUse this endpoint only with MCP-compatible clients that allow custom connectors.
MCP Tool Reference (15 Tools)
Poly-Glot exposes 15 primary tools through MCP: 7 interactive tools for template workflows, 4 language processing tools, and 4 Bring Your Own Model (BYOM) tools.
Interactive Tools (7)
search_templates
Searches the Poly-Glot prompt library by task or topic.
Find templates for writing a LinkedIn post.
Search for coding templates.
Find a template for salary negotiation.get_template
Retrieves the selected template after discovery. A common pattern is search_templates followed by get_template.
build_prompt
Populates a selected template using user-provided requirements and produces a completed prompt for downstream use.
prepare_compare
Prepares the same prompt for side-by-side evaluation across multiple AI providers. Poly-Glot Compare Mode supports workflows spanning 2 to 9 AIs.
get_language_options
Returns supported language options. Poly-Glot supports 38 languages across interface and output workflows.
get_subscription_status
Checks the user's current Poly-Glot plan or subscription state before gated functionality is used.
open_workspace
Transitions the user from an MCP-driven conversational workflow into the full Poly-Glot Workspace.
Language Processing Tools (4)
transcribe_audio
Transcribes supplied audio for cross-platform Poly-Glot workflows. Accepts an HTTPS audio URL or base64-encoded audio data. Supports optional language hints and language detection.
Transcribe this audio file for me.
Convert this voice memo to text.detect_language
Detects the language of supplied text and maps it to a supported Poly-Glot language. Useful for routing multilingual input to the correct workflow.
What language is this text in?
Detect the language before translating.translate_text
Translates text into a supported Poly-Glot language. Preserves meaning, formatting, names, code, and URLs.
Translate this email to Spanish.
Convert this paragraph to Japanese.localize_text
Localizes text for a target language, locale, audience, and tone — not merely literal translation. Adapts idioms, cultural references, and register for the target audience.
Localize this marketing copy for a German audience.
Adapt this message for a formal Japanese business context.Bring Your Own Model (BYOM) Tools (4)
get_custom_model_capabilities
Returns the capabilities and connection requirements for developer-controlled models, including supported BYOM endpoint patterns and Poly-Glot integration behavior.
validate_custom_model
Validates a developer-supplied HTTPS model endpoint before execution. Poly-Glot applies endpoint safety checks and does not persist raw provider API keys in Neon.
run_custom_model
Runs a Poly-Glot prompt against a developer-controlled model while preserving Poly-Glot prompt construction, localization, entitlement, and orchestration workflows.
prepare_custom_compare
Prepares a Compare Mode workflow that can include a developer-controlled model alongside supported built-in AI providers.
Bring Your Own Model (BYOM)
BYOM extends the same Poly-Glot MCP platform to developer-controlled models. Teams can connect private, fine-tuned, self-hosted, enterprise, or third-party models and use them with Poly-Glot prompt workflows, 38-language localization, and Compare Mode.
OpenAI-compatible endpoints
Connect compatible hosted models by providing the endpoint, model identifier, and transient credentials required for the request.
Custom HTTPS REST endpoints
Poly-Glot can adapt supported developer endpoints while enforcing HTTPS, request limits, endpoint validation, and safe redirect behavior.
Compare with your own model
Use prepare_custom_compare to evaluate a BYOM model alongside supported Poly-Glot providers using the same prompt and localization context.
Credential privacy
Raw API keys, bearer tokens, and authorization headers are not stored in ordinary Neon database tables. Credentials are supplied transiently or through an approved secrets mechanism.
BYOM request path
Developer / MCP Client
|
v
Poly-Glot MCP Server
|
+---- prompt building + localization
+---- endpoint validation + entitlements
+---- BYOM adapter
|
v
Developer-Controlled Model Endpoint
|
v
Poly-Glot Compare / Response Workflow
Neon stores configuration, entitlement state, and analytics metadata.
Raw provider credentials are not persisted.
Localhost, .local, loopback, RFC1918/private-network, link-local, and cloud metadata endpoints are blocked from the public remote MCP path. A local/private model must be exposed through a secure supported HTTPS endpoint or a future local bridge.
Example: Build a Developer Prompt
A user can describe an outcome without knowing the underlying tool names:
Search Poly-Glot for LinkedIn templates and build me
one about AI productivity.User request
|
v
search_templates
|
v
get_template
|
v
build_prompt
|
v
Completed promptThe agent handles template discovery and construction while the user remains focused on the desired outcome.
Example: Compare Multiple Models
After building a prompt, a user can extend the workflow:
Now compare that across ChatGPT, Claude, and Gemini.The agent can invoke prepare_compare and stage the prompt for the selected providers.
User
|
| "Compare it across ChatGPT, Claude, and Gemini."
v
prepare_compare
|
v
Poly-Glot Workspace
|
+---- ChatGPT
+---- Claude
+---- Gemini
|
v
Human evaluationThis preserves human judgment at the end of the workflow: the system prepares alternatives, but the user decides which response best satisfies the task.
Localization Workflow
Localization is a first-class workflow rather than an output-only translation step. Poly-Glot distinguishes between application language and requested AI output language.
User intent
|
v
get_language_options
|
v
Select supported language
|
v
search_templates
|
v
get_template
|
v
build_prompt
|
v
AI workflowThis allows multilingual behavior to be incorporated into orchestration rather than added only after content generation.
Privacy and Execution Model
The native Poly-Glot application is designed around local workflows. MCP integrations introduce an external assistant and MCP service into the execution path, so developers should evaluate the privacy and data-handling policies of the client and AI provider they use.
Native workflow
User --> Poly-Glot --> User-selected AI experience
MCP workflow
User --> MCP Client --> Poly-Glot MCP Server
|
+--> AI assistantIntegration Design Principles
Intent over implementation
Users state goals while the agent selects and sequences tools.
Composable tools
Discovery, retrieval, construction, localization, comparison, entitlement, and workspace access remain separate capabilities.
Human in the loop
Multi-model comparison preserves human evaluation instead of assuming a single model is always best.
Progressive interaction
A task can begin conversationally and transition into the full workspace when a richer interface is useful.
Troubleshooting
Poly-Glot tools do not appear
Confirm that the MCP endpoint is correct and that the connector is enabled in the client.
A template cannot be found
Use a broader, task-oriented search rather than an exact template title.
Find a template for creating developer documentation.Compare Mode does not include the expected provider
Confirm that the intended providers were selected when the comparison was prepared.
The requested language is unavailable
Use get_language_options to determine currently supported languages.
A feature is unavailable for the current account
Use get_subscription_status before proceeding with gated functionality.
Developer Workflow Summary
1. Receive user intent
|
2. Discover template -> search_templates
|
3. Retrieve template -> get_template
|
4. Determine language -> get_language_options
|
5. Detect input language -> detect_language
|
6. Construct prompt -> build_prompt
|
7. Translate output -> translate_text
|
8. Localize output -> localize_text
|
9. Transcribe audio input -> transcribe_audio
|
10. Prepare providers -> prepare_compare
|
11. Open workspace -> open_workspace
|
12. Compare outputs
|
13. Human selects resultThis architecture turns a prompt library into a set of agent-accessible, composable capabilities while preserving human control over the final output.
About This Sample
Poly-Glot AI Workspace: Developer Integration Guide is an independent technical writing sample based on the publicly documented Poly-Glot AI Workspace product and MCP integration.
It demonstrates developer documentation, information architecture, procedural documentation, conceptual documentation, API/tool reference organization, AI workflow documentation, localization concepts, and docs-as-code-oriented content design.
Author: Harold Moses II
Product: Poly-Glot AI Workspace
Reference: hmoses.github.io/poly-glot-site
Developer DocsMCPAgentic AIDocs-as-CodeLocalizationMulti-Model Workflows