About openrelik-mcp-server
openrelik-mcp-server connects MCP clients to OpenRelik, exposing content from folders that an OpenRelik user is permitted to access. Setup uses an API key for a dedicated user and Docker Compose configuration.
Key features
- 01Expose permitted OpenRelik folders
- 02Authenticate with an API key
- 03Configure deployment through Docker Compose
Use cases
- 01Give an agent access to selected OpenRelik folders
- 02Deploy an OpenRelik MCP server alongside its services
MCP support
It connects MCP clients to OpenRelik. The content available is limited by the folders granted to the configured user.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP server for OpenRelik
- Create a new user, e.g.
agent-smith(using admin.py) - Create an API key for
agent-smith(via logging in as the user and create one in the UI) - Make sure to give
agent-smithaccess to folders you want to expose - Update docker-compose.yml
openrelik-mcp-server:
container_name: openrelik-mcp-server
image: ghcr.io/openrelik/openrelik-mcp-server:latest
restart: always
ports:
- 7070:7070
environment:
- OPENRELIK_API_URL=http://openrelik-server:8710
- OPENRELIK_API_KEY=<OPENRELIK API KEY>
- MCP_TRANSPORT=[http, sse, stdio]
- MCP_HTTP_HOST=127.0.0.1
- MCP_HTTP_PORT=7070
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.