osiris-mcp

# OSIRIS MCP OSIRIS MCP is a read-only Model Context Protocol server for controlled access to research information stored in OSIRIS. The project is intentionally split into two layers: 1. OSIRIS remains responsible for data access and authorization. 2. This MCP server exposes a small allowlist of typed, auditable tools. The current implementation is an initial development scaffold. Before exposing it publicly, review the deployment end to end, including TLS, network access, logging, rate limits, and the scopes granted to its dedicated API client. ## Installation Python 3.12 is required. Run the published package without installing it globally: ```bash uvx --from osiris-mcp osiris-mcp ``` Alternatively, install the command into an isolated environment: ```bash pipx install osiris-mcp osiris-mcp ``` The server uses the stdio transport by default and reads its configuration from environment variables or a `.env` file in the current directory. At minimum, set `OSIRIS_BASE_URL` and `OSIRIS_API_KEY`; dedicated OSIRIS API clients should also set `OSIRIS_CLIENT_ID`. See [Configuration](#configuration) for the full setup and the distinction between downstream OSIRIS credentials and inbound MCP authentication. ## Development setup ```bash uv sync uv run pytest ``` Start the local stdio server: ```bash uv run osiris-mcp ``` ## Local Docker container The included Compose configuration runs OSIRIS MCP as a persistent local Streamable HTTP service. It requires Docker but no local Python installation. ```bash cp .env.example .env # Configure the OSIRIS URL, client ID, API key, and source URL in .env. docker compose up --build -d ``` The MCP endpoint is then available at `http://127.0.0.1:8765/mcp` and the minimal process health check at `http://127.0.0.1:8765/health`. Stop it with: ```bash docker compose down ``` The published port is deliberately bound to `127.0.0.1`. The default `OSIRIS_MCP_AUTH_MODE=none` is suitable only for this loopback setup and must ne…