docflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCFLOW_HOST | No | Docflow API host (default: https://docflow.textin.com) | https://docflow.textin.com |
| DOCFLOW_APP_ID | Yes | Your Docflow application ID | |
| DOCFLOW_SECRET_CODE | Yes | Your Docflow secret code |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docflow_get_or_create_workspaceA | Find a workspace by name, or create one if it does not exist. Returns: workspace_id (str): ID of the workspace. created (bool): True if a new workspace was created. Use this as Step 1 of every workflow to ensure a workspace is ready. |
| docflow_list_categoriesA | List all enabled categories in a workspace, including their field configurations. Returns a list of category objects with name, category_id, and fields. Use this to check which categories are already configured before creating new ones. |
| docflow_create_categoryB | Create a file category with field configuration and a sample file. |
| docflow_upload_and_extractA | Upload files and wait for classification and extraction to complete. Provide either file_paths (explicit list) or directory (auto-scans supported files). Supported formats: PDF, JPG, PNG, DOC, DOCX, XLS, XLSX, OFD, TXT. |
| docflow_setup_review_rulesB | Create a review rule repository (idempotent — reuses existing repo if name matches). |
| docflow_run_reviewA | Submit a review task and wait for results. |
| docflow_fetch_filesA | Query processed files in a workspace (GET /file/fetch). Useful for checking status of previously uploaded files or retrieving results later. recognition_status: "0"=pending, "1"=success, "2"=failed, "3"=processing. |
| docflow_update_fileB | Update metadata or verification status of a processed file (POST /file/update). |
| docflow_delete_filesA | Delete processed files from a workspace (POST /file/delete). Provide either task_ids or batch_numbers. Deletion is permanent. |
| docflow_extract_fieldsA | Re-extract specific fields from an already-processed file (POST /file/extract_fields). Use when you need to extract additional fields without re-uploading the file, or when the original extraction missed certain fields. |
| docflow_retry_filesA | Retry processing for files that failed (POST /file/retry). Use when recognition_status=2 (failed). |
| docflow_amend_categoryA | Correct a misclassified file's category and trigger re-extraction (POST /file/amend_category). Use when a file was classified into the wrong category. The file will be re-processed using the correct category's field configuration. |
| docflow_list_workspacesA | List all workspaces accessible to the current account (GET /workspace/list). Returns workspace_id, name, description, and auth_scope for each. |
| docflow_get_workspaceB | Get detailed information about a specific workspace (GET /workspace/get). Returns workspace metadata including name, description, auth_scope, and statistics. |
| docflow_update_workspaceB | Update workspace settings (POST /workspace/update). |
| docflow_delete_workspaceA | Delete a workspace and all its contents (POST /workspace/delete). WARNING: This permanently deletes all files, categories, and review rules in the workspace. |
| docflow_update_categoryC | Update an existing file category's settings (POST /category/update). |
| docflow_delete_categoryA | Delete a file category and its field configuration (POST /category/delete). WARNING: Existing files classified under this category retain their extracted data, but future uploads will not match this category. |
| docflow_list_category_tablesA | List all table configurations in a category (GET /category/tables/list). Returns table_id, name, and fields for each table. Use this to get table_id before adding table fields or building review rules. |
| docflow_add_category_tableA | Add a table field group to a category (POST /category/tables/add). Use for extracting structured table data (e.g. invoice line items, hotel charges). |
| docflow_update_category_tableC | Update a table configuration in a category (POST /category/tables/update). |
| docflow_delete_category_tablesC | Delete table configurations from a category (POST /category/tables/delete). |
| docflow_list_category_fieldsA | List all fields configured in a category (GET /category/fields/list). Returns field_id, name, description, and configuration for each field. Use this to get field_ids needed when building review rules with referenced_fields. |
| docflow_add_category_fieldsC | Add fields to an existing category (POST /category/fields/add). |
| docflow_update_category_fieldA | Update a field's name, description, or extraction prompt (POST /category/fields/update). Updating the prompt can improve extraction accuracy for specific field types. |
| docflow_delete_category_fieldsB | Delete fields from a category (POST /category/fields/delete). |
| docflow_add_category_samplesA | Add sample files to a category to improve classification accuracy (POST /category/sample/upload). More samples (3–5 recommended, max 10 total) improve classification reliability. |
| docflow_list_category_samplesA | List all sample files configured for a category (GET /category/sample/list). Returns sample_id, file name, and upload time for each sample. |
| docflow_delete_category_samplesA | Delete sample files from a category (POST /category/sample/delete). Use to remove low-quality or irrelevant samples that hurt classification accuracy. |
| docflow_list_review_reposA | List all review rule repositories in a workspace (GET /review/rule_repo/list). Returns repo_id, name, and creation time for each. |
| docflow_get_review_repoA | Get a review rule repository with all its groups and rules (GET /review/rule_repo/get). Use this to inspect existing rule configurations before making changes. |
| docflow_update_review_repoC | Rename a review rule repository (POST /review/rule_repo/update). |
| docflow_delete_review_repoA | Delete a review rule repository and all its groups and rules (POST /review/rule_repo/delete). WARNING: This is permanent. Existing review task results are not affected. |
| docflow_update_review_rule_groupB | Rename a review rule group (POST /review/rule_group/update). |
| docflow_delete_review_rule_groupA | Delete a review rule group and all rules within it (POST /review/rule_group/delete). |
| docflow_update_review_ruleB | Update an existing review rule's prompt or configuration (POST /review/rule/update). Use to refine rule prompts based on review results, or adjust risk levels. risk_level: 10=high, 20=medium, 30=low. |
| docflow_delete_review_ruleC | Delete a review rule (POST /review/rule/delete). |
| docflow_get_review_resultA | Get the current result of a review task without waiting (POST /review/task/result). Use to check status of a previously submitted review, or for manual polling. status: 0=pending, 1=pass, 2=failed, 3=reviewing, 4=not_pass, 7=recognition_failed. |
| docflow_delete_review_taskC | Delete review tasks (POST /review/task/delete). |
| docflow_retry_review_taskA | Retry an entire review task that failed or produced unexpected results (POST /review/task/retry). All rules in the task will be re-evaluated. |
| docflow_retry_review_ruleA | Retry evaluation of a single rule within a review task (POST /review/task/rule/retry). Use when one specific rule failed or needs re-evaluation after updating its prompt, without re-running all other rules in the task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
Each tool targets a distinct resource/action such as workspace, category, field, table, sample, review repo/rule/task, or file, so descriptions mostly prevent ambiguity. Some close pairs like retry_review_rule vs retry_review_task or update_category vs update_category_field require careful reading, but the boundaries are clear enough.
All tools share the docflow_ snake_case prefix and generally follow a verb-first naming pattern, making the set predictable. Minor inconsistencies like delete_category_tables vs add_category_table, or the less explicit upload_and_extract, prevent a perfect score.
41 tools is well above the 25+ threshold and feels too heavy for an agent to efficiently select from, even though the domain is broad. Many tools are narrow API endpoints for closely related subresources that could potentially be consolidated.
File and category coverage is fairly complete with create/read/update/delete operations, but review-rule management has a notable gap: there is no explicit way to add a new rule or rule group to an existing repository, only update/delete and whole-repo setup. There is also no list-review-tasks operation, which creates partial dead ends in review workflows.