Functional Requirements MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_user_storyC | Create a structured user story based on provided context |
| generate_requirementsC | Generate structured requirements from a user story |
| get_user_storiesB | Retrieve all stored user stories |
| get_requirementsB | Retrieve all stored requirements |
| get_tasks_toolC | Retrieve all tasks from the task repo system. |
| create_taskC | Create a new task in the task repo system. |
| update_task_statusC | Update an existing task in the task repo system. |
| delete_taskC | Delete a task from the task repo system. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_technical_specification | Convert requirements into detailed technical specifications. |
| create_architecture_decision_record | Document technical decisions and rationale. |
| create_sequence_diagram_prompt | Generate PlantUML sequence diagrams from user story process flows. |
| create_architecture_overview | Generate comprehensive architecture documentation with multiple PlantUML diagrams. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: user stories (create/get), requirements (generate/get), and tasks (create/get/update status/delete). There is no overlap or ambiguity between any pair of tools.
Most tools follow a consistent verb_noun pattern in snake_case (create_user_story, get_user_stories, create_task, etc.). The tool 'get_tasks_tool' deviates by appending a redundant '_tool' suffix, which is a minor inconsistency.
Eight tools are well-scoped for managing user stories, requirements, and tasks. Each tool has a clear purpose and the count fits comfortably within the typical 3-15 range.
The server covers create and retrieve for user stories and requirements, and partial CRUD for tasks, but lacks update/delete operations for user stories and requirements, as well as task retrieval by ID or full task updates. These notable gaps limit lifecycle coverage.