MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Let your agent chase the documents: create, chase, read and collect DokuTrak Document Requests.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 15/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 DokuTrak。按照 https://mcp.popnx.com/i/crackx17-dokutrak-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(app.dokutrak.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
DokuTrakhttps://app.dokutrak.com/api/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsDokuTrak
用 DokuTrak 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 DokuTrak,或回答中出现 DokuTrak 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
DokuTrakhttps://app.dokutrak.com/api/mcp开启新聊天,输入前先从插件列表中选择 DokuTrak
用 DokuTrak 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 DokuTrak,或回答中出现 DokuTrak 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user dokutrak https://app.dokutrak.com/api/mcp应能看到 DokuTrak 在列表中并显示已连接
用 DokuTrak 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 DokuTrak,或回答中出现 DokuTrak 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 DokuTrak 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 DokuTrak,或回答中出现 DokuTrak 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 DokuTrak 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 DokuTrak,或回答中出现 DokuTrak 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://app.dokutrak.com/api/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user dokutrak https://app.dokutrak.com/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"dokutrak": {
"url": "https://app.dokutrak.com/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"dokutrak": {
"type": "http",
"url": "https://app.dokutrak.com/api/mcp"
}
}
}Claude Code
claude mcp add --scope user dokutrak --env DOKUTRAK_API_KEY=your-value -- npx -y dokutrak-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"dokutrak": {
"command": "npx",
"args": [
"-y",
"dokutrak-mcp"
],
"env": {
"DOKUTRAK_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"dokutrak": {
"command": "npx",
"args": [
"-y",
"dokutrak-mcp"
],
"env": {
"DOKUTRAK_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"dokutrak": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"dokutrak-mcp"
],
"env": {
"DOKUTRAK_API_KEY": "your-value"
}
}
}
}DOKUTRAK_API_KEY 机密 必填 envDOKUTRAK_API_URL env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
prepare_requestPrepare or edit recipient, checklist, deadline and optional message before connecting. No request is created and nothing is sent. Keep the returned preview through connection, then pass it unchanged to review_request. Missing or invalid details must be corrected.
review_requestAfter connection, submit the unchanged preview and a stable UUID operation_id. Open reviewUrl for the Professional to review and explicitly confirm in DokuTrak. Reuse the operation_id for retries. Changed details require a new operation and confirmation. No request or email is cr
send_requestSend only after the Professional confirms the exact version on reviewUrl. Use operation_id and version from review_request. Retries recover the same request. sent means accepted by the email provider, not delivery to the inbox. delivery_unknown requires inspection in DokuTrak; do
get_requestRead checklist receipt, Human Approval status, deadlines and recorded reminder progress. Give request_id or search the title, Client name or email. If several requests match, ask the Professional to select a candidate and call again with its id. Received does not mean approved. T
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Crackx17 验证,该账户拥有此仓库
代码最后更新于35天前
使用 MIT
在 58 毫秒内响应(HTTP 200)
无需登录
已读取 4 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 dokutrak-mcp@0.1.2 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/crackx17-dokutrak-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:DOKUTRAK_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于35天前,最新版本(0.1.2)于36天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 DokuTrak | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 是 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 5/5 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | MIT | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The open MCP connector for DokuTrak: let your agent chase the documents.
DokuTrak collects documents from your clients on your behalf: you send a request, the client uploads through a secure link, the files are reviewed, and silent clients get reminded. This connector puts that loop inside the agent you already work in, so "where does the Dupont file stand?" is answered without leaving Claude.
The connector is a thin, stateless client of the DokuTrak API. It holds the Agent Connection you give it, stores nothing on disk, keeps no cache, and duplicates no rule: what your agent may and may not do is decided by the service, and refusals come back as tool errors with the service's own explanation.
You need a DokuTrak workspace and an Agent Connection, issued from Settings → Connect an agent in the DokuTrak app. That screen hands you a paste-ready configuration with your key already in place; the instructions below are the same thing, by hand.
The key is read from the environment variable DOKUTRAK_API_KEY. It is never taken from the command line.
dokutrak.mcpb, the connector packaged as an MCP Bundle.DOKUTRAK_API_KEY.The bundle carries its own copy of the connector and runs on the Node.js built into Claude Desktop: no npx, no configuration file to edit. npm run bundle builds the same file from a clone.
Open the configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the server under mcpServers (create the object if the file is empty):
{
"mcpServers": { "dokutrak": { "command": "npx", "args": ["-y", "dokutrak-mcp"], "env": { "DOKUTRAK_API_KEY": "dk_live_…" } } } }
Restart Claude Desktop. The DokuTrak tools appear in the tools menu of a new conversation.
claude mcp add dokutrak -e DOKUTRAK_API_KEY=dk_live_… -- npx -y dokutrak-mcp
Then /mcp inside Claude Code lists dokutrak and its tools.
/plugin install dokutrak --marketplace Crackx17/dokutrak-mcp
The plugin adds the hosted connector (you sign in to DokuTrak on first use) and the tax-season-document-chase skill: give Claude your client list, it builds each client's checklist by return type (W-2, 1099, Schedule C, rental, K-1, retiree…), shows you the whole batch to confirm, prepares one request per client for you to confirm in DokuTrak, sends them, and later reports who is still missing what. Nothing goes out without your confirmation.
Add https://app.dokutrak.com/api/mcp as a custom connector. You sign in to DokuTrak (or create an account) during the OAuth step. The hosted connector prepares a request, sends it only after you confirm it in DokuTrak, and tracks progress. It never returns file content. Downloading files stays with this local connector. Setup: dokutrak.com/connectors.
git clone https://github.com/Crackx17/dokutrak-mcp.git
cd dokutrak-mcp npm ci && npm run build
Then point the client at the built file instead of npx:
{
"mcpServers": { "dokutrak": { "command": "node", "args": ["/path/to/dokutrak-mcp/dist/cli.js"], "env": { "DOKUTRAK_API_KEY": "dk_live_…" } } } }
or, for Claude Code: claude mcp add dokutrak -e DOKUTRAK_API_KEY=dk_live_… -- node /path/to/dokutrak-mcp/dist/cli.js.
skills/dokutrak/SKILL.md teaches the agent the three everyday uses — ask a Client for documents, know where a request stands, chase on rejected files — and how to connect. It is what a DokuTrak user installs alongside the connector:
npx skills add Crackx17/dokutrak-mcp # the open agent-skills installer
cp -r skills/dokutrak ~/.claude/skills/dokutrak
| Variable | Required | Default | Meaning |
|---|---|---|---|
DOKUTRAK_API_KEY | yes | — | The Agent Connection, from Settings → Connect an agent. |
DOKUTRAK_API_URL | no | https://app.dokutrak.com/api | Base URL of the API. Ends in /api; the connector adds /v1. |
Four tools, one round trip: ask, chase, know, collect.
create_requestCreates a Document Request and sends it, in one call, so nothing is left created but unsent. Takes the client's email, a deadline (YYYY-MM-DD or an ISO datetime), the checklist of documents wanted, and an optional title and message. The email goes to the recipient given here and to nobody else; the client uploads through the secure link it contains. Under the hood this is the same two-step the DokuTrak app performs: create with sendEmail: false, then send. If the send fails, the error names the created request, which stays visible in the dashboard.
Nothing goes out without your yes. The email to a real client cannot be recalled, so the tool tells the agent to show you the recipient, the deadline, the checklist and the message, and to wait for your confirmation. The tool is also flagged so that the client asks you before every call: Claude Code prompts each time, even in auto or bypass mode, and Claude Desktop treats it as a tool that always needs approval. A client that ignores these flags is left with the instruction to the agent alone.
request_replacementChases the client on the rejected files of a request: flags them, moves the request back to awaiting the client, and returns it to the automatic reminder cadence. This call sends no email by itself; the reminders do, and DokuTrak has no way to email the client immediately, not even from the dashboard. The optional message is recorded in the request's audit trail and is not sent to the client. It refuses a request with no rejected file.
get_requestWhere a Document Request stands, in one call: status, the checklist, every collected file with its verdict (approved, rejected with the reviewer's reason, or pending), and the reminder state. Give a request_id, or a search term matching the title or the client's name or email. When several requests match, the tool returns the candidates and asks for the id.
download_documentsEvery collected file of a request, as one zip archive. The archive comes back embedded in the tool result as binary content (an MCP resource with a base64 blob and application/zip), not as a link: the API has no short-link endpoint for a zip, and the connector writes nothing to disk. What the agent does with the bytes is decided on the professional's side, exactly like a download from the browser. Large archives make large results; check with get_request that documents have arrived before calling it.
Approving or rejecting a document is your decision, taken in the DokuTrak dashboard. No tool here can take it, and the service refuses it to any Agent Connection regardless of which connector asks. The same goes for billing, workspace settings and the management of API keys.
Revoking the Agent Connection in DokuTrak takes effect on the very next call: the connector answers with the service's 401 and nothing else.
The connector runs on your machine and talks to one service only: the DokuTrak API (https://app.dokutrak.com/api, or the URL you set in DOKUTRAK_API_URL), with the Agent Connection you configured. It sends what the tools need (the request you create, the id or search term you look up) and relays the answers to your agent. It writes nothing to disk, keeps no cache or log, and sends no telemetry or analytics to DokuTrak or to anyone else.
Everything it sends is processed by DokuTrak under the DokuTrak Privacy Policy, which covers what is collected, how it is used and stored, the subprocessors it is shared with, retention and deletion, and your rights. Questions: arthur@dokutrak.com; security issues: security@dokutrak.com.
npm ci
npm run check # typecheck, build, tests npm test # tests alone
The tests are contract tests at the MCP seam: a real MCP client and the real server, connected in memory through the official SDK's transport, with HTTP stubbed at fetch using recorded responses. They call tools, never functions, and run with no DokuTrak account and no network.
Before a release, the built binary is driven once against a real workspace, by a real MCP client over stdio: create → chase → read → collect → revoke → 401. It is a record pasted into the release PR, never a CI check (a blocking check calls no third party). It pauses twice for acts the service refuses to any Agent Connection: rejecting the uploaded file, and revoking the key.
npm run build
DOKUTRAK_API_KEY=dk_live_… STAGING_RECIPIENT_EMAIL=you@example.com npm run staging
A real Document Request is created and a real email goes to STAGING_RECIPIENT_EMAIL. The transcript lands in staging-run- .md (git-ignored); the key is never written to it.
npm run bundle builds mcpb/server/index.cjs (the connector with every dependency inlined), starts it and checks that it lists exactly the tools declared in mcpb/manifest.json at the version of package.json, then validates the manifest and packs dokutrak.mcpb with the official mcpb CLI. CI runs it on every pull request, and the release workflow attaches dokutrak.mcpb to the GitHub release of each tag. A change to the tool surface or the version updates mcpb/manifest.json too.
A tag vX.Y.Z matching package.json and SERVER_VERSION triggers .github/workflows/release.yml: npm run check, npm publish (trusted publishing through GitHub's OIDC token, provenance attached), then the listing in the MCP Registry as io.github.Crackx17/dokutrak-mcp — the mcpName of package.json, which the registry checks against the published tarball. Running the workflow by hand does a --dry-run and publishes nothing.
MIT.