MCP Kibela Server

What kiwamizamurai/mcp-kibela-server MCP server does

The kiwamizamurai/mcp-kibela-server MCP server exposes Kibela content and selected note actions through the Model Context Protocol. It is designed for MCP clients that need to search an organization's notes, inspect note details, browse group and folder structures, and retrieve information about users.

The available operations include advanced note search with optional archive, co-editing, sorting, user, and folder filters. An agent can also fetch the current user's latest notes, recently viewed notes, notes within a group, notes directly inside a folder, or notes that can be identified by a Kibela path or URL. Note retrieval includes content and comments, with an option to include image data URLs.

In addition to read operations, the server provides like and unlike actions for notes. Group and folder queries return organizational metadata, while user queries return user identifiers, accounts, and real names as described by the project documentation.

How it works

The server communicates with Kibela using the team-specific API configuration supplied through environment variables. MCP clients invoke named tools such as kibela_search_notes, kibela_get_note_content, kibela_get_group_folders, and kibela_get_note_from_path; each tool accepts the identifiers or filters needed for its operation.

The project README states that the implementation performs GraphQL schema introspection with functions from the graphql package, including schema construction, introspection-query generation, and schema printing. This is used to reverse engineer Kibela's API. The material does not describe a separate local database or caching layer.

Setup and configuration

Set these required environment variables before starting the server:

• KIBELA_TEAM: the Kibela team name.
• KIBELA_TOKEN: the Kibela API token.

The documented Cursor configuration runs the published package with npx -y @kiwamizamurai/mcp-kibela-server. Docker users can run the image ghcr.io/kiwamizamurai/mcp-kibela-server:latest and pass both variables into the container. For development, clone the repository, run npm install, and start the built entry point with Node. The README also describes building a local Docker image and gives http://localhost:3000/sse as the SSE server URL.

The kiwamizamurai/mcp-kibela-server MCP server requires valid Kibela credentials; the supplied examples use placeholder values that must be replaced with the user's team name and token.

Tools and capabilities

• Search notes by query, archive status, co-editing status, sort order, users, or folders.
• Retrieve the latest notes associated with the authenticated user.
• Read note HTML, comments, attachments, groups, and folders.
• Include image data URLs when requested for note content.
• List accessible groups and users.
• Browse group folders, group notes, and folder notes.
• Like or unlike a note.
• Retrieve recently viewed notes.
• Resolve note content from a path or full Kibela URL.

Limitations and notes

The documentation explicitly provides a Cursor integration, but does not confirm compatibility with every MCP client. Search and listing limits apply to some tools: latest notes default to 15, folder notes default to 100, and recently viewed notes have a maximum of 15. The available material documents note likes and unlikes, but does not describe broader note editing or deletion operations.