MCP server that exposes the Knora institutional-memory platform to AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"knora-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Knora MCP Server An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that exposes the full Knora institutional-memory platform to AI agents. Once connected, Claude (or any MCP-compatible agent) can search, query, create, and manage your organisation's knowledge base directly from a conversation. --- ## What the server does The Knora MCP server wraps the Knora REST API and exposes it as **~80 MCP tools** organised into these categories: | Category | What agents can do | |---|---| | **Query & Search** | Ask natural-language questions (RAG), semantic search, view query history, find documentation gaps | | **Knowledge Management** | Create/read/update/delete entries, verify, flag, relate, bulk import/export, manage tags and departments | | **Capture** | Quick notes, voice upload (Whisper), document upload (PDF/Word/Excel/image), interviews, shift logs | | **Admin** | Invite/manage members, update roles, org settings, API keys, webhooks, integrations | | **Analytics** | Dashboard overview, bus factor risk, knowledge health score, staleness report, query analytics | --- ## Security boundaries This MCP server is designed for **per-org customer access**, not platform administration. The following invariants are enforced: 1. **Org-isolated** — all operations are scoped to the authenticated user's organisation. Agents cannot see or modify data belonging to another org. 2. **No superadmin tools** — the admin endpoints (`/api/v1/admin/…`) are not exposed here and must not be added. 3. **No plan/billing changes through MCP** — subscription upgrades and cancellations must go through the Stripe checkout flow, which requires human-initiated payment. --- ## Installation ```bash # From the repo root pip install -e ./mcp # Or install directly from the mcp/ directory cd mcp pip install -e . ``` Requirements: Python 3.11+, a running Knora backend. --- ## Configuration All configuration is via environment variables. No config file is required. #…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.