Skip to main content
mcpSource-backedReview first Safety Privacy

MaxKB MCP Server

MCP endpoint in MaxKB that exposes a published MaxKB application as an authenticated tool, letting Claude send messages into a configured enterprise agent, RAG workflow, or knowledge-base-backed application.

by 1Panel-dev·added 2026-06-06·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • MaxKB checks the Authorization bearer token against active application API keys and only exposes published applications.
  • The MCP handler exposes one tool named from the published application id prefix and sends each tool call message into a new MaxKB chat session.
  • The published MaxKB application may retrieve knowledge-base content, call configured workflows or functions, use connected model providers, and trigger any tools enabled for that application.
  • Do not expose test applications, broad internal knowledge bases, high-privilege workflows, or unreviewed function tools to MCP clients.
  • Use least-privilege application keys, rotate keys regularly, avoid default deployment credentials, and require human approval before workflows that can change external systems.

Privacy notes

  • Tool calls can expose user prompts, chat transcripts, application names, application descriptions, retrieved knowledge-base snippets, workflow outputs, and model-provider payloads.
  • Knowledge bases may contain uploaded documents, crawled web pages, customer support material, internal runbooks, or other sensitive enterprise content.
  • Application API keys, bearer headers, MCP URLs, request bodies, response text, logs, and MaxKB chat history should be treated as sensitive operational data.
  • Redact prompts, retrieved passages, generated answers, application ids, API keys, and model-provider traces before sharing logs or screenshots.

Prerequisites

  • Running MaxKB v2 deployment with the web service reachable by the MCP client.
  • Published MaxKB application that is safe to expose as an MCP tool.
  • Active MaxKB application API key for that application.
  • Reviewed model provider, knowledge base, workflow, function, and MCP-tool settings inside the MaxKB application.
  • TLS, reverse proxy, access controls, and logging appropriate for the deployment environment.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
GPL-3.0-licensed open-source MaxKB project. The MCP endpoint is source-backed in the v2 branch; verify current MaxKB release notes and deployment settings before exposing production applications.
Full copyable content
{
  "mcpServers": {
    "maxkb": {
      "url": "https://<maxkb-host>/chat/api/mcp",
      "headers": {
        "Authorization": "Bearer <maxkb-application-api-key>"
      }
    }
  }
}

About this resource

Content

MaxKB MCP Server is the MCP endpoint built into MaxKB v2 for exposing a published MaxKB application as a tool. The source-backed handler implements MCP initialization, tool listing, and tool calls over the chat API path, then routes each call into a MaxKB chat session for the application tied to the supplied API key.

Use it when a team already runs MaxKB for enterprise agents, RAG workflows, or knowledge-base-backed applications and wants Claude to call one reviewed, published MaxKB application through an MCP client.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, v2 README, license, URL routing, MCP view, MCP tool handler, and application API key sources for current behavior.

Features

  • Expose a published MaxKB application as a single MCP tool.
  • Authenticate MCP calls with an active MaxKB application API key.
  • Return MCP server metadata with the maxkb-mcp server name.
  • List a generated agent_<application-prefix> tool using the application name and description.
  • Accept a message input and send it into a new MaxKB chat session.
  • Stream the MaxKB response back to the MCP client as text.
  • Keep the MCP tool scoped to the published application associated with the API key.
  • Follow the configured MaxKB chat path, with /chat/api/mcp as the default route in the reviewed source.

Installation

Deploy MaxKB, review the application that should be callable by Claude, publish that application, and create an active application API key for it. Then configure the MCP client with the MaxKB MCP endpoint and bearer token:

{
  "mcpServers": {
    "maxkb": {
      "url": "https://<maxkb-host>/chat/api/mcp",
      "headers": {
        "Authorization": "Bearer <maxkb-application-api-key>"
      }
    }
  }
}

If the deployment overrides MaxKB's CHAT_PATH, replace /chat with the configured chat path before connecting the MCP client.

Use Cases

  • Let Claude query a reviewed MaxKB knowledge-base application.
  • Route support questions into a MaxKB customer-service agent.
  • Call a MaxKB workflow application from Claude while keeping the agent configuration centralized in MaxKB.
  • Test a published MaxKB application from an MCP client before widening access.
  • Provide one scoped application tool instead of exposing the entire MaxKB admin surface.
  • Use MaxKB as the RAG and workflow runtime while Claude handles conversation planning.

Safety and Privacy

Treat the MaxKB MCP endpoint as access to the published application behind the API key. The application can retrieve knowledge-base material, call configured workflow steps, use model providers, and return tool output selected by the MaxKB app design. Review the application, knowledge sources, function tools, model providers, and workflow permissions before enabling MCP clients.

Protect application API keys like production credentials. MCP transcripts, chat history, retrieved passages, model payloads, workflow outputs, application ids, URLs, logs, and generated answers may contain sensitive business or personal data. Use TLS, least-privilege applications, key rotation, audit logs, and redaction before sharing prompts, screenshots, or debug traces.

Duplicate Check

No 1Panel-dev/MaxKB, MaxKB MCP, maxkb-mcp, MaxKB agent tool, or matching source URL entry was found in content/mcp or README.md. Existing RAG, knowledge-base, and workflow MCP entries do not cover MaxKB's built-in source MCP endpoint for published MaxKB applications.

#agents#rag#knowledge-base#workflow#django

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.