Kibela

What is mcp-kibela-server?

mcp-kibela-server is a Model Context Protocol (MCP) server that facilitates the integration of Large Language Models (LLMs) with Kibela, a collaborative note-taking and knowledge-sharing platform. It acts as a bridge, allowing LLMs to access and interact with content stored in Kibela.

How to use mcp-kibela-server?

To use mcp-kibela-server, you need to configure it with your Kibela team name and API token. This can be done via environment variables (KIBELA_TEAM and KIBELA_TOKEN). The server can be run directly from the source using npx or as a Docker container. For integration with tools like Cursor, you can add a configuration to your ~/.cursor/mcp.json file, specifying the command to run the server (e.g., npx @kiwamizamurai/mcp-kibela-server or a Docker command).

Key Features of mcp-kibela-server

• Search Notes: Advanced search capabilities with filters for co-editing status, archive status, sort order, user IDs, and folder IDs.
• Get Latest Notes: Retrieve a specified number of your most recent notes.
• Note Content and Comments: Access full note content, including HTML, comments, attachments, groups, and folders.
• Group and Folder Management: List accessible groups and folders within groups, including nested folders.
• Note Management: Like/unlike notes, get notes within a group (not attached to a folder), and get notes within a specific folder.
• User Listing: Retrieve a list of users with their IDs, account names, and real names.
• Recently Viewed Notes: Get a list of your recently viewed notes.
• Note by Path/URL: Retrieve note content using its path or full Kibela URL.

Use Cases of mcp-kibela-server

• LLM Integration: Enable LLMs to search, retrieve, and interact with Kibela content for tasks like summarization, question answering, and content generation.
• Automated Knowledge Retrieval: Build automated systems that can pull specific information from Kibela based on queries.
• Enhanced Productivity Tools: Integrate Kibela with other productivity tools that leverage LLMs for a more seamless workflow.
• Custom Kibela Clients: Develop custom applications that can programmatically access and manipulate Kibela data.

FAQ from mcp-kibela-server

Q: What environment variables are required to run mcp-kibela-server? A: You need to set KIBELA_TEAM (your Kibela team name) and KIBELA_TOKEN (your Kibela API token).

Q: Can I run mcp-kibela-server using Docker? A: Yes, you can build and run the server as a Docker container. Example Docker commands and mcp.json configurations are provided in the README.

Q: How do I integrate mcp-kibela-server with Cursor? A: You can add a configuration to your ~/.cursor/mcp.json file, specifying the command to run the server, either via npx or Docker.

Q: What kind of information can I retrieve about notes? A: You can get note ID, title, URL, author, groups, full HTML content, comments, attachments, and more, depending on the specific tool used.

Q: Can I manage likes on notes using this server? A: Yes, there are tools available to like and unlike notes, which will update the likers list.

Kibela MCP Server

MCP server implementation for Kibela API integration, enabling LLMs to interact with Kibela content.

Features

• Search notes with advanced filters
• Get your latest notes
• Get note content and comments
• Manage groups and folders
• Like/unlike notes
• List users
• View note attachments
• View recently viewed notes
• Get notes by path

Configuration

Environment Variables

• KIBELA_TEAM: Your Kibela team name (required)
• KIBELA_TOKEN: Your Kibela API token (required)

Cursor Integration

Add to your ~/.cursor/mcp.json:

{
    "mcpServers": {
        "kibela": {
            "command": "npx",
            "args": ["-y", "@kiwamizamurai/mcp-kibela-server"],
            "env": {
                "KIBELA_TEAM": "YOUR_TEAM_NAME",
                "KIBELA_TOKEN": "YOUR_TOKEN"
            }
        }
    }
}

If you want to use docker instead

{
    "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_TEAM_NAME",
                "KIBELA_TOKEN": "YOUR_TOKEN"
            }
        }
    }
}

Tools

kibela_search_notes

Search Kibela notes with given query

• Input:
  • query (string): Search query
  • coediting (boolean, optional): Filter by co-editing status
  • isArchived (boolean, optional): Filter by archive status
  • sortBy (string, optional): Sort by (RELEVANT, CONTENT_UPDATED_AT)
  • userIds (string[], optional): Filter by user IDs
  • folderIds (string[], optional): Filter by folder IDs
• Returns: List of matching notes with ID, title, URL, author, groups and more

kibela_get_my_notes

Get your latest notes from Kibela

• Input:
  • limit (number, optional): Number of notes to fetch (default: 15)
• Returns: List of your latest notes with author information

kibela_get_note_content

Get content and comments of a specific note

• Input:
  • id (string): Note ID
  • include_image_data (boolean, optional): Whether to include image data URLs in the response (default: false)
• Returns: Full note content including HTML, comments, attachments, groups, folders and more

kibela_get_groups

Get list of accessible groups

• Input: None
• Returns: List of groups with details like privacy settings and permissions

kibela_get_group_folders

Get folders in a group

• Input:
  • groupId (string): Group ID
  • parentFolderId (string, optional): Parent folder ID for nested folders
• Returns: List of folders with their notes and metadata

kibela_get_group_notes

Get notes in a group that are not attached to any folder

• Input:
  • groupId (string): Group ID
• Returns: List of notes with author information, sorted by last update time

kibela_get_folder_notes

Get notes in a folder

• Input:
  • folderId (string): Folder ID
  • limit (number, optional): Number of notes to fetch (default: 100)
• Returns: List of notes with author information, sorted by last update time

kibela_get_users

Get list of users

• Input: None
• Returns: List of users with ID, account and real name

kibela_like_note

Like a note

• Input:
  • noteId (string): Note ID
• Returns: Updated likers list

kibela_unlike_note

Unlike a note

• Input:
  • noteId (string): Note ID
• Returns: Updated likers list

kibela_get_recently_viewed_notes

Get your recently viewed notes

• Input:
  • limit (number, optional): Number of notes to fetch (max 15)
• Returns: List of recently viewed notes with author information

kibela_get_note_from_path

Get note content by its path or URL

• Input:
  • path (string): Note path (e.g. '/group/folder/note') or full Kibela URL (e.g. 'https://team.kibe.la/notes/123')
  • include_image_data (boolean, optional): Whether to include image data URLs in the response (default: false)
• Returns: Full note content including HTML, comments, attachments, groups, folders and more

Local Development

Running from Source

1. Clone the repository
2. Install dependencies: npm install

Environment Setup

For local development, update your ~/.cursor/mcp.json:

{
    "mcpServers": {
        "kibela": {
            "command": "node",
            "args": ["path/to/mcp-kibela-server/dist/src/index.js"],
            "env": {
                "KIBELA_TEAM": "YOUR_TEAM_NAME",
                "KIBELA_TOKEN": "YOUR_TOKEN"
            }
        }
    }
}

MCP inspector

npx @modelcontextprotocol/inspector node ./dist/src/index.js

and set environemtns

Docker

Build and run locally:

docker build -t mcp-kibela-server .

Then use this configuration:

{
    "mcpServers": {
        "kibela": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "-e",
                "KIBELA_TEAM",
                "-e",
                "KIBELA_TOKEN",
                "mcp-kibela-server"
            ],
            "env": {
                "KIBELA_TEAM": "YOUR_TEAM_NAME",
                "KIBELA_TOKEN": "YOUR_TOKEN"
            }
        }
    }
}

For SSE transport, ensure the server URL is set to: http://localhost:3000/sse

Other products

• vscode extension for kibela