mcp-ecosystem

This MCP server collection provides configurable contexts for AIOS-related workflows, including context7 for up-to-date LLM documentation, desktop-commander for file and terminal operations, playwright for browser automation, and exa for AI-powered web search and content extraction. Each server is exposed as an MCP endpoint that can be consumed by your IDEs or tooling that support the MCP protocol. To get started, run the corresponding container (or deploy the server in your preferred environment) and point your MCP client at the server endpoints defined in each server’s JSON configuration. The presets in the repository help you quickly assemble multi-server configurations for development, research, or full-task pipelines.

Prerequisites:

• Docker installed and running (or your preferred container runtime).
• Access to the repository files (clone or download).

Step-by-step:

1. Install dependencies if you’re running locally outside of Docker (optional for native runtimes): ensure you have Docker and your MCP client configured.
2. Review the server JSON files under mcp-ecosystem/servers to understand the exact endpoint names and any required API keys.
3. Start each MCP server instance:
   • For Docker-based runs, use the following example commands (adjust image names as needed): docker run -i mcp-ecosystem-context7 docker run -i mcp-ecosystem-desktop-commander docker run -i mcp-ecosystem-playwright docker run -i mcp-ecosystem-exa
4. If you’re using a non-Docker runtime, adapt the commands to launch the respective servers, ensuring they point to the JSON configurations located in servers/ (e.g., servers/context7.json).
5. Configure your MCP client (IDE config or CLI) to point to the running server endpoints. Use the environment variables documented in each server config if keys or API keys are required.

Notes and tips:

• The exa server requires an API key (EXA_API_KEY). Set this in the environment or provide via your MCP client configuration.
• Some servers may expose different types (SSE vs stdio). Ensure your MCP client supports the corresponding transport type.
• If you update any server JSON, restart the corresponding container or process to apply changes.
• The repository includes presets (aios-dev, aios-research, aios-full) to compose multi-server configurations quickly; choose one based on your task scope.
• For IDE integrations (Claude Code, Cursor), you can copy the sample configs from ide-configs to your editor’s configuration and merge them with your existing setup.