DocForge turns documents into structured data. Upload a PDF, image, or Office file and get fielded JSON back with per-field confidence scores. 95 templates (invoices, receipts, bank statements, ID docs), custom JSON Schema mode, auto-detect, natural-language instructions. Keyless demo tool included. Free 7-day trial.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
docforge_extract10 fields changedInput schema / properties / file_base64 / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / file_base64 / defaultAdded value: +nullInput schema / properties / file_base64 / descriptionPrevious value: -"The document, base64-encoded. Supported types: PDF, JPG,\nPNG, TIFF, BMP, DOCX, PPTX, HTML, MD, TXT."New value: +"Optional. The local document, base64-encoded.\nSupported types: PDF, JPG, PNG, TIFF, BMP, DOCX, PPTX, HTML,\nMD, TXT. Mutually exclusive with url."Input schema / properties / file_base64 / typeRemoved value: -"string"Input schema / properties / filename / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / filename / defaultAdded value: +nullInput schema / properties / filename / descriptionPrevious value: -"Original filename with extension (e.g. \"invoice.pdf\") —\nused for type detection."New value: +"Original filename with extension (e.g. \"invoice.pdf\") —\nrequired with file_base64 (used for type detection); ignored\nwith url= (derived from the link automatically)."Input schema / properties / filename / typeRemoved value: -"string"Input schema / properties / urlAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Public http(s) URL of your document — e.g. a Drive\nor S3 share link. PREFERRED: no base64, no context bloat.\nMutually exclusive with file_base64."
+}Input schema / requiredRemoved value: -[
- "file_base64",
- "filename"
-]docforge_demo2 fields changedInput schema / properties / file_base64 / descriptionPrevious value: -"Optional. Your document, base64-encoded. Omit to use\nthe bundled sample invoice."New value: +"Optional. Your local document, base64-encoded. Omit\nto use the bundled sample invoice."Input schema / properties / urlAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Public http(s) URL of your document — e.g. a Drive\nor S3 share link. Preferred over base64."
+}docforge_demo3 fields changedInput schema / properties / file_base64Added value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Your document, base64-encoded. Omit to use\nthe bundled sample invoice."
+}Input schema / properties / filenameAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Original filename with extension (e.g.\n\"invoice.pdf\") — required when file_base64 is given."
+}Input schema / properties / template / descriptionAdded value: +"Optional template name (see docforge_templates)."docforge_extract3 fields changedInput schema / properties / schema / descriptionPrevious value: -"Optional JSON Schema (string) — output conforms to it."New value: +"Optional JSON Schema (string) — output conforms to it\n(Pro-plan feature)."Input schema / properties / schema_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional layout ID from docforge.biz (upload an\nExcel/CSV spreadsheet and use its column headers as the field\nlist — any plan). Takes precedence over template."
+}Input schema / properties / template / descriptionPrevious value: -"Optional template name (see docforge_templates). If omitted\nalong with schema/instructions, DocForge auto-detects the\ndocument type."New value: +"Optional template name (see docforge_templates). If omitted\nalong with schema/schema_id/instructions, DocForge auto-detects\nthe document type."docforge_extract_url1 field changedInput schema / properties / schema_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+}docforge_accountdocforge_demodocforge_extractdocforge_extract_urldocforge_statusdocforge_templatesClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Turn any PDF into structured JSON via AI + OCR: invoices, bank statements, contracts.
Turn PDFs, scans and photos into a queryable database. Invoices, CVs, receipts, in bulk.
Extract, search and tag any document: invoices, receipts, contracts, templates. OAuth or API key.
Turn PDFs and images into typed fields — invoices, receipts, IDs and custom models — via Mindee OCR.
Add one secure layer between your agents and this server.
docforge_extract_url is explicitly marked as a compatibility alias and recommends using docforge_extract instead, creating direct overlap. This redundancy makes it unclear which tool to use and adds confusion. All other tools are distinct, but this one degrades the overall disambiguation.
All tools share the consistent 'docforge_' prefix. The suffixes are descriptive nouns (account, demo, extract, status, templates), but 'extract_url' is a variant of 'extract', breaking the pattern slightly. Overall naming is readable but not perfectly uniform.
Six tools is an appropriate size for a data extraction service. It covers core functionality without being overwhelming or too thin. Each tool has a clear purpose except for the redundant alias.
The tool set covers the main extraction workflow (demo, full extraction, status polling), account management, and template listing. The redundant docforge_extract_url occupies a slot that could be eliminated, but it does not create a significant gap. Minor missing features like template management or batch extraction are not essential for core use.
