POEM MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| poem_readA | Read and parse a .poem file into structured elements (constants, structs, functions, etc). Returns the parsed structure so you can understand, discuss, or translate the spec. Use this when someone shares a .poem file or asks about its contents. |
| poem_validateA | Validate a .poem file for syntax correctness and convention compliance. Checks: brace balance, naming conventions (UPPER_SNAKE for constants, snake_case for functions, PascalCase for types), and structural completeness. Returns errors (must fix), warnings (should fix), and stats. |
| poem_translateA | Prepare a .poem spec for translation to a target language. Parses the POEM, validates it, and returns a structured translation brief. YOU (the LLM) then use this brief to generate idiomatic code in the target language. The tool handles parsing and validation. You handle the translation. Supported targets: any programming language (python, typescript, go, rust, java, sql, swift, kotlin, etc). |
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 3 tools
Each tool targets a distinct operation: read parses and returns structure, validate checks correctness, and translate prepares for conversion. There is no overlap in their purposes, making selection unambiguous.
All tools follow a consistent 'poem_verb' pattern with clear, specific verbs (read, validate, translate). Naming is predictable and uniform in snake_case.
Three tools is well-scoped for a specialized POEM handling server, covering the core needs of parsing, validation, and translation. Each tool earns its place without redundancy.
The set covers the primary lifecycle of reading, validating, and translating POEM specs. Minor gaps like a create/edit tool are outside the apparent focus, so the surface is mostly complete for its stated purpose.