Gemina Filetag

MCP设计创作

提供方 tommyil

设计创作 未标注 API Key 社区 / 第三方 CursorCodexZed

Gemina FileTag Tag, rename, and enrich PDFs and images with structured metadata extracted via OCR + LLM. Built for AI agents that need to make sense of unstructured document piles. What it does - Tag — extract structured fields (title, date, party names, document type, language, summary, etc.) from any PDF or image. - Rename — generate descriptive filenames from extracted metadata. -

一句话选型结论

按资料字段整理

Gemina Filetag 属于设计创作类 MCP 服务器,传输方式未标注,API Key,可直接接入 Cursor、Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

pdf image ocr metadata document processing file management llm

支持客户端

适用场景

pdfimageocr

安装与配置

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

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
出图与素材

生成配图、图标与素材。

设计稿处理

读取设计稿、批量改尺寸或导出。

内容生成

按主题生成文案与视觉草稿。

选择建议

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

值得选的地方

  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gemina Filetag当前 未标注 未标注 未标注 无 未标注
Cursor Talk To Figma MCP Da1c7911 40 未标注 未标注 无 2026-05-17
Blender MCP 17 stdio · 本地进程 本地部署 有 2026-05-18
Nova Canvas MCP Server 2 stdio · 本地进程 本地部署 有 2026-05-17
Figma Context MCP 3aaa8d28 未标注 未标注 支持远程部署 无 2026-05-17
kreuzberg 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

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

详细介绍

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

Gemina — MCP server

Tag, extract, and search your documents from any MCP client. Free tier: 1,500 FileTag tags/month, no credit card.

Install • Examples • Product page • Full docs


What is this?

This repository is the discovery, install, and examples surface for Gemina's MCP server. The server itself is hosted at https://api.gemina.co/api/v1/mcp/ — there is no daemon to run locally. Point your MCP-compatible client at the endpoint, sign in with your Gemina account (or paste an API key for headless use), and tag your first document in under a minute.

One server, three tool groups: FileTag (free tier — tag, rename, and enrich any PDF or image), Extraction (Core-OCR: invoice headers, line items, full text, custom templates), and Document Intelligence (ask questions and run spend analytics over your indexed documents — no re-upload). See Tools for the full list.

The server itself is closed-source (operated by Gemina). Everything in this repo — install snippets, examples, integration code — is MIT-licensed and contributions are welcome.

What you get

One sign-in, three tool groups. Every group takes any PDF or image up to 50 MB (PDF, PNG, JPEG, GIF, WebP, HEIC/HEIF, AVIF).

1. FileTag — tag, rename, enrich (free tier). Send a document, get structured metadata, six suggested filenames, and a downloadable copy with the metadata embedded in the file itself. Tools: files_create_upload → tag_file, or tag_url.

2. Extraction — pull the fields out (paid). Ready-made models for invoice headers and invoice line items (plus Hebrew document details and line items); and custom templates — you define the fields, Gemina extracts them from any document type: contracts, forms, statements, delivery notes, IDs, anything. Tools: files_create_upload (purpose='extract') → extract_document → get_extraction_result, list_extractions, get_extraction, get_document, add_document_extractions (run more extraction types on a stored document — no re-upload; wait for the values, or wait=false and just file it for later search), submit_extraction_feedback (send corrections back).

3. Document Intelligence — ask your archive (paid). Ask questions and run spend analytics across your whole indexed collection — no re-upload. Every document you tag (FileTag) or run a structured extraction on is submitted for indexing when indexing is enabled — plain OCR isn't, and a document can be skipped (no extractable fields, or no indexing credits). Search by vendor, date, amount, type or free text (query_documents); get sums, averages and counts grouped by vendor, currency, type or month (aggregate_documents) — e.g. “total spent per vendor last quarter”. Tools: query_documents, aggregate_documents, index_document.

Sample: FileTag output (click to expand)```json
{
"document_id": "abc-123",
"suggested_filename": "2026-02-15_Acme-Corp_Invoice_12345.pdf",
"metadata": {
"document_type": "invoice",
"vendor": "Acme Corp",
"date": "2026-02-15",
"amount": 7200,
"currency": "ILS",
"document_number": "12345",
"title": "Invoice",
"tags": ["vendor", "invoice"]
},
"filename_patterns": {
"date_first": "2026-02-15_Invoice_12345.pdf",
"type_first": "Invoice_12345_2026-02-15.pdf",
"vendor_first": "Acme-Corp_Invoice_2026-02-15.pdf",
"date_vendor": "2026-02-15_Acme-Corp.pdf",
"vendor_date": "Acme-Corp_2026-02-15.pdf",
"compact": "Acme-Corp_Invoice.pdf"
},
"enriched_file_url": "https://api.gemina.co/files/tmp_abc123.pdf",
"enriched_file_expires_at": "2026-02-15T12:15:00Z"
}


Sample: extraction output (abridged — extract_document with invoice_headers)```json
{
  "status": "success",
  "meta": { "extractionType": "invoice_headers", "modelType": "invictus", "extractionId": "…" },
  "values": {
    "vendorName":   { "value": "Acme Office Supplies Ltd.", "confidence": 0.98 },
    "documentDate": { "value": "2026-02-15" },
    "docNumber":    { "value": "12345" },
    "netAmount":    { "value": 692.31 },
    "vatAmount":    { "value": 117.69 },
    "totalAmount":  { "value": 810.00 },
    "currency":     { "value": "USD" }
  },
  "document": { "documentId": "…", "externalId": "your-idempotency-key" }
}

With custom_template, values contains exactly the fields you defined in the template.

Sample: Document Intelligence (abridged — aggregate_documents)```json
{
"rows": [
{ "group": { "vendor_name": "Acme Office Supplies Ltd.", "currency": "USD" }, "values": { "sum_total_amount": 810.0, "count": 1 } },
{ "group": { "vendor_name": "BluePeak Cafe", "currency": "USD" }, "values": { "sum_total_amount": 26.19, "count": 1 } }
]
}


## Quick install

**Sign in with your Gemina account** — no API key to copy. Every snippet below points your client at the endpoint; the client discovers Gemina's authorization server and opens a browser sign-in. Don't have an account? Create one free (no credit card) at **https://console.gemina.co/registration/create-account**.

Running headless (CI, servers, scripts, or a client that doesn't prompt to sign in)? Use the **API-key form** shown under each client instead.

**Endpoint:** `https://api.gemina.co/api/v1/mcp/` · **Transport:** Streamable HTTP · **Auth:** OAuth 2.1 sign-in (default) *or* `X-API-Key` header (headless)

How OAuth sign-in works (click to expand)

- Clients discover the authorization server from the MCP URL via RFC 9728 (protected-resource metadata) and RFC 8414 (authorization-server metadata):
  - `https://api.gemina.co/.well-known/oauth-protected-resource/api/v1/mcp`
  - `https://api.gemina.co/.well-known/oauth-authorization-server/api/v1/mcp`
- Dynamic Client Registration (DCR) and Client ID Metadata Documents (CIMD) are both supported — no pre-registration, no client ID/secret to paste.
- Scope: `mcp`. Access tokens last 1 hour; refresh tokens rotate and last 30 days.
- Each connected app gets its own API key named ` (OAuth)`. See and revoke them under **Console → API Keys → Connected apps** at https://console.gemina.co.
- Most hosts need nothing beyond the URL. Three need an explicit second step — **Codex CLI**, **OpenClaw** and **Hermes-Agent** (see their sections) — and three can't sign in at all: **Cline** (no documented OAuth for remote servers as of 2026-08-27), **curl** and the **OpenAI Responses API** (no browser). **ChatGPT** is the mirror case: it signs in, but cannot send an API key.

Claude Desktop / claude.ai

**Recommended: OAuth via Connectors.** claude.ai and Claude Desktop use the same flow — no config file, no `mcp-remote`, no API key. Gemina creates a key for the app when you approve it.```text
URL: https://api.gemina.co/api/v1/mcp/

1. Customize → Connectors
2. Add → Add custom connector
3. Paste the URL
4. Sign in

Sign in with your Gemina account when prompted and approve the consent page. The Gemina tools appear in new chats immediately.

Fallback: API key via mcp-remote. Claude Desktop's Connectors UI doesn't accept custom headers, so an API key has to go through the mcp-remote stdio bridge. Use this only if you need a specific key (headless or shared machines).

Prerequisites

  1. Node.js 18+ — install from nodejs.org (Windows: ensure "Add to PATH" stays checked; macOS/Linux: standard installer).
  2. Claude Desktop capabilities — open Settings → Capabilities and turn on:
    • Code execution and file creation
    • Allow network egress
    • Domain allowlist: All domains (or add storage.googleapis.com to the narrow allowlist — that's where signed enriched-file URLs are hosted).

Without network egress, tag_file/tag_url return JSON correctly but Claude can't fetch the enriched-file URL from storage and you'll see "Host not in allowlist". Settings only apply to new chats — start a fresh conversation after toggling.

Config

In Claude Desktop, Settings → Developer → Edit Config opens claude_desktop_config.json at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Merge the mcpServers block alongside any existing config:```json
{
"mcpServers": {
"gemina": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.gemina.co/api/v1/mcp/",
"--header",
"X-API-Key:${GEMINA_API_KEY}"
],
"env": {
"GEMINA_API_KEY": "<paste-your-key-here>"
}
}
}
}


Save → fully quit Claude Desktop (Cmd+Q / right-click tray → Quit) → relaunch. First launch may take 10–30s while `npx` downloads `mcp-remote`.

**Notes**

- No space after `X-API-Key:` in the `--header` arg — it&#x27;s the documented workaround for `npx`&#x27;s shell-split parsing.
- The env-var indirection (`${GEMINA_API_KEY}`) keeps the literal key out of `args`, where it could leak via process listings.
- **Windows + `spawn npx ENOENT`**: Claude Desktop doesn&#x27;t inherit your shell&#x27;s PATH. Replace `&quot;command&quot;: &quot;npx&quot;` with the absolute path from `where npx` in PowerShell (forward slashes work in JSON), e.g. `&quot;C:/Program Files/nodejs/npx.cmd&quot;`.

Claude Code (CLI)

**OAuth (default):** register the server, then run `/mcp` and sign in — Claude Code opens the Gemina sign-in in your browser.```bash
claude mcp add --transport http gemina https://api.gemina.co/api/v1/mcp/
# then run /mcp and sign in

Inside Claude Code: /mcp → select gemina → Authenticate → sign in with your Gemina account in the browser → approve the consent page.

API key (headless):```bash
claude mcp add --transport http gemina https://api.gemina.co/api/v1/mcp/ \
--header "X-API-Key: <paste-your-key-here>"


Cursor

File: `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project). Cursor registers itself dynamically and opens your browser on the first 401 — no client ID or secret in the file.

**OAuth (default):**```json
{
  &quot;mcpServers&quot;: {
    &quot;gemina&quot;: {
      &quot;url&quot;: &quot;https://api.gemina.co/api/v1/mcp/&quot;
    }
  }
}

API key (headless):```json
{
"mcpServers": {
"gemina": {
"url": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}


VS Code

File: `.vscode/mcp.json` (per workspace), or run **MCP: Open User Configuration** from the Command Palette for all of them. VS Code registers dynamically and opens a browser on first connection; confirm the trust prompt, then find the account under **Accounts → Manage Trusted MCP Servers**.

**OAuth (default):**```json
{
  &quot;servers&quot;: {
    &quot;gemina&quot;: {
      &quot;type&quot;: &quot;http&quot;,
      &quot;url&quot;: &quot;https://api.gemina.co/api/v1/mcp/&quot;
    }
  }
}

API key (headless):```json
{
"servers": {
"gemina": {
"type": "http",
"url": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}


Cline

In Cline&#x27;s MCP settings (gear icon → MCP Servers → Edit Config), add:

**OAuth (default):**

&gt; **Cline is API-key only.** As of 2026-08-27 Cline has no documented OAuth path
&gt; for remote MCP servers — its MCP docs never mention OAuth, and the one release
&gt; note that does (v4.1.7) names the legacy SSE transport, not `streamableHttp`.
&gt; Use the API-key form below.

**API key (headless):**```json
{
  &quot;mcpServers&quot;: {
    &quot;gemina&quot;: {
      &quot;type&quot;: &quot;streamableHttp&quot;,
      &quot;url&quot;: &quot;https://api.gemina.co/api/v1/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;X-API-Key&quot;: &quot;&lt;paste-your-key-here&gt;&quot;
      }
    }
  }
}

Windsurf

File: ~/.codeium/windsurf/mcp_config.json, or the MCPs icon in the Cascade panel. Remote servers take serverUrl (url also works), then reload the MCP list. Now shipped as Devin Desktop — the Windsurf docs redirect there.

The docs say Cascade "supports OAuth for each transport type" but describe no explicit sign-in step, so if no browser prompt appears, use the API-key form.

OAuth (default):```json
{
"mcpServers": {
"gemina": {
"serverUrl": "https://api.gemina.co/api/v1/mcp/"
}
}
}


**API key (headless):**```json
{
  &quot;mcpServers&quot;: {
    &quot;gemina&quot;: {
      &quot;serverUrl&quot;: &quot;https://api.gemina.co/api/v1/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;X-API-Key&quot;: &quot;&lt;paste-your-key-here&gt;&quot;
      }
    }
  }
}

Codex CLI

OAuth (default):```bash
codex mcp add gemina --url https://api.gemina.co/api/v1/mcp/
codex mcp login gemina


`codex mcp add` detects OAuth on the URL and usually starts the browser sign-in by itself; `codex mcp login` is the documented guarantee. Do **not** paste a bare `[mcp_servers.gemina]` block for OAuth — Codex will connect to the server *unauthenticated* and every tool call fails. Verified against codex-cli 0.150.1 on 2026-08-27.

For the API-key lane, append to `~/.codex/config.toml`:

**API key (headless):**```toml
[mcp_servers.gemina]
url = &quot;https://api.gemina.co/api/v1/mcp/&quot;
http_headers = { &quot;X-API-Key&quot; = &quot;&lt;paste-your-key-here&gt;&quot; }

OpenClaw

OAuth (default):```bash
openclaw mcp set gemina '{"url":"https://api.gemina.co/api/v1/mcp/","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login gemina


Both lines are required. `mcp set` stores the server with `auth: &quot;oauth&quot;`; `mcp login` runs the flow — OpenClaw does not start OAuth off a 401 on its own. On a headless box, pass the code back with `openclaw mcp login gemina --code `, and check it with `openclaw mcp doctor gemina --probe`.

**API key (headless):**```bash
openclaw mcp set gemina &#x27;{&quot;url&quot;:&quot;https://api.gemina.co/api/v1/mcp/&quot;,&quot;transport&quot;:&quot;streamable-http&quot;,&quot;headers&quot;:{&quot;X-API-Key&quot;:&quot;&lt;paste-your-key-here&gt;&quot;}}&#x27;

Hermes-Agent

Append under mcp_servers in ~/.hermes/config.yaml:

OAuth (default):```yaml
mcp_servers:
gemina:
url: "https://api.gemina.co/api/v1/mcp/"
auth: oauth


Then run `hermes mcp login gemina` from a **fresh** terminal, not inside a live session — the in-session config reload times out at 30s, too short for a browser sign-in. The `auth: oauth` line is what turns OAuth on; Hermes never infers it from a 401.

**API key (headless):**```yaml
mcp_servers:
  gemina:
    url: &quot;https://api.gemina.co/api/v1/mcp/&quot;
    headers:
      X-API-Key: &quot;&lt;paste-your-key-here&gt;&quot;

Grok

xAI's coding agent. Install with curl -fsSL https://x.ai/cli/install.sh | bash. OAuth triggers a browser flow on first use; tokens cache in ~/.grok/mcp_credentials.json. On grok.com instead: Connectors → New Connector → Custom, paste the URL.

OAuth (default):```bash
grok mcp add --transport http gemina https://api.gemina.co/api/v1/mcp/


**API key (headless):**```bash
grok mcp add --transport http gemina https://api.gemina.co/api/v1/mcp/ \
  --header &quot;X-API-Key: &lt;paste-your-key-here&gt;&quot;

Gemini CLI

Google's terminal agent. Add -s user to install Gemina for every project. Nothing to configure for OAuth — the default dynamic_discovery provider registers itself off the 401 and opens your browser; tokens cache in ~/.gemini/mcp-oauth-tokens.json. Re-run the sign-in with /mcp auth gemina.

OAuth (default):```bash
gemini mcp add --transport http gemina https://api.gemina.co/api/v1/mcp/


**API key (headless):**```bash
gemini mcp add --transport http \
  --header &quot;X-API-Key: &lt;paste-your-key-here&gt;&quot; \
  gemina https://api.gemina.co/api/v1/mcp/

n8n

Workflow automation, cloud or self-hosted. Use the MCP Client Tool node under an AI Agent, or MCP Client for a plain workflow step. For OAuth, create an MCP OAuth2 API credential and leave Dynamic Client Registration on with Resource URL empty — n8n registers itself with Gemina. Needs MCP Client Tool node v1.2 or later.

OAuth (default):```text
URL: https://api.gemina.co/api/v1/mcp/

  1. Add the MCP Client Tool node (under an AI Agent), or MCP Client for a plain step
  2. MCP Endpoint URL: paste the URL above
  3. Server Transport: HTTP Streamable
  4. Authentication: MCP OAuth2
  5. Credentials -> create an "MCP OAuth2 API" credential; leave Dynamic Client
    Registration on and Resource URL empty
  6. Click sign in, approve Gemina in the browser, then set Tools to Include

**API key (headless):**```text
URL: https://api.gemina.co/api/v1/mcp/

1. Add the MCP Client Tool node (under an AI Agent), or MCP Client for a plain step
2. MCP Endpoint URL: paste the URL above
3. Server Transport: HTTP Streamable
4. Authentication: Header Auth -&gt; Name: X-API-Key, Value: &lt;paste-your-key-here&gt;
5. Set Tools to Include (All, or a subset)

Copilot Studio

Microsoft's agent builder — a browser wizard, no config file. Dynamic discovery is the right lane: Gemina publishes DCR and the discovery documents, so no client ID, secret or endpoint URL has to be typed. Copilot Studio supports the Streamable transport only. MCP access flows through Power Platform connectors, so tenant DLP policies apply.

OAuth (default):```text
URL: https://api.gemina.co/api/v1/mcp/

  1. In your agent: Tools -> Add a tool -> New tool -> Model Context Protocol
  2. Server name: Gemina
  3. Server URL: paste the URL above
  4. Authentication: OAuth 2.0 -> Type: Dynamic discovery
  5. Create -> Create a new connection -> Add to agent

**API key (headless):**```text
URL: https://api.gemina.co/api/v1/mcp/

1. In your agent: Tools -&gt; Add a tool -&gt; New tool -&gt; Model Context Protocol
2. Server name: Gemina
3. Server URL: paste the URL above
4. Authentication: API key -&gt; Type: Header -&gt; Name: X-API-Key
5. Create -&gt; Create a new connection (paste &lt;paste-your-key-here&gt;) -&gt; Add to agent

Zapier

Connects Gemina's tools to 8,000+ apps through the MCP Client app (Beta). A connection form, not a config file.

> Bearer only. Zapier has no custom-header field, so the key goes in the Bearer Token box — Gemina accepts it as Authorization: Bearer. There is no X-API-Key lane here.

OAuth (default):```text
URL: https://api.gemina.co/api/v1/mcp/

  1. Apps -> + Add connection -> MCP Client -> Add connection
  2. Server URL: paste the URL above
  3. Transport: Streamable HTTP
  4. OAuth: Yes (leave Bearer Token blank)
  5. Continue, then sign in to Gemina in the tab that opens

**API key (headless):**```text
URL: https://api.gemina.co/api/v1/mcp/

1. Apps -&gt; + Add connection -&gt; MCP Client -&gt; Add connection
2. Server URL: paste the URL above
3. Transport: Streamable HTTP
4. OAuth: No
5. Bearer Token: &lt;paste-your-key-here&gt;

ChatGPT

Add Gemina as a custom MCP app in ChatGPT on the web. Needs Developer mode and a Pro, Plus, Business, Enterprise or Edu account.

> OAuth only. ChatGPT cannot send a custom header or an API key to a remote MCP server, so there is no headless lane here — sign in instead, or use Codex CLI if you need a specific key.

Setup steps:```text
URL: https://api.gemina.co/api/v1/mcp/

  1. Settings -> Security and login -> turn on Developer mode
  2. Go to chatgpt.com/plugins and select +
  3. Name it "Gemina" and paste the URL above under Connection
  4. Create, then sign in to Gemina when ChatGPT prompts

OpenAI Responses API

For embedding Gemina in your own product: one tool entry turns the whole Gemina surface into an OpenAI-side capability.

&gt; **API key only.** This is a server-side lane with no browser, so there is no OAuth sign-in to run — the API forwards a credential you already hold.

**API key:**```bash
curl https://api.openai.com/v1/responses \
  -H &quot;Content-Type: application/json&quot; \
  -H &quot;Authorization: Bearer $OPENAI_API_KEY&quot; \
  -d &#x27;{
    &quot;model&quot;: &quot;gpt-5.6&quot;,
    &quot;input&quot;: &quot;Extract the totals from the invoice I uploaded.&quot;,
    &quot;tools&quot;: [{
      &quot;type&quot;: &quot;mcp&quot;,
      &quot;server_label&quot;: &quot;gemina&quot;,
      &quot;server_url&quot;: &quot;https://api.gemina.co/api/v1/mcp/&quot;,
      &quot;headers&quot;: { &quot;X-API-Key&quot;: &quot;&lt;paste-your-key-here&gt;&quot; },
      &quot;require_approval&quot;: &quot;never&quot;
    }]
  }&#x27;

For the full machine-readable install guide (used by agents), see llms-install.md.

Free tier

Free tier: 1,500 FileTag tags per month. No credit card required. Sign up at gemina.co/filetag, then sign in from your MCP client — or grab an API key for headless use. The same key works for both MCP and the REST API.

Need more? Paid plans add larger monthly allowances, the extraction and document-intelligence tools, configurable data residency, and longer retention. See pricing.

Tools

One endpoint, 13 tools in three groups, plus 2 prompts. Every tool is listed for every key; the extraction and document-intelligence groups require a paid plan (see pricing). Anonymous discovery (tools/list, prompts/list) is available at https://api.gemina.co/api/v1/mcp/public/.

FileTag (free tier)

Tool What it does
files_create_upload Reserve a pre-signed PUT slot. Returns file_id, the upload URL, the headers to echo on the PUT, and a next_tool_call recipe — tag_file by default, extract_document with purpose=&#x27;extract&#x27;. One slot type: any slot works with either tool.
tag_file Run the FileTag pipeline on an uploaded slot: metadata, six filename patterns, and a short-lived enriched-file URL.
tag_url Fetch a public HTTPS URL server-side and tag it — the bytes never pass through the model context.

Extraction (Core-OCR)

Tool What it does
extract_document Run one or more extraction types on an uploaded slot (from files_create_upload): invoice_headers, invoice_line_items, custom_template, ocr (plain text; runs only on the praetorian model), plus the legacy document_details_hebrew / document_line_items_hebrew (praetorian-only, not recommended for new work). Model choice is a recommendation, not a rule: velox for headers, invictus with thinking for line items.
get_extraction_result Poll an asynchronous extraction by meta.correlationId.
list_extractions List past extractions, newest first, with filters and pagination.
get_extraction Fetch one extraction by id, including the full extracted data.
get_document Fetch one document by id, including all of its extractions.
add_document_extractions Run more extraction types on a document Gemina already stores (by id) — no re-upload; paid per extraction. Two modes: wait for the values (default), or wait=false to file the document for later search and return at once.
submit_extraction_feedback Send verified/corrected field values back — the extraction-quality feedback loop.

Document Intelligence

Tool What it does
query_documents Search your indexed documents: structured filters, semantic similarity, or hybrid (best default).
aggregate_documents Sums/averages/min/max/counts over indexed documents, grouped by vendor, currency, type, month, and more.
index_document (Re)index one document into the searchable index — after corrections or to backfill.

Prompts: explain_filename_patterns (the six filename patterns and when to use each) · explain_upload_flow (files_create_upload → PUT → tag_file).

The full reference for each group is in llms-install.md.

Use cases

Use case Tools Example
🧾 Invoice / receipt data entry extract_document (invoice_headers, invoice_line_items) → your accounting, ERP or spreadsheet examples/bulk-tag-folder
📄 Any document, your fields extract_document with a custom_template (contracts, forms, statements, delivery notes, IDs) — define the template in the console
📊 Questions over your archive query_documents, aggregate_documents ("total spend with vendor X in Q2") —
📥 Email attachment triage FileTag: tag inbound attachments, route to folders by vendor/type examples/gmail-attachment-triage
🔍 RAG ingestion FileTag metadata on vector-store entries so retrieval can filter by vendor, date, type examples/llamaindex-reader · examples/langchain-loader
📁 Bulk document filing FileTag: walk a directory, rename every file to a consistent pattern examples/bulk-tag-folder
⚡ Quickstart (curl) First tag in three minutes, no MCP client needed examples/curl-quickstart
🖥️ Claude Desktop walkthrough Step-by-step setup with screenshots examples/claude-desktop

Why Gemina, not a raw LLM call?

A naive "ask the model to read this PDF" pipeline breaks in production: hallucinated vendor names, inconsistent dates, no stable schema, no line-item arithmetic, no feedback loop, nothing to search afterwards.

Raw LLM Gemina
Structured output Free text, requires parsing Stable JSON schema per extraction type, or your own template fields
Line items Rows guessed from text Column-aware line-item extraction with totals reconciliation
Hallucinations Frequent Cross-checked, refuses when unsure; corrections fed back with submit_extraction_feedback
Search & totals Build your own index Every extraction indexed; query_documents / aggregate_documents
Filing DIY Six filename patterns + metadata-embedded copy (FileTag)
Data residency Wherever the model runs You pick the region per account: EU, US, Israel or Asia
Cost $$ per call Free tier: first 1,500 FileTag tags/month

Privacy & trust

  • No model training. Your documents are never used to train AI models — Gemina's or anyone else's.
  • 7-day deletion. Files are deleted within 7 days of upload (configurable per plan).
  • Encryption. AES-256 at rest, TLS 1.3 in transit.
  • Compliance. GDPR and CCPA compliant. Configurable data residency on paid plans.

Full details on the Gemina Trust Center.

Documentation

  • 📖 Full docs: gemina.co/docs/mcp — REST + MCP reference
  • 🤖 Agent install guide: llms-install.md — machine-readable, used by AI agents auto-discovering the server
  • 🔌 MCP manifest: gemina.co/.well-known/mcp.json
  • 🏷️ REST endpoint reference: gemina.co/docs.md

Community & support

  • 🐛 Bug reports
  • 🆘 Integration help
  • 💬 Discussions
  • ✉️ Email: info@gemina.co
  • 🔒 Security: see SECURITY.md

For aggregators and directory listings

The Dockerfile at the repo root is not for end users. It exists so directory operators (e.g. Glama's /mcp/servers/ tier) can build a container that introspects the public tool surface without provisioning credentials. The container runs mcp-remote against https://api.gemina.co/api/v1/mcp/public/ — a read-only discovery endpoint that serves initialize / tools/list / prompts/list to anonymous callers but refuses tools/call. End users should follow the Quick install section above and connect to the authenticated endpoint by signing in (or with their personal API key).

Contributing

Examples PRs welcome — see CONTRIBUTING.md. The server itself is closed-source, so PRs that touch the actual MCP server logic will be declined, but bug reports against the live server are very welcome.

License

The contents of this repository — install snippets, example code, documentation, configuration files, and sample assets — are released under the MIT License.

The Gemina MCP server itself is a hosted closed-source service operated by Gemina (https://gemina.co) and is not covered by this license. Use of the server is governed by Gemina's Terms of Service and Privacy Policy.

常见问题

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

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

Gemina Filetag 怎么在 Cursor、Codex、Zed 里配置?

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

Gemina Filetag 收费吗?

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

Gemina Filetag 需要 API Key 吗?

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

Gemina Filetag 支持哪些客户端?

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

Gemina Filetag 能提供哪些能力?

资料显示能力标签包括 pdf、image、ocr、metadata、document processing、file management。具体工具清单以官方文档为准。

Gemina Filetag 需要什么运行环境?

运行时为 Cross-platform。

热门专题

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

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