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.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access, third-party handling.
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.
{
"mcpServers": {
"maxkb": {
"url": "https://<maxkb-host>/chat/api/mcp",
"headers": {
"Authorization": "Bearer <maxkb-application-api-key>"
}
}
}
}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.
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.
maxkb-mcp server name.agent_<application-prefix> tool using the application name
and description.message input and send it into a new MaxKB chat session./chat/api/mcp as the default
route in the reviewed source.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.
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.
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.
Show that MaxKB MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/maxkb-mcp-server)MaxKB MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | 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. Open dossier | Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions. Open dossier | MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge. Open dossier | Apache-licensed TypeScript MCP server for Obsidian vaults with stdio and Streamable HTTP transports, Local REST API access, note search, section-aware edits, tag/frontmatter management, path policies, and read-only controls. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | 1Panel-dev | Agentset | Graphlit | cyanheads |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | 22k repo stars | — | — | — |
| 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. | ✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows. | ✓Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project. Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested. Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content. Generated audio and image publishing can call configured model/provider services and consume credits or quota. Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes. | ✓Cyanheads Obsidian MCP can read, list, search, create, append, patch, replace, delete, tag, and edit frontmatter in the configured vault through the Local REST API plugin. The server defaults to full-vault access unless read paths, write paths, or read-only mode are configured. Set `OBSIDIAN_READ_ONLY=true` for research-only workflows, then narrow writes with `OBSIDIAN_WRITE_PATHS` before allowing note edits. Delete operations are permanent in the vault and should require human review even when the MCP host supports destructive-tool prompts. Command-palette tools are disabled unless `OBSIDIAN_ENABLE_COMMANDS=true`; command execution can trigger opaque or destructive Obsidian plugin behavior. Streamable HTTP deployments should use JWT or OAuth auth before being exposed beyond a trusted local machine. |
| 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. | ✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files. | ✓Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client. Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot. Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content. Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations. Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data. | ✓Vault notes, headings, block references, frontmatter, tags, file metadata, outgoing links, search queries, command names, plugin status, and edit history may be exposed to the MCP client and model provider. API keys, local plugin endpoints, HTTP auth settings, path allowlists, logs, OpenTelemetry traces, and Docker environment variables can reveal private vault structure or credentials. Tag listing is vault-wide in upstream behavior and can reveal tag names outside narrowed read paths. Notes may contain personal journals, client work, credentials, meeting notes, research plans, health data, or other sensitive knowledge-base content. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Query Agentset RAG namespaces from Claude through the official `@agentset/mcp` server.
Connect Claude to Graphlit projects for ingestion, retrieval, web crawling, feeds, collections, conversations, memory, and RAG workflows.
Source-backed guides for putting this to work.
Use file checkpointing in the Claude Agent SDK: enable it, capture checkpoint UUIDs, and rewind files by resuming the session.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.