MCP OCI Registry Server
A Model Context Protocol (MCP) server for querying OCI container registries. Provides tools and prompts for interacting with registries like Docker Hub, GHCR, and other OCI-compatible registries.
README
MCP OCI Registry Server
A Model Context Protocol (MCP) server for querying OCI container registries. Built with the fastmcp framework, this server provides tools and prompts for interacting with container registries like Docker Hub, GHCR, and other OCI-compatible registries.
Features
Tools:
ping- Health check toollist_oci_tags- List all tags for an OCI repositoryget_oci_details- Fetch manifest details including architectures, digest, and annotations
Prompts:
list_tags_prompt- Instructions for listing repository tagslist_architectures_prompt- Instructions for listing supported architectureslist_digests_prompt- Instructions for retrieving image digestslist_annotations_prompt- Instructions for listing OCI annotations
Additional Features:
- Custom
NonValidatingRegistryclass that bypasses jsonschema validation for manifest lists/indexes - Support for multi-architecture images
- Optional authentication (username/password)
- HTTP health check endpoint (
/healthz) - Docker support with docker-compose for development
Requirements
- Python 3.11+
- Docker (optional, for containerized deployment)
Installation
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
pip install -r requirements.txt
Usage
Run in stdio mode (default)
By default, the server runs over stdio which is what most MCP clients expect:
python server.py
The process will wait for JSON-RPC requests over stdin/stdout. Typically you do not run it manually; it is launched by an MCP-compatible client.
Run with uvicorn (HTTP)
For HTTP access, use the Makefile:
make run
Or manually:
uvicorn server:asgi_app --host 127.0.0.1 --port 8888
Run with Docker Compose
For development with hot reload:
make compose-up
Or manually:
docker compose up --build
Example Tool Usage
List tags:
# Using FastMCP Client
from fastmcp import Client, FastMCP
import server
client = Client(server.mcp)
async with client:
tags = await client.call_tool("list_oci_tags", {
"registry": "registry-1.docker.io",
"repository": "library/alpine"
})
print(tags.data) # ['latest', '3.22.2', 'edge', ...]
Get OCI details:
details = await client.call_tool("get_oci_details", {
"registry": "registry-1.docker.io",
"repository": "library/alpine",
"reference": "3.22.2"
})
print(details.data)
# {
# "digest": "sha256:...",
# "architectures": ["amd64", "arm64", ...],
# "annotations": {...}
# }
MCP Client Configuration (Claude Desktop)
Add an entry in your Claude Desktop MCP config (~/.cursor/mcp.json or similar):
{
"mcpServers": {
"mcp-oci-registry": {
"command": "/path/to/.venv/bin/python",
"args": [
"/path/to/mcp-oci-registry/server.py"
],
"env": {}
}
}
}
Adjust paths as needed for your environment.
Project Layout
mcp-oci-registry/
├── server.py # MCP server entrypoint
├── tools.py # Tool functions (ping, list_oci_tags, get_oci_details)
├── prompts.py # Prompt templates
├── registry.py # NonValidatingRegistry class
├── __init__.py # Package initialization
├── requirements.txt # Python dependencies
├── Dockerfile # Container image definition
├── docker-compose.yml # Development environment
├── Makefile # Common operations
└── tests/ # Test suite
├── test_tools.py
└── test_integration_http.py
Development
Run tests:
make test
Available Make targets:
make install- Install dependenciesmake run- Run server with uvicornmake test- Run test suitemake docker-build- Build Docker imagemake docker-run- Run Docker containermake compose-up- Start with docker-composemake compose-down- Stop docker-composemake compose-logs- View docker-compose logs
Testing
The project includes both unit tests and integration tests:
- Unit tests (
tests/test_tools.py) - Test individual tool functions with mocked dependencies - Integration tests (
tests/test_integration_http.py) - Test full MCP protocol flow using FastMCP Client
Run all tests:
pytest -v
Extending
Add new tools:
- Add the function to
tools.py - Register it in
server.py:mcp.tool(your_function)
Add new prompts:
- Add the prompt function to
prompts.py - Register it in
server.py:mcp.prompt(your_prompt)
License
Apache
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.