search_kibela_noteLABSCO SUMMARY
The team wiki, inside the editor.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — docker run -i -e KIBELA_ORIGIN -e KIBELA_ACCESS_TOKEN ghcr.io/kibela/kibela-mcp-server
USE CASES
01
Answering from the team's own documentation
Search the wiki, then open the note that matched, instead of guessing from memory.
02
Turning a working session into a note
The note gets written while the context is still there rather than afterwards.
03
Keeping a note current
Open it from the URL you were sent and update its body in place.
04
Finding where something should live
Folder search resolves the structure before you create a note in the wrong place.
05
Narrowing a search that returns the whole wiki
Filters on group, folder, update date and resource type cut a broad keyword down to the notes that matter.
17 tools
Listed in project docs. Your client may show a different list.
get_kibela_note_by_relay_idget_kibela_note_from_path_or_urlget_kibela_notescreate_kibela_noteupdate_kibela_note_contentsearch_kibela_folderget_kibela_folder_by_relay_idget_kibela_folder_from_path_or_urlget_kibela_folderscreate_kibela_foldermove_kibela_note_to_another_folderattach_kibela_note_to_foldercreate_kibela_commentcreate_kibela_comment_replyget_kibela_groupsget_kibela_feed_sectionsBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- docker on PATH
- KIBELA_ACCESS_TOKEN in your environment
- KIBELA_ORIGIN in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
docker run -i -e KIBELA_ORIGIN -e KIBELA_ACCESS_TOKEN ghcr.io/kibela/kibela-mcp-serverMCP Clients
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"kibela": {
"command": "docker",
"args": [
"run",
"-i",
"-e",
"KIBELA_ORIGIN",
"-e",
"KIBELA_ACCESS_TOKEN",
"ghcr.io/kibela/kibela-mcp-server"
],
"env": {
"KIBELA_ORIGIN": "https://<YOUR_SUBDOMAIN>.kibe.la",
"KIBELA_ACCESS_TOKEN": "<YOUR_KIBELA_ACCESS_TOKEN>"
}
}
}
}
