Almost everything here reads: kibela_like_note and kibela_unlike_note are the only tools that change anything on the team, so attaching this to an agent does not put the wiki's content at risk. That read surface is arranged around how people look for wiki pages — by phrase, by folder, by author, by what they viewed yesterday, or by the URL a colleague sent. Images are opt-in through include_image_data, which keeps an ordinary note lookup from dragging binary data into the context.
A read-oriented front end to one Kibela team, exposing notes, groups, folders and users through 12 tools.
- Search with the filters that actually narrow a wiki: kibela_search_notes takes a query plus folderIds, userIds, coediting and isArchived, and sorts by a chosen field.
- Two ways into a note's full text: kibela_get_note_content returns content and comments for an id, kibela_get_note_from_path resolves a note by its URL, and both take include_image_data when the images matter.
- The team's structure walked in order: kibela_get_groups lists accessible groups, kibela_get_group_folders their folders, kibela_get_folder_notes the notes inside one, and kibela_get_group_notes the notes in a group that sit in no folder.
- Your own recent context: kibela_get_my_notes returns your latest notes and kibela_get_recently_viewed_notes what you last opened, both capped by limit.
- People and reactions: kibela_get_users lists the team's users, and kibela_like_note and kibela_unlike_note set or clear a like.
A Kibela team and a token for it, supplied as KIBELA_TEAM and KIBELA_TOKEN.
One command plus a key — npx -y @kiwamizamurai/mcp-kibela-server, then supply credentials