Kibela MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIBELA_TEAM | Yes | Your Kibela team name | |
| KIBELA_TOKEN | Yes | Your Kibela API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kibela_search_notesB | Search Kibela notes with given query |
| kibela_get_my_notesA | Get your latest notes from Kibela |
| kibela_get_note_contentC | Get content and comments of a specific note |
| kibela_get_groupsB | Get list of accessible groups |
| kibela_get_group_foldersC | Get folders in a group |
| kibela_get_group_notesB | Get notes in a group that are not attached to any folder |
| kibela_get_folder_notesC | Get notes in a folder |
| kibela_get_usersC | Get list of users |
| kibela_like_noteC | Like a note |
| kibela_unlike_noteC | Unlike a note |
| kibela_get_recently_viewed_notesB | Get your recently viewed notes |
| kibela_get_note_from_pathC | Get note content by its URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but some overlap exists between tools that retrieve notes in different contexts (e.g., get_note_content vs get_note_from_path) and between personal note lists (get_my_notes vs get_recently_viewed_notes). Descriptions help disambiguate, so the set is mostly clear.
All tools follow a consistent pattern: 'kibela_verb_noun' with present tense verbs. The naming is uniform and predictable, with no mixing of conventions.
With 12 tools, the count is well-suited for a knowledge management server. It provides a balanced set of read operations, search, and simple interactions without being overwhelming or too sparse.
The tool set is heavily read-only, covering notes, folders, groups, and users, plus like/unlike. However, it lacks essential write operations such as creating, updating, or deleting notes or groups, which limits its completeness for typical workflows.