mcp-builder-community
The MCP server for the MCP Server Builder Community
claude mcp add --transport stdio michael-watson-mcp-builder-community-server docker run -it --env-file .env -p 5000:5000 mcp-server-builder-series-mcp
How to use
This MCP server setup provides two containers: the MCP service container and the Router/container that complements the MCP server. The MCP container runs the Apollo MCP server binary configured to read environment-based credentials, while the Router handles request routing for your GraphOS-driven MCP endpoints. To use, create a local .env file with your Apollo credentials, then start both containers so they can communicate and expose their endpoints. The recommended flow is to build both images from the provided Dockerfile setup and then run them with the environment variables loaded from .env. Once running, you can query the MCP endpoints and test your GraphOS-based MCP integration through the exposed ports (default 5000 for MCP and 4000 for Router in this setup).
How to install
Prerequisites:
- Docker installed on your system
- Access to the repository with the provided Dockerfiles (mcp.Dockerfile) for building the images
- Apollo GraphOS keys for MCP server usage
Step-by-step:
-
Prepare your environment file with Apollo credentials
- Create a .env file in the project directory: APOLLO_KEY=service:cfp-<your-key>:... APOLLO_GRAPH_REF=cfp-<your-key>@current
-
Build the MCP and Router images
- docker build --tag mcp-server-builder-series-mcp -f mcp.Dockerfile .
- docker build --tag mcp-server-builder-series-router -f mcp.Dockerfile .
- Optional: use --build-arg BUILD_ENV=local for local development variants
-
Run the containers with your environment variables
- docker run -it --env-file .env -p 5000:5000 mcp-server-builder-series-mcp
- docker run -it --env-file .env -p 4000:4000 mcp-server-builder-series-router
-
Verify operation
- Access the MCP server at http://localhost:5000 (MCP) and router at http://localhost:4000 (Router)
- Ensure the .env file is available to the containers or use --env-file to pass variables
Additional notes
Notes and tips:
- The environment file (.env) should contain your Apollo credentials (APOLLO_KEY and APOLLO_GRAPH_REF) as described in the README.
- If you encounter port conflicts, adjust the -p mappings in the docker run commands to free ports on your host.
- Ensure your Apollo key has the necessary permissions for MCP server operations in GraphOS.
- If you modify mcp.Dockerfile or the startup commands, rebuild the images to apply changes.
- You can switch to local development by using BUILD_ENV=local in the docker build, which may adjust defaults for development behavior.
- For troubleshooting, inspect container logs with docker logs <container_id>.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.