Gemina
Extract, search and tag any document: invoices, receipts, contracts, templates. OAuth or API key.
Open source Repository Open in the app JSON README (API)
About
Extract, search and tag any document: invoices, receipts, contracts, templates. OAuth or API key.
Details
- Kind
- MCP servers
- Topic
- Finance & crypto
- Publisher
- co.gemina
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 2.1.0
- Stars
- 1
- Last push
- 2026-08-30T15:44:29Z
- Repository state
- ativo
- Language
- Python
- License
- MIT
- Added
- 2026-08-29 03:00:51
- Updated
- 2026-09-07 14:36:04
- Origin id
co.gemina/gemina
README
<div align="center">
<img src="assets/logo/logo.svg" alt="Gemina" width="120" />
# Gemina — MCP server
**Tag, extract, and search your documents from any MCP client. Free tier: 1,500 FileTag tags/month, no credit card.**
[](LICENSE)
[](https://www.gemina.co/filetag)
[](https://modelcontextprotocol.io)
[](https://github.com/tommyil/gemina-mcp/commits/main)
[Install](#quick-install) • [Examples](./examples) • [Product page](https://www.gemina.co/product/agents) • [Full docs](https://www.gemina.co/docs/mcp)
</div>
---
## 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** (search and aggregate over your indexed documents). See [Tools](#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).** OCR for any document; 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_extraction_upload` → `extract_document` → `get_extraction_result`, `list_extractions`, `get_extraction`, `get_document`, `submit_extraction_feedback` (send corrections back).
**3. Document Intelligence — ask your archive (paid).** Every extraction is indexed. Search by vendor, date, amount, type or free text; get sums, averages and counts grouped by vendor, currency, type or month. Tools: `query_documents`, `aggregate_documents`, `index_document`.
<details>
<summary><b>Sample: FileTag output</b> (click to expand)</summary>
```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"
}
```
</details>
<details>
<summary><b>Sample: extraction output</b> (abridged — <code>extract_document</code> with <code>invoice_headers</code>)</summary>
```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.
</details>
<details>
<summary><b>Sample: Document Intelligence</b> (abridged — <code>aggregate_documents</code>)</summary>
```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 } }
]
}
```
</details>
## 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)
<details>
<summary><b>How OAuth sign-in works</b> (click to expand)</summary>
- 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 `<app> (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.
</details>
<details>
<summary><b>Claude Desktop / claude.ai</b></summary>
**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](https://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's the documented workaround for `npx`'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't inherit your shell's PATH. Replace `"command": "npx"` with the absolute path from `where npx` in PowerShell (forward slashes work in JSON), e.g. `"C:/Program Files/nodejs/npx.cmd"`.
</details>
<details>
<summary><b>Claude Code (CLI)</b></summary>
**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>"
```
</details>
<details>
<summary><b>Cursor</b></summary>
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
{
"mcpServers": {
"gemina": {
"url": "https://api.gemina.co/api/v1/mcp/"
}
}
}
```
**API key (headless):**
```json
{
"mcpServers": {
"gemina": {
"url": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}
```
</details>
<details>
<summary><b>VS Code</b></summary>
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
{
"servers": {
"gemina": {
"type": "http",
"url": "https://api.gemina.co/api/v1/mcp/"
}
}
}
```
**API key (headless):**
```json
{
"servers": {
"gemina": {
"type": "http",
"url": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}
```
</details>
<details>
<summary><b>Cline</b></summary>
In Cline's MCP settings (gear icon → MCP Servers → Edit Config), add:
**OAuth (default):**
> **Cline is API-key only.** As of 2026-08-27 Cline has no documented OAuth path
> for remote MCP servers — its MCP docs never mention OAuth, and the one release
> note that does (v4.1.7) names the legacy SSE transport, not `streamableHttp`.
> Use the API-key form below.
**API key (headless):**
```json
{
"mcpServers": {
"gemina": {
"type": "streamableHttp",
"url": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}
```
</details>
<details>
<summary><b>Windsurf</b></summary>
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
{
"mcpServers": {
"gemina": {
"serverUrl": "https://api.gemina.co/api/v1/mcp/",
"headers": {
"X-API-Key": "<paste-your-key-here>"
}
}
}
}
```
</details>
<details>
<summary><b>Codex CLI</b></summary>
**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 = "https://api.gemina.co/api/v1/mcp/"
http_headers = { "X-API-Key" = "<paste-your-key-here>" }
```
</details>
<details>
<summary><b>OpenClaw</b></summary>
**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: "oauth"`; `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 <code>`, and check it with `openclaw mcp doctor gemina --probe`.
**API key (headless):**
```bash
openclaw mcp set gemina '{"url":"https://api.gemina.co/api/v1/mcp/","transport":"streamable-http","headers":{"X-API-Key":"<paste-your-key-here>"}}'
```
</details>
<details>
<summary><b>Hermes-Agent</b></summary>
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: "https://api.gemina.co/api/v1/mcp/"
headers:
X-API-Key: "<paste-your-key-here>"
```
</details>
<details>
<summary><b>Grok</b></summary>
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 "X-API-Key: <paste-your-key-here>"
```
</details>
<details>
<summary><b>Gemini CLI</b></summary>
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 "X-API-Key: <paste-your-key-here>" \
gemina https://api.gemina.co/api/v1/mcp/
```
</details>
<details>
<summary><b>n8n</b></summary>
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 -> Name: X-API-Key, Value: <paste-your-key-here>
5. Set Tools to Include (All, or a subset)
```
</details>
<details>
<summary><b>Copilot Studio</b></summary>
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 -> Add a tool -> New tool -> Model Context Protocol
2. Server name: Gemina
3. Server URL: paste the URL above
4. Authentication: API key -> Type: Header -> Name: X-API-Key
5. Create -> Create a new connection (paste <paste-your-key-here>) -> Add to agent
```
</details>
<details>
<summary><b>Zapier</b></summary>
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 -> + Add connection -> MCP Client -> Add connection
2. Server URL: paste the URL above
3. Transport: Streamable HTTP
4. OAuth: No
5. Bearer Token: <paste-your-key-here>
```
</details>
<details>
<summary><b>ChatGPT</b></summary>
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
```
</details>
<details>
<summary><b>OpenAI Responses API</b></summary>
For embedding Gemina in your own product: one tool entry turns the whole Gemina surface into an OpenAI-side capability.
> **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 "Content-Type: application/json" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-d '{
"model": "gpt-5.6",
"input": "Extract the totals from the invoice I uploaded.",
"tools": [{
"type": "mcp",
"server_label": "gemina",
"server_url": "https://api.gemina.co/api/v1/mcp/",
"headers": { "X-API-Key": "<paste-your-key-here>" },
"require_approval": "never"
}]
}'
```
</details>
For the full machine-readable install guide (used by agents), see [`llms-install.md`](./llms-install.md).
## Free tier
**Free tier: 1,500 FileTag tags per month. No credit card required.** Sign up at [gemina.co/filetag](https://www.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](https://www.gemina.co/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](https://www.gemina.co/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 for a file you'll tag. Returns `file_id`, the upload URL, and the headers to echo on the PUT. |
| `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 |
|---|---|
| `files_create_extraction_upload` | Reserve a pre-signed PUT slot for extraction (distinct from the FileTag slot). |
| `extract_document` | Run one or more extraction types on an uploaded slot: `ocr`, `invoice_headers`, `invoice_line_items`, `document_details_hebrew`, `document_line_items_hebrew`, `custom_template`. |
| `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. |
| `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`](./llms-install.md#3-tools-exposed).
## 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`](./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](https://console.gemina.co) |
| 📊 **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`](./examples/gmail-attachment-triage) |
| 🔍 **RAG ingestion** | FileTag metadata on vector-store entries so retrieval can filter by vendor, date, type | [`examples/llamaindex-reader`](./examples/llamaindex-reader) · [`examples/langchain-loader`](./examples/langchain-loader) |
| 📁 **Bulk document filing** | FileTag: walk a directory, rename every file to a consistent pattern | [`examples/bulk-tag-folder`](./examples/bulk-tag-folder) |
| ⚡ **Quickstart (curl)** | First tag in three minutes, no MCP client needed | [`examples/curl-quickstart`](./examples/curl-quickstart) |
| 🖥️ **Claude Desktop walkthrough** | Step-by-step setup with screenshots | [`examples/claude-desktop`](./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](https://www.gemina.co/trust-center).
## Documentation
- 📖 **Full docs:** [gemina.co/docs/mcp](https://www.gemina.co/docs/mcp) — REST + MCP reference
- 🤖 **Agent install guide:** [`llms-install.md`](./llms-install.md) — machine-readable, used by AI agents auto-discovering the server
- 🔌 **MCP manifest:** [gemina.co/.well-known/mcp.json](https://www.gemina.co/.well-known/mcp.json)
- 🏷️ **REST endpoint reference:** [gemina.co/docs.md](https://www.gemina.co/docs.md)
## Community & support
- 🐛 [Bug reports](https://github.com/tommyil/gemina-mcp/issues/new?template=bug.yml)
- 🆘 [Integration help](https://github.com/tommyil/gemina-mcp/issues/new?template=integration_help.yml)
- 💬 [Discussions](https://github.com/tommyil/gemina-mcp/discussions)
- ✉️ Email: [info@gemina.co](mailto:info@gemina.co)
- 🔒 Security: see [SECURITY.md](./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`](https://www.npmjs.com/package/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](./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](./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](https://www.gemina.co/terms-of-service) and [Privacy Policy](https://www.gemina.co/privacy-policy).