· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Parsewise v1.0.3
Extract from document sets
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Extract key fields from my documents with citations.
Developer declarations; not independently tested. Listing last checked Nov 13, 2026. Package observed Nov 12, 2026.
From the marketplace listing
Extract data from document sets with citations. Turn collections of contracts, reports, invoices, and other documents into structured results you can trace back to the source. Define the fields you need, compare information across documents, calculate derived metrics, and investigate missing or inconsistent results. Organise your document sets in Parsewise projects and track extraction progress directly from your assistant.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
parsewise documents extraction document-intelligence citations mcp
Extract data from document sets with citations. Turn collections of contracts, reports, invoices, and other documents into structured results you can trace back to the source. Define the fields you need, compare information across documents, calculate derived metrics, and investigate missing or inconsistent results. Organise your document sets in Parsewise projects and track extraction progress directly from your assistant.
Extract from document sets
Extract data from document sets with citations.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Talonic helps users turn documents such as PDFs, scans, invoices, contracts, certificates, statements, and forms into schema-validated JS...
Shared terms: extract, document, contract, extraction
Turn documents into structured data. Upload files, read extracted fields, and run document forensics in your fileAI workspace.
Shared terms: document, extract, field, invoice
Contract Information Extractor helps ChatGPT organize information explicitly stated in user-supplied contract text. It extracts contract ...
Shared terms: extract, contract, structured, result
Extracts explicitly written acceptance criteria from requirements, user stories, specifications, and testing notes. It returns structured...
Shared terms: extract, missing, structured, result
Big Documents Agent by Agints.com helps investigate private documents with cited evidence, add local files through a secure uploader, sea...
Shared terms: document, citation, collection, investigate
--- name: parsewise description: Work with Parsewise projects, documents, extraction and derived agents, dimensions, processing runs, and cited results through the Parsewise MCP server. Use when a user asks to work in Parsewise or explicitly delegates document extraction to Parsewise. --- # Parsewise Use the connected Parsewise MCP server to perform the requested document intelligence workflow. The server's discovered tools and input schemas describe the available operations; use the host's actual tool names, including any namespace prefix. This plugin connects the full MCP tool surface without a tool allowlist. ## Connect and orient The production endpoint is `https://api.parsewise.ai/mcp`, using Streamable HTTP and OAuth. Use the host's connection and sign-in flow. Access is scoped to the authenticated Parsewise organisation and permissions. Start with `list_projects` for existing work. Use returned IDs for subsequent calls. If the requested project is ambiguous, resolve it before making changes. Archived projects appear in `list_archived_projects` and must be restored before live project tools can access them. When the host supports MCP resources, read the relevant guide rather than loading all guides: - First extraction: `parsewise://guides/mcp-workflow`. - Choosing or changing row structure: `parsewise://guides/dimensions`. - Creating or editing agents: `parsewise://guides/agent-design`. - Improving results or deciding what to rerun: `parsewise://guides/agent-iteration`. - Confusing statuses or stalled processing: `parsewise://guides/troubleshooting`. - General concepts: `parsewise://guides/overview`. - Requests for Output Schemas: `parsewise://guides/schema-mapping`; this describes a separate HTTP API workflow, not additional MCP tools. If resource reading is unavailable, use the instructions below, current tool descriptions, and [Parsewise MCP documentation](https://docs.parsewise.ai/parsewise-mcp). Never invent a resource-reading tool. ## Projects and folders - Find, create, and edit projects with `list_projects`, `create_project`, and `update_project`; check progress with `get_project_processing_status` and capacity with `get_usage_limits`. - Use `archive_project`, `list_archived_projects`, and `restore_archived_project` for the archive lifecycle. Archiving hides a project but retains its documents, agents, and results. - Organise projects with `list_project_folders`, `create_project_folder`, `update_project_folder`, and `delete_project_folder`. Folder lists are flat; reconstruct hierarchy using `parent_id`. Deleting a folder removes its empty descendants and is blocked when the hierarchy contains live projects. ## Upload and inspect documents 1. Use `request_document_upload(project_id, file_names)` to request slots for up to 25 unique base filenames. Check current tool constraints for supported formats and size limits. 2. Send each selected file's raw bytes by HTTP `PUT` to its returned `upload_url`. Use the returned URL exactly; do not add the user's OAuth token or API key. Treat upload URLs as temporary credentials and avoid displaying or storing them in shared output. 3. After successful PUTs, call `finalize_document_upload(project_id, upload_ids)` with those slots. Finalization is atomic for the supplied IDs. Check the response: an input file can yield zero, one, or multiple documents, and existing filenames may be skipped. Requesting a slot does not upload a file, and sending bytes does not finalize it. If the host cannot perform the HTTP upload, direct the user to the project's Documents page in Parsewise, then resume with `list_documents` after upload. Use `list_documents` for IDs and parsing status, `get_document_summary_and_metadata` for an overview, and `get_document_page` for source text. Page numbers start at 1; large pages support character offsets. Use `delete_document` only for the intended removal: it also removes pages, storage files, and extraction data from that document. ## Configur
Preview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 12, 2026.
plugin_asdk_app_6abe6ff797808191b7731fdea93759ba
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.