silverstripe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PHP_BINARY | No | Path to PHP 8.3+ executable (auto-detected if not specified) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ss-validatorA | Analyzes PHP code for Silverstripe 6 compatibility issues. MUST be called on any generated Silverstripe PHP code before presenting to the user. Keep calling until no issues remain. Detects:
|
| list-sectionsA | Lists available Silverstripe 6 changelog sections. Use this to discover what documentation is available before fetching with get-documentation. |
| get-documentationA | Fetches Silverstripe 6 changelog documentation for a specific section. Call list-sections first to see available sections. |
| search-changelogA | Search the SS6 changelog for specific terms. Use this when you need to find information about a specific class, method, or feature that may not be in the themed documentation sections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| silverstripe-task | Initialize a Silverstripe development task with documentation context |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: listing changelog sections, fetching specific documentation, searching the changelog, and validating PHP code. No two tools overlap in functionality, making selection unambiguous.
Three tools follow a consistent verb_noun pattern (list-sections, get-documentation, search-changelog), but ss-validator breaks the pattern as a noun phrase. This is a minor deviation in an otherwise predictable naming scheme.
With only 4 tools, the server is tightly scoped to its stated purpose of Silverstripe 6 migration assistance. Each tool earns its place, covering documentation access and code validation without redundancy.
The tool set provides a complete lifecycle: discover sections, retrieve documentation, search for terms, and validate code. No obvious gaps exist for the domain of Silverstripe 6 compatibility checking.