Statelessor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATELESSOR_API_URL | No | API endpoint for Statelessor | http://localhost:3001 |
| STATELESSOR_API_TIMEOUT | No | Request timeout in milliseconds | 300000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_git_repositoryC | Analyze a Git repository for stateful code patterns in .NET or Java projects |
| analyze_local_projectC | Analyze a local project directory for stateful code patterns |
| generate_analysis_scriptC | Generate a bash or PowerShell script for offline analysis |
| get_project_findingsC | Retrieve historical analysis findings for a project |
| explain_remediationC | Get detailed remediation guidance for a specific stateful pattern |
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 has a clearly distinct purpose: analyze_git_repository and analyze_local_project target different source locations, explain_remediation provides guidance, generate_analysis_script creates scripts, and get_project_findings retrieves historical data. No overlap or ambiguity exists between these functions.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., analyze_git_repository, explain_remediation, generate_analysis_script). The naming is predictable and readable throughout the set.
With 5 tools, the server is well-scoped for analyzing stateful code patterns. Each tool serves a unique and necessary function in the workflow, from analysis to remediation and historical retrieval, without being too sparse or bloated.
The toolset covers core analysis workflows (git/local analysis, remediation guidance, script generation, and findings retrieval). A minor gap exists in direct remediation actions (e.g., fixing patterns automatically), but agents can work around this using the provided guidance and scripts.