Magic MCP vs Gemina FileTag — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Magic MCP vs Gemina FileTag
In-depth architectural comparison of the Magic MCP and Gemina FileTag MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Magic MCP
Developer Tools · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Gemina FileTag
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Magic MCP if you need specialized Developer Tools tools running via a local process. Choose Gemina FileTag if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Magic MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: TWENTY_FIRST_API_KEY, API_KEY_21ST.
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='extract'`. One slot type: any slot works with either tool.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Gemina FileTag belongs to Developer Tools using local stdio subprocess. Select Magic MCP when you need capabilities focused on developer tools and Gemina FileTag when you require tools for developer tools.
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.
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 reco…
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.
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.