registry

The BioContextAI Registry MCP server is a centralized catalog that lists MCP servers used for biomedical research under the BioContextAI project. It provides a UI at biocontext.ai/registry and a machine-readable Registry JSON at biocontext.ai/registry.json, allowing users to discover, compare, and access tools built by the community. As a consumer, you can browse the registry to find MCP servers that fit your biomedical use case, review descriptions, and follow links to the respective server repositories. If you are a server author, you can submit your MCP server to the Registry by creating a meta.yaml file in the servers directory and opening a pull request; the registry enforces schema validation and documentation requirements to ensure consistency and discoverability. The registry also integrates with automation (e.g., Bluesky posting) and provides an editor to help you generate the required meta.yaml configuration for your MCP server.

Prerequisites:

• Git
• Python 3.9+ (for local development and repository tooling)
• Virtual environment support (optional but recommended)

Step-by-step:

1. Clone the registry repository git clone https://github.com/biocontext-ai/registry.git cd registry

2. Set up a Python virtual environment and install tooling used for development and validation python -m venv .venv source .venv/bin/activate # on macOS/Linux .venv\Scripts\activate # on Windows pip install -r requirements-dev.txt

3. Run local validation and developer hooks (pre-commit) as described by the repository instructions uv venv source .venv/bin/activate uv sync pre-commit install

4. If you are adding a new MCP server, create a meta.yaml under the servers/ directory following the schema described in schema.json, then run the repository's validation steps to ensure compliance before opening a PR. You can use the provided editor at https://biocontext.ai/registry/editor to help generate the meta.yaml file.

5. After submitting a PR, ensure the repository CI passes (schema validation, tests, and deployment workflow) so that your MCP server is added to the Registry UI and Registry JSON.

Tips and considerations:

• The Registry focuses on biomedical applicability, open licensing, and MCP compliance. When adding a server, make sure your meta.yaml includes a clear description, unique identifier, and publicly accessible repository/documentation URLs.
• Regularly maintain your entry to reflect updates in capabilities or licensing.
• If you rely on automated notifications, you can enable GitHub watch to receive alerts about new registry entries.
• The provided MVP CI pipelines include schema validation and a deployment workflow to publish registry.json and UI assets when changes are merged.
• If you encounter environment-related issues while developing locally, ensure your Python virtual environment is activated and that dependencies listed in requirements-dev.txt are installed.