Ecosystem Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECOSYSTEM_ROOTS | Yes | The filesystem root (or roots) to allowlist for the ecosystem intelligence server. Example: "$HOME/Documents". |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inventory_rootsA | List the explicitly configured directories this server is allowed to inspect. Does not scan file contents. |
| summarize_projectA | Return a bounded, read-only structural summary for a directory inside an approved root. |
| read_project_fileA | Read a small recognized text file inside an approved root with sensitive-path filtering and redaction. |
| analyze_projectA | Infer a project purpose and capabilities from bounded local evidence, with confidence, evidence paths, readiness, and safety details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_policy | The local safety and privacy policy for this MCP server. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing roots, summarizing projects, reading files, and analyzing project purpose. There is no overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern in snake_case (inventory_roots, summarize_project, read_project_file, analyze_project). This makes the API predictable and easy to navigate.
With only 4 tools, the server is tightly scoped to its purpose of inspecting and analyzing projects. Each tool is essential and there is no bloat.
The tool surface covers the full workflow: discover roots, summarize structure, read specific files, and derive an analysis. No obvious missing operations for the stated domain.