CTP MCP Server
Server 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 |
|---|---|
| ctp_create_toolB | Generate a complete CTP tool from a natural language description. Creates tool definition, implementation, and tests. |
| ctp_validate_toolB | Validate a tool definition against the CTP specification |
| ctp_generate_implementationB | Generate implementation code from a tool definition |
| ctp_generate_testsB | Generate test suite for a CTP tool |
| ctp_search_duplicatesC | Search for existing tools with similar functionality |
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 tool targets a distinct step in the CTP tool generation workflow: full creation, implementation, testing, duplicate search, and validation. There is no overlap in purpose.
All tool names follow a consistent pattern: 'ctp_' prefix followed by verb_noun (e.g., create_tool, generate_implementation). No mixing of styles.
With 5 tools, the server covers the essential stages of tool generation without being bloated. Each tool is necessary and well-scoped.
The tools cover creation, implementation, testing, validation, and duplicate detection. A list or delete tool might be useful but is not critical for the generator's purpose.