EIP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Google Gemini API key required for the EIP MCP server to function. |
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 |
|---|---|
| initialize_local_ssotB | Connects to the ESSOT Web App, pulls initial business requirements (SRD) and scaffolds the local knowledge/ directory. |
| generate_implementation_planC | Acts as the Software Architect. Reads local SSOT artifacts and generates a massive, professional-grade implementation-plan.md. |
| generate_task_planC | Generates an exhaustive Task Plan and saves it to the local workspace. |
| generate_test_planC | Generates an exhaustive Test Plan and saves it to the local workspace. |
| synchronize_ssotA | Called by the IDE Coding Agent to synchronize local SSOT changes with the ESSOT Web App. Reads the local ssot/ directory, determines what has changed, and pushes the updates back to the cloud database and Knowledge Graph. Args: update_summary: A brief description of what was changed locally during development. |
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
Tools mostly target distinct artifacts: task plan, implementation plan, test plan, and SSOT synchronization. generate_task_plan and generate_implementation_plan could potentially be confused since both produce planning documents, but their descriptions clarify the output differences.
All tools follow a consistent snake_case verb_noun pattern: generate_*, initialize_*, synchronize_*. This makes the set predictable and easy to navigate.
Five tools is well-scoped for a planning-and-sync workflow. Each tool has a clear role and there is no obvious redundancy.
The core lifecycle is covered: initialize SSOT, generate task/implementation/test plans, and synchronize changes. Minor gaps exist, such as no explicit update/retrieve tool for existing plans, but agents can likely work around this through the local workspace.