MCP-Document-Assistant

MCPAI代理

提供方 DCode-v05

AI代理 stdio · 本地进程 API Key 社区 / 第三方 Claude
查看接入方式

MCP Document Assistant is a terminal chat application that gives Claude direct, structured access to local documents through the Model Context Protocol, with @-mention context injection and /-command workflows for local document Q&A, summarization, and formatting.

一句话选型结论

按资料字段整理

MCP-Document-Assistant 属于AI代理类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

Local Deployment Model Context Protocol Claude Python Local document access Terminal chat Document Q&A Document summarization & formatting

支持客户端

适用场景

Local DeploymentModel Context ProtocolClaude

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
git clone https://github.com/DCode-v05/MCP-Document-Assistant.git cd MCP-Document-Assistant # Option A: uv (recommended) pip install uv uv venv source .venv/bin/activate # Windows: .venv\Scripts\activate uv pip install -e . # Option B: pip python -m venv .venv source .venv/bin/activate # Windows: .venv\Scripts\activate pip install anthropic python-dotenv prompt-toolkit "mcp[cli]>=1.8.0"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 python,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP-Document-Assistant当前 未标注 stdio · 本地进程 本地部署 有 2026-11-08
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方DCode-v05上游标注的维护方 DCode-v05
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-08上游最后核验时间

详细介绍

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

MCP Document Assistant

A command-line chat app that gives Anthropic's Claude direct, structured access to your local documents over the Model Context Protocol.

Overview

This is a terminal chat client that lets Claude work against a set of local documents instead of an isolated chat box. Rather than pasting file contents into a prompt every time, you mention a document with @ and the assistant pulls in its contents, or you run a /command that triggers a predefined workflow on the server side. Under the hood it talks to a local MCP server that owns the documents and exposes them through the three Model Context Protocol primitives: Resources, Tools and Prompts.

It's a focused, single-purpose app. The document store is a small in-memory set of sample files (a deposition, a report, financials, a spec and so on), so the project is really a compact working reference for how an LLM CLI wires up to an MCP server: the client/server split, the tool-use loop, context injection, and a prompt-toolkit UI with live autocompletion. It's module 5 ("Claude MCP") of a longer MCP learning series, and it's where I worked out the client-side agent loop and the @// patterns that later carried over into bigger MCP projects.

Key Features

  • Interactive Claude chat in the terminal. A REPL-style loop (>) backed by prompt-toolkit, with in-memory history, live completion menus and inline auto-suggestions.
  • @-mention context injection. Type @ to open an autocomplete menu of available documents. Mentioned docs are read from the MCP server and injected into the prompt inside `` tags before Claude sees the query.
  • /-command prompt workflows. Type / to list server-defined prompts (format_doc, summarize_doc), pass a document id, and the server returns a ready-made instruction sequence that's appended to the conversation.
  • Tool-use loop. Claude can call MCP tools on its own. The client runs each requested tool, feeds the result back, and repeats until Claude produces a final text answer.
  • Document tools. read_doc (read a document's contents) and edit_doc (search-and-replace edit on a document).
  • Document resources. A docs://documents list resource and a per-document docs://document/{doc_id} content resource, returned as JSON or plain text.
  • Server-side prompts. summarize_doc (concise summary) and format_doc (rewrite a document as Markdown using the edit tool).
  • Extra servers from the command line. The entry point can attach more MCP servers passed as arguments, and the tool manager aggregates tools across every connected client and routes each call to the client that owns the tool.
  • Cross-platform stdio transport. Client and server talk over stdio JSON-RPC, with a Windows-specific asyncio event-loop policy so it runs on Windows as well as Unix.

How It Works

The app is split into a client process (the CLI you talk to) and a server process (which owns the documents). They run separately and speak MCP over stdio.

MCP Server (mcp_server.py)

A FastMCP server named DocumentMCP. It holds an in-memory docs dictionary of sample documents keyed by id (deposition.md, report.pdf, financials.docx, outlook.pdf, plan.md, spec.txt). It registers:

  • Tools: read_doc(doc_id) returns a document's text; edit_doc(doc_id, old_str, new_str) does an in-place string replacement. Both raise a clear error if the id doesn't exist. Arguments are described with Pydantic Field metadata so the schema reaches the model.
  • Resources: docs://documents returns the list of ids as JSON; docs://document/{doc_id} returns a single document's contents as plain text.
  • Prompts: summarize_doc(doc_id) and format_doc(doc_id) return templated UserMessage instruction sequences. format_doc tells Claude to add headers, bullets and tables and to apply the changes via the edit tool without changing the meaning.

It runs with mcp.run(transport="stdio").

MCP Client (mcp_client.py)

A thin async wrapper around the MCP SDK's ClientSession and stdio_client. It starts the server as a subprocess (python mcp_server.py, or uv run mcp_server.py when USE_UV=1), initializes the session, and offers list_tools, call_tool, list_prompts, get_prompt and read_resource. read_resource decodes the first content block and parses JSON when the mime type is application/json. The client is an async context manager, so connect and cleanup are handled by an AsyncExitStack.

Chat orchestration (core/chat.py, core/cli_chat.py)

Chat runs the core agent loop:

  1. Add the user's processed query to the message list.
  2. Call Claude with the full message history plus the tools gathered from every connected client.
  3. If Claude's stop_reason is tool_use, run the requested tools, append the results as a user message, and loop again.
  4. Otherwise, extract the final text and return it.

CliChat extends this with the document-specific behaviour. _process_query first checks whether the input is a /command. If so, it fetches the matching server prompt with the given doc_id and converts the prompt messages into Anthropic message params. For a normal query, _extract_resources scans for @-mentions, reads each mentioned document from the server, and wraps the query and the document contents into one structured prompt that tells Claude to answer directly and not to mention the injected context.

Tool execution (core/tools.py)

ToolManager aggregates tools across all clients into Anthropic's tool schema, finds the client that owns a requested tool, calls it, and packages the output (or any error) into tool_result blocks the model can use. Tool failures are caught and returned as error results instead of crashing the loop.

Claude wrapper (core/claude.py)

A small wrapper over the anthropic SDK. It builds the messages.create call with max_tokens of 8000, an optional system prompt, tools, temperature and an optional extended-thinking budget, and has helpers to append user/assistant messages and pull text out of a response.

CLI front end (core/cli.py, main.py)

main.py loads config from .env (it requires CLAUDE_MODEL and ANTHROPIC_API_KEY and asserts on missing values), starts the document client plus any extra servers passed as arguments, and runs the app. CliApp builds the prompt-toolkit session: a UnifiedCompleter that suggests document ids after @ and command names after /, a CommandAutoSuggest that hints a prompt's argument, and custom key bindings on /, @ and space that open the completion menu at the right moments. On startup it refreshes the document and prompt lists from the server so completions match what the server actually exposes.

Tech Stack

  • Language: Python 3.10+ (requires-python in pyproject.toml)
  • AI / protocol: Anthropic Claude via the anthropic SDK; Model Context Protocol via the mcp[cli] SDK and FastMCP server
  • CLI / UX: prompt-toolkit (completion, history, key bindings, styling)
  • Supporting libraries: pydantic (tool/argument schemas), python-dotenv (config)
  • Transport: stdio JSON-RPC between client and server; asyncio with AsyncExitStack
  • Packaging / env: uv (recommended) with uv.lock, or plain pip

Getting Started

Prerequisites

  • Python 3.10 or newer
  • An Anthropic API key
  • uv (recommended) or pip

Installation```bash

git clone https://github.com/DCode-v05/MCP-Document-Assistant.git
cd MCP-Document-Assistant

Option A: uv (recommended)

pip install uv
uv venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
uv pip install -e .

Option B: pip

python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install anthropic python-dotenv prompt-toolkit "mcp[cli]>=1.8.0"


### Configuration

Create a `.env` file in the project root:```bash
ANTHROPIC_API_KEY="your_api_key_here"
CLAUDE_MODEL="your_claude_model_id"       # any Claude model id you have access to
# USE_UV=1                                # set to launch the server via "uv run"

Both ANTHROPIC_API_KEY and CLAUDE_MODEL are required. The app asserts on startup if either is missing.

Running```bash

uv

uv run main.py

plain python

python main.py


The client launches the MCP document server as a subprocess automatically. To attach extra MCP servers, pass their scripts as arguments: `uv run main.py path/to/other_server.py`.

## Usage

Once the `> ` prompt appears:

- **Ask a question.** Just type. Example: `What does the report say about the condenser tower?`
- **Reference a document.** Type `@` and pick from the menu; the contents are injected for you.
  > `Tell me about the budget in @financials.docx`
- **Run a server prompt.** Type `/` to list commands, then pass a document id.
  > `/summarize_doc deposition.md`
  > `/format_doc plan.md`
- **Exit.** `Ctrl-C` ends the session.

The built-in sample documents are `deposition.md`, `report.pdf`, `financials.docx`, `outlook.pdf`, `plan.md` and `spec.txt`. To use your own, edit the `docs` dictionary in `mcp_server.py`.

## Project Structure```
MCP-Document-Assistant/
├── main.py              # Entry point: loads .env, starts clients, runs the CLI loop
├── mcp_server.py        # FastMCP "DocumentMCP" server: docs + tools/resources/prompts
├── mcp_client.py        # Async MCP client wrapper over the stdio ClientSession
├── core/
│   ├── __init__.py
│   ├── chat.py          # Base agent loop (Claude call -> tool-use loop -> final text)
│   ├── cli_chat.py      # Document chat: @-mention injection, /command handling
│   ├── cli.py           # prompt-toolkit app: completer, key bindings, REPL
│   ├── claude.py        # Thin wrapper over the anthropic SDK
│   └── tools.py         # ToolManager: aggregate, route, and execute tool calls
├── pyproject.toml       # Project metadata and dependencies
├── uv.lock              # Locked dependency versions
├── .gitignore
└── README.md

Contact

Portfolio: DenistanLinkedIn: denistanb

GitHub: DCode-v05LeetCode: Denistan_B

Email: denistanb05@gmail.com

Made with ❤️ by Denistan B

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP-Document-Assistant 怎么安装?

在客户端按下面的安装命令接入:git clone https://github.com/DCode-v05/MCP-Document-Assistant.git cd MCP-Document-Assistant # Option A: uv (recommended) pip install uv uv venv source .venv/bin/activate # Windows: .venv\Scripts\activate uv pip install -e . # Option B: pip python -m venv .venv source .venv/bin/activate # Windows: .venv\Scripts\activate pip install anthropic python-dotenv prompt-toolkit "mcp[cli]>=1.8.0"。装完在客户端配置里引用同一个包或端点。

MCP-Document-Assistant 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP-Document-Assistant 收费吗?

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

MCP-Document-Assistant 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

MCP-Document-Assistant 支持哪些客户端?

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

MCP-Document-Assistant 能提供哪些能力?

资料显示能力标签包括 Local Deployment、Model Context Protocol、Claude、Python、Local document access、Terminal chat。具体工具清单以官方文档为准。

MCP-Document-Assistant 需要什么运行环境?

运行时为 python;属于本地进程,需要在本机装好运行环境。

MCP-Document-Assistant 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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