kibela_get_folder_notes
Get notes in a folder
LABSCO SUMMARY
A wiki link pasted into a thread turns into the note's actual content and comments, without a search step.
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.
What it is
A read-oriented front end to one Kibela team, exposing notes, groups, folders and users through 12 tools.
What you get
- 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.
Requirements
A Kibela team and a token for it, supplied as KIBELA_TEAM and KIBELA_TOKEN.
Setup effort
One command plus a key — npx -y @kiwamizamurai/mcp-kibela-server, then supply credentials
USE CASES
01
Answering a team question from the wiki rather than from memory
Search the notes with the phrase and any author or folder filter that narrows it, then read the winning note's content and its comments.
02
Following a Kibela link somebody pasted into the thread
Resolve the URL straight to the note's content instead of searching for its title.
03
Finding out what a group has actually documented
Walk from the accessible groups into their folders, then read both the notes filed in folders and the ones that never were.
04
Picking your own half-finished writing back up
Pull your latest notes and the ones you were reading recently, then open whichever one you meant.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
kibela_get_group_folders
Get folders in a group
kibela_get_group_notes
Get notes in a group that are not attached to any folder
kibela_get_groups
Get list of accessible groups
kibela_get_my_notes
Get your latest notes from Kibela
kibela_get_note_content
Get content and comments of a specific note
kibela_get_note_from_path
Get note content by its URL
kibela_get_recently_viewed_notes
Get your recently viewed notes
kibela_get_users
Get list of users
kibela_like_note
Like a note
kibela_search_notes
Search Kibela notes with given query
kibela_unlike_note
Unlike a note
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. Ten of the twelve read; the only writes are kibela_like_note and kibela_unlike_note. Notes cannot be created, edited, commented on or deleted.
Requires
- npx on PATH
- KIBELA_TEAM in your environment
- KIBELA_TOKEN in your environment
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @kiwamizamurai/mcp-kibela-serverMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"kibela": {
"command": "npx",
"args": [
"-y",
"@kiwamizamurai/mcp-kibela-server"
],
"env": {
"KIBELA_TEAM": "<YOUR_KIBELA_TEAM>",
"KIBELA_TOKEN": "<YOUR_KIBELA_TOKEN>"
}
}
}
}Cursor — Docker
CURSOR — DOCKER · JSON
{
"mcpServers": {
"kibela": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KIBELA_TEAM",
"-e",
"KIBELA_TOKEN",
"ghcr.io/kiwamizamurai/mcp-kibela-server:latest"
],
"env": {
"KIBELA_TEAM": "<YOUR_KIBELA_TEAM>",
"KIBELA_TOKEN": "<YOUR_KIBELA_TOKEN>"
}
}
}
}
