MCP Kibela MCP Server

MCP server implementation that integrates with Kibela API

Local serverstdio

What is the MCP Kibela MCP server?

If you already use MCP Kibela, the mcp kibela mcp server is the piece that lets your assistant work with it directly. MCP server implementation that integrates with Kibela API.

What the server does

A Model Context Protocol (MCP) server implementation that enables AI assistants to search and reference Kibela content. This setup allows AI models like Claude to securely access information stored in Kibela.

  • Note Search — Search Kibela notes by keywords
  • My Notes — Fetch your latest notes
  • Note Content — Get note content and comments by ID
  • Note by Path — Get note content by path
  • Create Note — Create a new note
  • Update Note Content — Update note content by note id

Installation

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: KIBELA_TEAM, KIBELA_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Before you begin, ensure you have: - Node.js (v18 or higher) - MCP Client (Claude Desktop, Cursor, etc.) - Kibela Access Token (How to get a token) -

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by kj455; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

How to install the MCP Kibela MCP server

{
  "mcpServers": {
    "mcp-kibela": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "KIBELA_TEAM",
        "-e",
        "KIBELA_TOKEN",
        "ghcr.io/kj455/mcp-kibela:latest"
      ],
      "env": {
        "KIBELA_TEAM": "your-team-name from https://[team-name].kibe.la",
        "KIBELA_TOKEN": "your-token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

Before you begin, ensure you have: - Node.js (v18 or higher) - MCP Client (Claude Desktop, Cursor, etc.) - Kibela Access Token (How to get a token) -

VariableDescriptionRequired
KIBELA_TEAMConfiguration value read at startup.Optional
KIBELA_TOKENCredential the server authenticates with.Yes

Frequently asked questions

It connects MCP Kibela to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with MCP Kibela directly.