PEP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_TRANSPORT | No | The transport mechanism to use, typically set to 'stdio' for standard input/output communication. | |
| FASTMCP_SHOW_SERVER_BANNER | No | Determines whether to show the startup banner. Setting this to 'false' is often required to prevent banner text from interfering with the stdio JSON-RPC stream. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pepsA | List active Python PEPs with compact metadata. |
| search_pepsB | Search active PEP titles for a query string. |
| get_pepA | Get a PEP by number. Use Pass |
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
The three tools have clearly distinct purposes: 'get' retrieves a specific PEP by number, 'list' enumerates all active PEPs, and 'search' finds PEPs by title query. No functional overlap exists between them.
All tools follow a consistent snake_case verb_noun pattern (get_pep, list_peps, search_peps). The pluralization appropriately matches the return cardinality (singular for single retrieval, plural for collection operations).
Three tools is the ideal minimum for a read-only document server, covering the essential access patterns: enumeration, search, and specific retrieval. The scope is tightly focused without bloat.
While the basic read operations are present, notable gaps exist: list_peps and search_peps are restricted to 'active' PEPs only with no way to access other statuses, search_peps only searches titles (not content or authors), and there are no filtering options for metadata like author or Python version.