PT-MCP (Paul Test Man Context Protocol)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_codebaseC | Perform comprehensive codebase analysis including structure, dependencies, and metrics |
| enrich_contextC | Enrich codebase context with knowledge graph data from YAGO 4.5 and Schema.org annotations |
| generate_contextC | Generate context files in specified format for the codebase |
| update_contextC | Incrementally update existing context files based on code changes |
| extract_patternsC | Identify and extract architectural and coding patterns from the codebase |
| analyze_dependenciesC | Analyze and map internal and external dependencies |
| watch_projectB | Start monitoring project for changes and auto-update context |
| extract_api_surfaceB | Extract and document public API surface of the codebase |
| validate_contextC | Validate accuracy and completeness of generated context files |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project Context | Current project context including structure, patterns, and dependencies |
| Detected Patterns | Architectural and coding patterns detected in the codebase |
| Dependency Graph | Internal and external dependency relationships |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdz-axo/pt-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server