Releases: OSIRIS-Solutions/osiris-mcp
Release list
OSIRIS MCP v0.1.0
This is the first public alpha release of OSIRIS MCP, a secure, read-only Model Context Protocol connector for the OSIRIS research information system.
OSIRIS MCP enables compatible language-model clients to answer reporting, research-management, and communication questions using deliberately restricted and structured institutional data access.
Highlights
- Twelve typed, read-only MCP tools for:
- activities and publications
- projects
- people
- expertise discovery
- organisational units
- research topics
- activity types and instance metadata
- Compact, evidence-centred responses instead of complete database records
- Explicit activity date semantics for:
- activities starting within a period
- activities ending within a period
- activities active during or overlapping a period
- Paginated searches for complete result retrieval
- Instance-specific discovery of units, topics, and activity types
- Dedicated OSIRIS API-client identities with independently revocable credentials and fine-grained permissions
- Safe error responses with traceable request IDs
- OAuth/OIDC resource-server support
- Static API-key authentication for simpler controlled deployments
- Local stdio and persistent Streamable HTTP transports
- Hardened Docker deployment running as an unprivileged user
- Python package published as
osiris-mcp - Licensed under AGPL-3.0-or-later
Installation
Run the package directly with uvx:
uvx --from osiris-mcp osiris-mcpAlternatively, install it into an isolated environment:
pipx install osiris-mcp
osiris-mcpThe connector requires access to an OSIRIS installation providing the corresponding MCP API routes and an appropriately permissioned OSIRIS API client.
For persistent HTTP deployments, see the included Docker Compose configuration and authentication documentation.
Security model
This release deliberately provides read-only access. Language-model clients cannot create, update, or delete OSIRIS records.
OSIRIS remains responsible for query construction, field allowlists, permissions, and access to the authoritative database. The connector never exposes a generic database query or unrestricted proxy tool.
OAuth access tokens received from MCP clients are not forwarded to OSIRIS. The connector uses a separate, restricted OSIRIS API identity for downstream requests.
Status
This is an initial alpha release developed and evaluated during the DBCLS BioHackathon 2026. It has been tested against a local OSIRIS installation containing synthetic data.
Before production deployment, institutions should perform their own security and privacy review and configure TLS, identity-provider integration, network restrictions, rate limits, audit retention, and secret rotation according to their local requirements.