Ocireg MCP Server

Ocireg mcp server lets Claude, Cursor and other MCP clients work with Ocireg directly. An SSE-based MCP server that allows LLM-powered applications to interact with OCI registries. It provides tools for retrieving information about container images, listing tags, and more.

What Ocireg does

An MCP (Model Context Protocol) server that provides tools for querying OCI registries and image references.

This project implements an SSE-based MCP server that allows LLM-powered applications to interact with OCI registries. It provides tools for retrieving information about container images, listing tags, and more.

Key capabilities

• Get information about OCI images
• List tags for repositories
• Get image manifests
• Get image configs

Tools it exposes

Once connected, the assistant can call these 8 tools directly:

• get_image_info — The get_image_info tool exposed by this server
• list_tags — The list_tags tool exposed by this server
• get_image_manifest — The get_image_manifest tool exposed by this server
• get_image_config — The get_image_config tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Authentication — The server supports the following authentication methods for accessing private OCI registries (in order of priority):
• Testing — The Testing tool exposed by this server
• Linting — The Linting tool exposed by this server

Installing the ocireg mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 3 environment variables: OCI_TOKEN, OCI_USERNAME, OCI_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Go 1.21 or later - Access to OCI registries

Where it fits

AI-service servers chain other models into your assistant, turning a single chat into a small production pipeline. Ocireg sits in that group, and the shape of its toolset — get_image_info, list_tags, get_image_manifest among others — tells you what it is really for. Worth comparing against the other ai services servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 8 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Ocireg.
• Written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the ocireg mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.