Phaset Manifest Generator MCP
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_phaset_schemaA | Get the Phaset integration API schema (RecordUpdate structure) for manifest generation |
| collect_repo_filesA | Collect relevant files from a repository for Phaset manifest analysis. Returns file contents that can be analyzed to generate a manifest. |
| suggest_manifestA | Analyze a repository and generate a Phaset manifest suggestion. This orchestrates schema retrieval and file collection, then provides them for AI analysis. |
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 has a clearly distinct purpose: collecting files, retrieving schema, and generating manifest suggestions. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (collect_repo_files, get_phaset_schema, suggest_manifest), making them predictable and easy to understand.
Three tools is appropriate for a focused manifest generation server; each tool serves a necessary step in the workflow without excess or deficiency.
The tool set covers the full manifest generation process: data collection, schema retrieval, and suggestion generation. No obvious gaps for the stated purpose.