Pasting a Kibela URL and getting the note back — then writing the follow-up note without switching tabs — is what makes an internal wiki usable while you are actually working.
Kibela's own MCP server, run locally over stdio from a Docker image or the bundled script. It exposes the parts of Kibela's GraphQL API that suit an assistant: searching notes and folders, resolving one from a path or URL, and creating or updating note content.
- search_kibela_note searches by keyword with filters on resource type, co-editing, update date range, group, folder and who liked it
- get_kibela_notes lists notes in the order you ask for
- get_kibela_note_from_path_or_url turns a Kibela link someone pasted into the note itself; get_kibela_note_by_relay_id does the same from an API ID
- create_kibela_note writes a new note and update_kibela_note_content changes an existing one's body
- Folders too: search_kibela_folder, get_kibela_folder_from_path_or_url and get_kibela_folder_by_relay_id, for organising rather than only reading
Docker installed and running, or the bundled CLI script referenced by absolute path if you would rather not use Docker. Plus a Kibela access token issued in your account settings: the server reads KIBELA_ORIGIN and KIBELA_ACCESS_TOKEN. Local stdio only — there is no hosted endpoint.
One command plus a key — docker run -i -e KIBELA_ORIGIN -e KIBELA_ACCESS_TOKEN ghcr.io/kibela/kibela-mcp-server, then supply credentials