mcp-discovery

mcp-discovery is a production-grade MCP server designed to provide discovery services within the MCP ecosystem. It emphasizes reliability, maintainability, and fast onboarding, making it suitable for teams building or integrating with MCP clients and other servers. Once running, the server exposes the MCP-compatible endpoints and runtime behavior necessary for service discovery, status checks, and coordination with other MCP components. You can interact with the server using its CLI or API routes (as documented in the project’s docs) to publish or query MCP endpoints, monitor health, and integrate with your CI/CD pipelines.

Key capabilities typically available with this type of server include starting and stopping the MCP service, performing health checks, inspecting current discovery mappings, and observing runtime logs. The project is structured to encourage reproducible local development and straightforward deployment to staging or production environments. Refer to the repository’s docs for specifics on available API routes, CLI commands, and any environment variables that influence discovery behavior.

Prerequisites

• Git
• Node.js (LTS version) and npm installed on your system
• A compatible runtime environment for the project (as specified by the repository)

Installation steps

1. Clone the repository git clone https://github.com/yksanjo/mcp-discovery.git cd mcp-discovery

2. Install dependencies npm ci

3. (Optional) Run lint and tests during development npm run lint npm test

4. Build the project (if a build step is defined in package.json) npm run build

5. Start the MCP Discovery server node src/server.js

Prerequisites recap

• Ensure you have network access to any services the discovery server communicates with
• Review SECURITY.md and CONtributing.md for any project-specific policies before deploying to production

Notes and tips:

• This MCP server follows the repository’s production-grade standards, so expect CI gates and tests to validate changes.
• If environment-specific configuration is required, look for an .env file or environment variables documented in the project docs.
• Common issues may include missing dependencies, port conflicts, or misconfigured endpoints. Check logs for stack traces and verify that npm install completed successfully.
• When deploying to environments with custom DNS or service meshes, ensure that discovery endpoints are reachable and that firewall rules allow necessary traffic.
• If you upgrade Node.js versions, re-run npm ci to refresh dependencies with compatible lockfiles.