Connections & Capabilities
Connects To
Capabilities
Quickstart
Install
npx -y @smithery/cli install @kj455/mcp-kibela --client claudeConfig
{
"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"
}
}
}Exposed MCP Tools (6)
Note SearchSearches Kibela notes based on keywords.
Read-only operation; no data modification.
My NotesFetches the user's latest Kibela notes.
Read-only operation; no data modification.
Note ContentRetrieves the content and comments of a Kibela note by its ID.
Read-only operation; no data modification.
Note by PathRetrieves the content of a Kibela note by its path.
Read-only operation; no data modification.
Create NoteCreates a new note in Kibela.
Creates new content; potential for spam or misuse.
Update Note ContentUpdates the content of an existing Kibela note by its ID.
Modifies existing content; potential for data corruption or vandalism.
Safety Assessment
This MCP server provides a moderate level of safety. The use of Docker enhances isolation, but the reliance on API tokens and write operations introduces risk. Secure handling of the Kibela API token is crucial. It is safe to use in environments where Kibela access is appropriately controlled and the token is securely managed. Risky scenarios include exposing the API token or granting access to untrusted users.
- Uses Docker for sandboxing and isolation.
- Relies on API token for authentication.
- No direct internet access from the host (containerized).
- Supports read and write operations, enabling a range of use cases.
- Requires Kibela API token, which if compromised, grants access to Kibela data.
- Write operations (create, update) can modify Kibela content.
- Environment variables are used to store sensitive information (API token).
- No explicit RBAC or fine-grained permission controls within the MCP server itself.
