pyfmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYFMCP_HOST | No | Host for HTTP transport (e.g., 127.0.0.1). Required when transport is 'http'. | |
| PYFMCP_PORT | No | Port for HTTP transport (e.g., 8000). Required when transport is 'http'. | |
| PYFMCP_ROOT_DIR | No | Project root directory. Defaults to the current directory. | |
| PYFMCP_TRANSPORT | No | Transport protocol: 'stdio' (default) or 'http'. | stdio |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| basedpyrightC | Run basedpyright diagnostics |
| pytestC | Run pytest and return its JUnit XML report. |
| ruff_lintC | Run Ruff diagnostics |
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 aspect of Python development: type checking (basedpyright), testing (pytest), and linting (ruff_lint). There is no functional overlap between them, making selection unambiguous.
Two tools use the bare command name (basedpyright, pytest) while ruff_lint appends a descriptor. This is a minor deviation, but the naming is still predictable since each tool is recognizable by its underlying tool name.
Three tools is well-scoped for a Python development server covering static analysis, linting, and testing. Each tool has a clear purpose and the count is appropriate for the domain.
The set covers the core development loop of type checking, linting, and testing. A formatter or build tool could be added, but the current coverage is typical and workable for most Python projects.