Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Schema-driven document extraction with local OCR + LLM. Document in, Structured JSON out.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"docpick": {
"command": "uvx",
"args": [
"docpick"
]
}
}
}在终端中运行这条命令
claude mcp add docpick -- uvx docpick粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"docpick": {
"command": "uvx",
"args": [
"docpick"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"docpick": {
"type": "stdio",
"command": "uvx",
"args": [
"docpick"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
发布者(ArkNill)不是仓库所有者(QuartzUnit);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.2)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
한국어 문서 · llms.txt
Document in, Structured JSON out. Locally. With your schema.
docpick is a lightweight, schema-driven document extraction pipeline that combines local OCR engines with local LLMs to extract structured JSON from any document — invoices, receipts, bills of lading, tax forms, and more.
pip install docpick # core (LLM extraction only)
pip install docpick[paddle] # + PaddleOCR (recommended) pip install docpick[easyocr] # + EasyOCR (Korean-optimized) pip install docpick[got] # + GOT-OCR2.0 (GPU, vision-language) pip install docpick[all] # all OCR backends
Requirements: Python 3.11+ / LLM endpoint (vLLM, Ollama, or OpenAI-compatible)
from docpick import DocpickPipeline
from docpick.schemas import InvoiceSchema
pipeline = DocpickPipeline() result = pipeline.extract("invoice.pdf", schema=InvoiceSchema)
print(result.data) # Structured dict matching schema print(result.validation) # Validation errors/warnings print(result.confidence) # Per-field confidence scores
# Extract structured data
docpick extract invoice.pdf --schema invoice --output result.json
docpick ocr document.png --lang ko,en
docpick validate result.json --schema invoice
docpick batch ./documents/ --schema invoice --output ./results/ --concurrency 4
docpick schemas list
docpick schemas show invoice
| Schema | Document Type | Key Validations |
|---|---|---|
invoice | Commercial invoices | Line item sums, tax ID checkdigit, date order |
receipt | Retail/restaurant receipts | Total = subtotal + tax + tip |
bill_of_lading | Ocean/air B/L | Container weight sums, ISO 6346, HS code format |
purchase_order | Purchase orders | PO total = line items, delivery date order |
kr_tax_invoice | Korean e-tax invoice (세금계산서) | Business number checkdigit (x2), supply/tax/total sums |
bank_statement | Bank statements | IBAN mod97, period date order |
id_document | Passport/ID (ICAO 9303) | MRZ, ISO 3166 country codes, date ranges |
certificate_of_origin | Certificate of Origin | ISO 3166 alpha-2 country codes |
Define your own schema with Pydantic:
from pydantic import BaseModel
from docpick import DocpickPipeline from docpick.validation.rules import SumEqualsRule, RequiredFieldRule
class MyDocument(BaseModel): """Custom document schema.""" company_name: str | None = None total_amount: float | None = None tax_amount: float | None = None net_amount: float | None = None items: list[dict] | None = None
class ValidationRules: rules = [ RequiredFieldRule("company_name"), SumEqualsRule(["net_amount", "tax_amount"], "total_amount"), ]
pipeline = DocpickPipeline() result = pipeline.extract("my_document.pdf", schema=MyDocument)
Or use a JSON Schema file:
docpick extract document.pdf --schema my_schema.json
| Algorithm | Use Case |
|---|---|
kr_business_number | Korean business registration number (10 digits) |
luhn | Credit card numbers |
iso_6346 | Shipping container numbers |
iban_mod97 | International bank account numbers |
awb_mod7 | Air waybill numbers |
mrz | Machine Readable Zone (passport/ID) |
| Rule | Description |
|---|---|
SumEqualsRule | Sum of fields equals target (with tolerance) |
DateBeforeRule | Date A must precede Date B |
RequiredFieldRule | Field must be non-null and non-empty |
FieldEqualsRule | Two fields must be equal |
RangeRule | Numeric field within min/max bounds |
RegexRule | Field matches regex pattern |
Validate consistency across related documents (e.g., Invoice + B/L + Packing List):
from docpick.validation.cross_document import create_trade_document_validator
validator = create_trade_document_validator() result = validator.validate({ "invoice": invoice_data, "bl": bl_data, "packing_list": packing_list_data, "certificate": certificate_data, }) print(result.is_valid)
| Engine | Type | GPU | Languages | Best For |
|---|---|---|---|---|
| PaddleOCR | Traditional OCR | Optional | 111 | General documents (default) |
| EasyOCR | Traditional OCR | Optional | 80+ | Korean text |
| GOT-OCR2.0 | Vision-Language | Required | Multi | Complex layouts |
| VLM | Vision-Language | Required | Multi | Direct image → JSON |
The default auto engine uses confidence-based fallback:
If Tier 1 average confidence falls below threshold (default 0.7), automatically escalates to Tier 2.
| Provider | Endpoint | Default Model |
|---|---|---|
| vLLM | http://localhost:8000/v1 | Qwen/Qwen3.5-32B-AWQ |
| Ollama | http://localhost:11434 | qwen3.5:7b |
Configure via CLI or YAML:
docpick config set llm.provider ollama
docpick config set llm.base_url http://localhost:11434 docpick config set llm.model qwen3.5:7b
The pipeline is designed to be resilient:
result.errorsresult = pipeline.extract("damaged.pdf", schema=InvoiceSchema)
if result.errors: print("Pipeline warnings:", result.errors) if result.data: print("Partial extraction:", result.data)
Process entire directories with parallel workers:
from docpick.batch import BatchProcessor
from docpick.schemas import InvoiceSchema
processor = BatchProcessor(concurrency=4) result = processor.process_directory( "./invoices/", schema=InvoiceSchema, recursive=True, )
print(f"Processed {result.succeeded}/{result.total} files") for path, extraction in result.results.items(): print(f"{path}: {extraction.data.get('total_amount')}")
flowchart TD
A["📄 Document\n(PDF / Image)"] --> B["DocumentLoader\n(pypdfium2)"] B --> C["Tier 1: OCR\n(PaddleOCR / EasyOCR)\nCPU"] C --> D{"Confidence\n≥ threshold?"} D -->|"yes"| F["LLM Extractor\n(vLLM / Ollama)\nSchema prompt"] D -->|"no"| E["Tier 2: VLM\n(GOT / VLM)\nGPU"] E --> F F --> G["Pydantic Validation"] G --> H["✅ ExtractionResult"]
Apache 2.0 — all dependencies are Apache 2.0 or MIT licensed.
Part of the QuartzUnit ecosystem — composable Python libraries for data collection, extraction, search, and AI agent safety.