Formatix AI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORMATIX_API_KEY | No | Your Formatix API key (fxi_...). Without it, only the claim_access tool works. | |
| FORMATIX_API_BASE | No | Override the API base URL for testing against another environment. | https://platform.formatix.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_document_typesA | List the branded talent documents Formatix can generate — assessment reports (Hogan, psychometric, CEO & leadership), progression reports, candidate profiles, shortlists, client submittals, proposals and RPO reports — each with its available output formats (DOCX, PPTX, PDF, XLSX). Call this first to choose a template_id for |
| generate_documentA | Generate a branded, personalized talent document from candidate text. Works for any document type returned by |
| format_from_linkedinA | Turn a LinkedIn profile into a polished, branded resume or candidate profile. Paste the visible profile text as |
| check_statusA | Check whether a generated document is ready and get its download link. Status is 'Processing' (keep polling), 'Formatted' (ready — share the download_url with the client), or 'Failed - '. |
| claim_accessA | Get FREE Formatix access using your COMPANY email. Personal inboxes (gmail, outlook, yahoo, proton, etc.) are not eligible. Returns a free API key — treat it as a secret: store it as FORMATIX_API_KEY in your MCP config rather than leaving it in chat history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each of the five tools has a clearly distinct purpose: claiming access, listing document types, generating documents from text, formatting from LinkedIn, and checking status. No two tools overlap in functionality.
All tool names follow a consistent snake_case verb_noun pattern (e.g., claim_access, list_document_types, generate_document). The naming is uniform and predictable.
With only five tools, the server is well-scoped for a focused document generation service. Each tool serves an essential step in the workflow without extraneous or missing functions.
The tool surface covers the entire flow: access, template selection, document generation from two sources, and status polling. No obvious gaps for the stated purpose.