Ecosystem Intelligence MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ecosystem Intelligence MCP analyze the project in ~/dev/myapp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ecosystem Intelligence MCP
A sellable prototype for bounded, read-only understanding of local project directories. It is designed to help an AI assistant inventory projects, identify technology markers, and read selected text files without executing code or exposing arbitrary filesystem paths.
Product documents
Related MCP server: Local Code MCP Server
Tools
inventory_roots— shows the configured allowlist.summarize_project— bounded directory structure, file counts, extensions, markers, and representative text-file paths.read_project_file— reads a small recognized text/project file under an approved root with sensitive-path filtering and redaction.analyze_project— infers purpose and capabilities from bounded evidence, with confidence, readiness, unknowns, and safety metadata.
It also exposes ecosystem://policy as a resource describing the safety model.
Run locally
npm install
ECOSYSTEM_ROOTS="$HOME/Documents" npm startThe server communicates over MCP stdio. It does not execute project code, mutate files, follow symlink escapes, inspect unconfigured roots, or read arbitrary binary files. Common sensitive paths are excluded and common secret patterns are redacted.
Package direction
manifest.json is MCPB-ready for a future downloadable bundle. Before selling, add signed release artifacts, a privacy policy, support documentation, a second platform test, and a hosted/paid tier only after validating demand.
Product boundary
The commercial moat should be the interpretation layer: project-purpose extraction, capability overlap, maturity scoring, and actionable productization recommendations. Keep those higher-level features separate from the local filesystem adapter so the product can later support uploaded manifests, Git repositories, or a hosted service.
Available Tools
4 toolsanalyze_projectAnalyze a projectARead-only
Infer a project purpose and capabilities from bounded local evidence, with confidence, evidence paths, readiness, and safety details.
Inputs: path (required).
inventory_rootsInventory approved rootsARead-only
List the explicitly configured directories this server is allowed to inspect. Does not scan file contents.
Inputs: no named parameters.
read_project_fileRead a project fileARead-only
Read a small recognized text file inside an approved root with sensitive-path filtering and redaction.
Inputs: path (required).
summarize_projectSummarize a projectARead-only
Return a bounded, read-only structural summary for a directory inside an approved root.
Inputs: path.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Static PyPI artifact/source import-layout evidence; no installs, execution, or resolver claims.
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides sandboxed access to local filesystem operations including directory and file management, content search with glob and regex patterns, and binary file support with configurable safety limits.-
- FlicenseBqualityDmaintenanceProvides LLMs with safe, read-only access to local codebases for searching, reading files, and finding function definitions. All source code remains local, ensuring privacy while enabling AI assistants to explore project structures and functionality.4-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with secure, read-only file system access to analyze and understand project codebases, enabling multi-repository context aggregation and cross-project code tracing.17 PyPI5MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely read and search project files within a configured root directory, supporting regex search, file listing, line-range reading, and symbol usage lookup.-