System Context

The Kibela MCP Bridge operates exclusively as a local daemon, communicating via Standard I/O (STDIO). It is designed for consumption by any adhering MCP client implementation, such as the Claude Desktop application or extensions for Visual Studio Code.

Tool exposure is restricted to publicly accessible GraphQL endpoints deemed appropriate for context-aware interactions.

Primary Capabilities

• Querying and retrieving data housed within the Kibela knowledge base.
• Programmatic structuring and manipulation of Kibela's folder hierarchies and individual articles.
• Utilizing integrated artificial intelligence services to assist in drafting and refining Kibela content.

Prerequisites

1. Installation of the Docker containerization platform.
2. Active execution state for the Docker daemon.
3. A valid Kibela access token must be generated.
4. An installed application implementing the MCP client specification.

Deployment Scenarios

Configuration Example: Claude Desktop

Populate the configuration file claude_desktop_config.json with the following structure. The Kibela domain endpoint and the secret access token must be provided via environment variables.

{ "mcpServers": { "kibela": { "command": "docker", "args": [ "run", "-i", "-e", "KIBELA_ORIGIN", "-e", "KIBELA_ACCESS_TOKEN", "ghcr.io/kibela/kibela-mcp-server" ], "env": { "KIBELA_ORIGIN": "https://your-subdomain.kibe.la", "KIBELA_ACCESS_TOKEN": "***" } } } }

Native Execution (Without Docker)

Specify the absolute path to the compiled execution script as the service command. Ensure environment variables are correctly set.

{ "mcpServers": { "kibela": { "command": "/path/to/kibela-mcp-server/bin/cli.mjs", "env": { "KIBELA_ORIGIN": "https://your-subdomain.kibe.la", "KIBELA_ACCESS_TOKEN": "***" } } } }

Exposed Toolkit Functions

Article Management

• search_kibela_note - Executes a query against the note index.

• query: The essential string for information retrieval (mandatory).

• resources: Filter by resource category (optional).
• coediting: Boolean filter for co-edited status (optional).
• updated: Timeframe specifier for modification date (optional).
• groupIds: Array of group identifiers for scope limitation (optional).
• folderIds: Array of folder identifiers for scope limitation (optional).
• likerIds: Filter based on users who have liked the note (optional).
• isArchived: Boolean flag to include archived items (optional).

• sortBy: Parameter governing result ordering (optional).

• get_kibela_note_by_relay_id - Fetches a specific article using its globally unique Relay ID.

• id: The target note's Relay Identifier (mandatory).

• get_kibela_note_from_path_or_url - Retrieves an article based on its human-readable path or direct URL locator.

• path: The hierarchical location or web address of the note (mandatory).

• get_kibela_notes - Lists articles residing within a specified container folder.

• folderId: The identifier of the parent folder (mandatory).

• first: Pagination control: number of initial records to return (optional).

• last: Pagination control: number of trailing records to return (optional).

• create_kibela_note - Provision a new knowledge artifact.

• title: The designated title for the new entry (required).

• content: The initial body content (required).
• draft: Flag indicating provisional save status (optional).
• groupIds: Mandatory array specifying the access groups for the note (required).

• folders: Optional structure defining where to place the new note.

  • groupId: Group context for the folder.
  • folderName: The name of the target folder.

• update_kibela_note_content - Overwrites the existing body of a specific article.

• id: Identifier of the article to modify (required).
• newContent: The replacement document body (required).
• baseContent: The state of the content prior to this update (required for optimistic locking/diffing).

Folder Hierarchy Management

• search_kibela_folder - Queries the folder index.

• query: Search term for folder names or metadata (required).

• get_kibela_folder_by_relay_id - Retrieves folder metadata using its Relay ID.

• id: The target folder's Relay Identifier (required).

• first: Initial record count for contained items (optional).

• get_kibela_folder_from_path_or_url - Locates a folder via its structural path or URI.

• path: The folder's location string (required).

• first: Initial record count for contained items (optional).

• get_kibela_folders - Returns a list of accessible folders.

• first: Initial record count (optional).

• last: Trailing record count (optional).

• create_kibela_folder - Establishes a new organizational unit.

• groupId: The owning group ID (required).

• fullName: The complete, absolute path specification for the new folder (required).

• move_kibela_note_to_another_folder - Reassigns an article from a source location to a destination.

• id: Target note's ID (required).

• fromFolder: Metadata describing the source container.
  • groupId: Source Group ID.
  • folderName: Source Folder Name.

• toFolder: Metadata describing the target container.

  • groupId: Destination Group ID.
  • folderName: Destination Folder Name.

• attach_kibela_note_to_folder - Establishes an association between an existing note and a folder.

• id: Note identifier (required).
• folder: Folder metadata for association.
  • groupId: Group ID context.
  • folderName: Folder name.

Annotation Services

• create_kibela_comment - Inserts a new annotation onto a specified article.

• content: The text of the annotation (required).

• noteId: Identifier of the note receiving the comment (required).

• create_kibela_comment_reply - Appends a response to an existing annotation thread.

• content: The reply text payload (required).
• commentId: Identifier of the parent annotation (required).

Metadata Retrieval

• get_kibela_groups - Yields a listing of defined organizational groups.

• first: Initial record count (optional).

• last: Trailing record count (optional).

• get_kibela_feed_sections - Retrieves pre-configured feed views.

• kind: Specifies the category or type of feed data requested (required).
• groupId: Contextual group identifier for the feed scope (required).

Predefined Interaction Modes (Prompts)

Review Protocol

Processes an article referenced by its URL for comprehensive review.

Input Schema:

typescript { url: string; // Must conform to standard URL structure }

Information Sourcing Protocol

Executes a targeted search for contextually pertinent data.

Input Schema:

typescript { query: string; }

Contextual Linkage Protocol

Navigates to and explores related knowledge assets based on an initial URL reference.

Input Schema:

typescript { url: string; // Must conform to standard URL structure }

Annotation Reflection Protocol

Takes a specified URL and synthesizes its associated commentary back into the primary note content.

Input Schema:

typescript { url: string; // Must conform to standard URL structure }

Configuration Overrides

Tool definitions and prompt texts can be dynamically modified by supplying a specific JSON configuration payload. Refer to server.ts for the mapping keys for tools and prompts.

{ "tools": { "search_kibela_note": { "description": "New description" } }, "prompts": { "review": { "prompt": "New review prompt" } } }

This configuration file can be mounted into the Docker container environment as follows:

{ "mcpServers": { "kibela": { "command": "docker", "args": [ "run", "-i", "-e", "KIBELA_ORIGIN", "-e", "KIBELA_ACCESS_TOKEN", "-v", "/path/to/kibela-mcp-server-config.json:/usr/src/app/kibela-mcp-server-config.json", "ghcr.io/kibela/kibela-mcp-server" ], "env": { "KIBELA_ORIGIN": "https://your-subdomain.kibe.la", "KIBELA_ACCESS_TOKEN": "***" } } } }

Development Lifecycle

Executing dependency installation within the containerized environment:

bash docker compose run mcp pnpm install

Starting the service locally:

bash docker compose up

Validation Using MCP Inspector

Testing the gateway integration via the Inspector utility:

bash npx @modelcontextprotocol/inspector \ -e KIBELA_ORIGIN=https://your-subdomain.kibe.la \ -e KIBELA_ACCESS_TOKEN=*** \ docker compose exec mcp bin/cli.mjs

Licensing Information

This software package is distributed under the terms of the MIT agreement.

WIKIPEDIA: Business management tools encompass the spectrum of systems, operational controls, computational solutions, and strategic methodologies employed by organizations to effectively navigate evolving market dynamics, secure a competitive footing, and systematically elevate organizational performance metrics.

== Conceptual Framework == Management functions across organizational sectors can be mapped to specific tool categories, such as those dedicated to strategic foresight, operational flow management, data persistence, personnel administration, evidence-based decision support, and performance monitoring. A functional taxonomy generally addresses these core domains:

Tools supporting initial data capture and integrity verification across any functional unit. Systems focused on the governance and enhancement of business processes. Platforms for aggregating information to facilitate strategic choices. The technological landscape for management tools has undergone profound transformation in the past decade, driven by rapid technological advancement. This acceleration makes the selection of optimal business tools for specific corporate scenarios increasingly complex. This difficulty stems from constant pressures to optimize expenditures, maximize revenue generation, deeply understand client requirements, and ensure product delivery aligns precisely with those needs. In this context, organizational leadership should adopt a strategic posture toward management tool adoption and integration, rather than defaulting to the newest available solution. Often, unadapted tools are integrated directly, leading to systemic instability. Business management instrumentation must be chosen deliberately and subsequently tailored to meet unique organizational requirements, reversing the common practice.

== Prominent Tools (2013 Benchmark) == Data from a 2013 assessment by Bain & Company highlighted the global distribution and application of various business tools, reflecting regional needs shaped by market conditions and economic climates. The leading ten instruments identified included:

Strategic planning frameworks Customer Relationship Management (CRM) systems Employee sentiment surveying platforms Competitive benchmarking methodologies Balanced Scorecard implementation Core competency identification Outsourcing strategy protocols Organizational Change Management programs Supply Chain optimization systems Mission and Vision statement articulation Market segmentation analysis Total Quality Management (TQM) initiatives

== Business Software Applications == Software solutions or interconnected program suites utilized by personnel to execute diverse corporate functions are broadly termed business software (or business applications). These applications serve to augment output volumes, quantify efficiency, and execute various corporate tasks with precision. The evolution progressed from foundational Management Information Systems (MIS) to integrated Enterprise Resource Planning (ERP) suites, later incorporating Customer Relationship Management (CRM) capabilities, culminating in the current era of cloud-based business management platforms. While a measurable link exists between IT investment and corporate outcomes, two factors are paramount for value realization: the efficacy of the deployment process and the judicious selection and subsequent adaptation of the chosen tools.

== Small and Medium Enterprise Focus == The toolset tailored for SMEs is crucial as it furnishes mechanisms to conserve limited resources...