Knownbase

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 ClaudeCursorVS CodeWindsurf

持久化、可搜索的项目记忆,供AI智能体通过模型上下文协议使用。

一句话选型结论

按资料字段整理

Knownbase 属于文档知识类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Knownbase当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

5.7 KB
来自项目仓库与上游目录的原文,未做删改

Knownbase MCP Server

Persistent, searchable project memory for AI agents, over the Model Context Protocol.

Knownbase is a hosted MCP server that gives AI coding agents (Claude,
Cursor, ChatGPT, Claude Code, Windsurf, and any other MCP-compatible client) a place to read and
write durable notes, decisions, and handoffs that live outside your git history: the working
memory an agent otherwise loses the moment a session ends.

This repository documents the /mcp endpoint: how to connect, what tools it exposes, and how
authentication works. There is no local install: Knownbase is a remote, streamable-HTTP MCP
server, so connecting is just pointing your client at a URL.https://knownbase.dev/mcp

The problem this solves

AI agents are stateless between sessions. Every new chat, every new terminal, every restarted
IDE window starts from zero. The agent re-reads your code but has no memory of why things are
the way they are:

  • Architecture decisions and the tradeoffs behind them
  • Debugging trails ("we tried X, it didn't work because Y")
  • Conventions and gotchas that aren't obvious from the code itself
  • Task handoffs between sessions, or between you and a teammate's agent
  • Anything you don't want cluttering git history but still need the agent to know

Without a memory layer, you end up re-explaining the same context every session, or the agent
re-discovers (and re-breaks) the same thing twice. Knownbase gives the agent a workspace it can
search and write to directly, so that memory persists and compounds instead of resetting.

Quick start

  1. Create a free workspace at knownbase.dev (no card required).
  2. Connect your MCP client to https://knownbase.dev/mcp; see
    docs/CONNECTING_CLIENTS.md for exact steps per client
    (Claude, Claude Code, ChatGPT, Cursor, and generic MCP clients).
  3. Authenticate with either a static API key or OAuth 2.1 (most clients auto-discover OAuth);
    see docs/AUTHENTICATION.md.
  4. Start a task with get_context to load what's already known, write durable knowledge with
    remember, and fall back to search_notes / get_note / upsert_note for direct control.
    Full tool reference: docs/TOOLS.md.

What it exposes

Tool Purpose
list_projects List project categories and note counts in the workspace
get_context One-call project orientation: constraints, decisions, status, open items, and recent changes, ranked and packed to a token budget
search_notes Search by text, project, tag, status, or last-modified date (keyword; semantic search is coming soon, and semantic: true falls back to keyword until then)
get_note Read one note in full, with its links/backlinks
get_notes Batch-read up to 50 notes in one call
remember Store a durable fact/decision/constraint in one call: derives the title, checks for duplicates or contradictions, reports what it did
checkpoint Close a work session as structured durable state: summary, decisions, discoveries, open items, next actions
get_changes_since Resume from another agent, session, or machine via an opaque cursor, without reloading the project
upsert_note Create a note, or partially update an existing one
patch_note Change part of a body (append, prepend, or literal find-and-replace) without resending it
delete_note Soft-delete (trash) a note
list_note_revisions List a note's saved prior versions
get_note_revision Read the full body of one historical revision
workspace_info / usage_summary Plan, limits, usage, and this key's own access scope
rename_project Bulk-rename a project across every note
rename_tag Bulk-rename or remove a tag across every note
backup_project Export full content of one project inline, for backup/portability

Notes also carry optional typed, temporal metadata (decision / fact / constraint / …, plus
a current / superseded / disputed lifecycle) that get_context ranks and filters on. See
Typed, temporal memory in the tool reference.

Full parameter-level reference, including the lean-by-default response shapes designed to save
agent tokens, is in docs/TOOLS.md.

Why a remote, hosted MCP server

Every note is scoped to your own workspace; nothing is shared across tenants. Full-text search
runs server-side, so agents get results without loading your entire notes corpus into context.
Semantic (meaning-based) search is coming soon: search_notes already accepts semantic: true
and falls back to keyword search until it is available, and workspace_info reports
plan.semanticSearch so an agent can check first. Notes are versioned (every edit snapshots a
revision) and soft-deleted (trash, not permanently gone), so an agent's write is never a one-way
door.

Links

  • Homepage: what Knownbase is and who it's for
  • Features
  • Pricing: free tier (3 projects, 300 notes, 2 MCP keys), plus
    Go / Solo / Team / Business plans, each with a 7-day free trial
  • Blog: guides on MCP, agent memory, and handoffs
  • llms.txt: machine-readable product/endpoint summary
  • Contact · hello@knownbase.dev

Repository contents

  • docs/AUTHENTICATION.md: API keys, OAuth 2.1 flow, project-scoped keys
  • docs/CONNECTING_CLIENTS.md: per-client setup (Claude, Claude Code, ChatGPT, Cursor, others)
  • docs/TOOLS.md: full tool reference with input/output shapes
  • server.json: MCP Registry manifest

This repository documents a hosted service; it does not contain the Knownbase server's source
code. Found an issue with these docs, or a mismatch with actual server behavior? Please
open an issue or email
hello@knownbase.dev.

License

Documentation in this repository is MIT licensed. Use of the Knownbase service itself
is governed by its Terms of Service.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Knownbase 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Knownbase 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Knownbase 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Knownbase 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Knownbase 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Windsurf、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Knownbase 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。