com.mcparmory/ragie
PYPI · MCPARMORY-RAGIE · 2 COMPONENTS · SCANNED SEP 16
Ingest, manage, and retrieve documents for RAG-powered AI applications
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 126 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8341 tokens (~160/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/ragie MCP server?
com.mcparmory/ragie runs locally as a PyPI package, launched with uvx mcparmory-ragie. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-ragie
claude mcp add com-mcparmory-ragie -- uvx mcparmory-ragie
{
"mcpServers": {
"com-mcparmory-ragie": {
"command": "uvx",
"args": [
"mcparmory-ragie"
]
}
}
} {
"servers": {
"com-mcparmory-ragie": {
"command": "uvx",
"args": [
"mcparmory-ragie"
]
}
}
} codex mcp add com-mcparmory-ragie -- uvx mcparmory-ragie
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-ragie": {
"type": "local",
"command": [
"uvx",
"mcparmory-ragie"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-ragie --command uvx --arg mcparmory-ragie
mcp_servers:
com-mcparmory-ragie:
command: "uvx"
args: ["mcparmory-ragie"] {
"McpServers": {
"com-mcparmory-ragie": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-ragie"
]
}
}
} assistant mcp add com-mcparmory-ragie -t stdio -c uvx -a mcparmory-ragie
{
"mcpServers": {
"com-mcparmory-ragie": {
"command": "uvx",
"args": [
"mcparmory-ragie"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 2.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Sept 2026 · Analysed pypi/mcparmory-ragie@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_authenticator Create Authenticator ~220
Create white-labeled connector credentials for integrating with third-party services. This establishes authentication configuration that enables secure API access to supported providers.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | The OAuth 2.0 client ID issued by the provider's application registration or developer console. |
| client_secret | string | yes | The OAuth 2.0 client secret issued by the provider's application registration or developer console. Keep this value secure. |
| domain | string | – | The domain or workspace identifier for the provider, if applicable. Required for certain providers that use domain-based authentication. |
| name | string | yes | A unique identifier for this authenticator configuration. This name is used to reference and distinguish the authenticator from others. Names must be globally unique within your account. |
| project_number | string | – | The project number identifier for the provider, if applicable. Required for certain providers that use project-based authentication. |
| provider | string | yes | The provider service to authenticate with. Must be one of: Atlassian, Dropbox, HubSpot, Microsoft, Salesforce, or Slack. |
No output schema declared.
No examples provided.
create_authenticator_connection Create Authenticator Connection ~336
Establish a connector for a specified authenticator with provider-specific credentials (e.g., Google Drive refresh token). Configure document processing options like OCR mode, media handling, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | boolean | – | Enable audio extraction and processing from documents. |
| authenticator_id | string | yes | The unique identifier (UUID) of the authenticator to create a connection for. |
| config | object | – | Provider-specific configuration object. Structure depends on the authenticator type. |
| connection | – | yes | Connection credentials object. Structure and required fields depend on the authenticator provider type. |
| metadata | object | – | Custom metadata key-value pairs for document classification and filtering. Keys must be strings; values can be strings, numbers, booleans, or lists of strings. Up to 1000 total values allowed (each a… |
| page_limit | integer | – | Maximum number of pages to process from the source. Omit or set to null for no limit. |
| static | string | – | OCR processing mode for static documents: 'hi_res' for high-resolution processing, 'fast' for quick processing, or 'agentic_ocr' for intelligent OCR. |
| video | string | – | Video processing mode: 'audio_only' to extract audio, 'video_only' to process video frames, or 'audio_video' to process both. |
| workflow | string | – | Processing workflow: 'parse' to extract and structure content, or 'index' to prepare for search and retrieval. |
No output schema declared.
No examples provided.
create_connection Create Connection ~331
Create a new connection for non-OAuth data sources such as S3-compatible storage, Freshdesk, or Zendesk. Configure the connection with source-specific settings and optional processing parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | boolean | – | Enable audio processing for documents that contain audio content. |
| config | object | – | Source-specific configuration object containing connection details and credentials required by the data source type. |
| connection | – | yes | Connection configuration object specifying the data source type and authentication details. |
| metadata | object | – | Custom metadata to attach to documents processed through this connection. Keys must be strings; values can be strings, numbers, booleans, or lists of strings. Up to 1000 total values allowed (each ar… |
| page_limit | integer | – | Maximum number of pages to process from each document. Omit or set to null for no limit. |
| static | string | – | Processing mode for document extraction: 'hi_res' for high-resolution processing, 'fast' for quick processing, or 'agentic_ocr' for advanced OCR-based extraction. |
| video | string | – | Video processing mode: 'audio_only' to extract audio tracks, 'video_only' to process video frames, or 'audio_video' to process both. |
| workflow | string | – | Processing workflow: 'parse' to extract and structure document content, or 'index' to prepare documents for search and retrieval. |
No output schema declared.
No examples provided.
create_document Create Document ~392
Upload and ingest a document for processing and retrieval. The document progresses through multiple processing stages (pending → partitioning → indexed → ready) and becomes available for retrieval once it reaches the ready state.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | Optional external identifier for the document, such as an ID from an external system or the source URL where the file originates. |
| file | string | yes | Base64-encoded file content for upload. The binary file to upload and index. Supported formats include plain text (.txt, .md, .json, .html, .xml, .eml, .msg, .rst, .rtf), images (.png, .jpg, .jpeg, .… |
| metadata | object | – | Custom metadata key-value pairs to attach to the document. Keys must be strings; values can be strings, numbers (integers or floats), booleans, or lists of strings. Up to 1000 total values are allowe… |
| mode | object | – | Processing mode configuration for document ingestion. Accepts either an object with detailed mode settings or a scalar shorthand value. |
| name | string | – | Optional display name for the document. If provided, this name will be used; otherwise, the uploaded file's name will be used as the document name. |
| workflow | string | – | Processing workflow to apply to the document. Choose 'parse' for document parsing or 'index' for indexing operations. |
No output schema declared.
No examples provided.
create_document_from_text Create Document from Text ~237
Ingest a document as raw text for processing through an automated pipeline. The document progresses through multiple stages (pending → partitioning → indexed → ready) and becomes available for retrieval once it reaches the ready state.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The document content as raw text or JSON. Must contain at least 1 character. |
| external_id | string | – | Optional external identifier for cross-referencing with other systems, such as a database ID or source URL. |
| metadata | object | – | Optional key-value metadata to attach to the document. Keys must be strings; values can be strings, numbers, booleans, or lists of strings. Up to 1000 total values are allowed (each array item counts… |
| name | string | – | Optional human-readable name for the document. If not provided, defaults to the current timestamp. |
| workflow | string | – | Optional processing stage to stop at. Use 'parse' to extract elements only, or 'index' (or omit) to run the full processing pipeline including chunking and indexing. |
No output schema declared.
No examples provided.
create_instruction Create Instruction ~362
Create a new instruction that automatically extracts structured data from documents as they are created or updated. Instructions apply natural language prompts to documents and store results according to a defined JSON schema.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether this instruction is immediately active and applied to new and updated documents. Defaults to true. |
| context_template | string | – | An optional Mustache template that prepends document context (name, type, source, metadata) to the content before extraction. Use variables like {{document.name}} and {{document.metadata.key_name}} t… |
| entity_schema | object | yes | A JSON schema defining the structure of extracted entities. Must be an object type at the root. For multiple items, use an array property (e.g., 'emails' as an array of strings). For single values, w… |
| filter | object | – | An optional metadata filter that restricts instruction application to matching documents. Supports operators like $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, and can combine conditions with AND/OR log… |
| name | string | yes | A unique name for the instruction that identifies its purpose (e.g., 'Find all pizzas'). Must not duplicate existing instruction names. |
| prompt | string | yes | A natural language instruction describing what data to extract from documents. This prompt is applied to document content and results are stored as entities matching the entity_schema. |
| scope | string | – | Determines the granularity of analysis: 'document' analyzes the entire document (useful for summaries or sentiment), while 'chunk' analyzes individual document sections (useful for fine-grained searc… |
No output schema declared.
No examples provided.
create_oauth_redirect_url Create OAuth Redirect URL ~410
Generates an OAuth redirect URL for initializing an embedded connector, allowing users to authenticate with third-party services like Google Drive, Notion, Salesforce, and others.
| Name | Type | Req | Description |
|---|---|---|---|
| authenticator_id | string | – | UUID of the authenticator to use for this OAuth flow. Links the redirect URL to a specific authentication context. |
| config | object | – | Connector-specific configuration options provided as a JSON object. Structure varies by connector type. |
| metadata | object | – | Custom key-value metadata to attach to synced documents. Keys must be strings; values can be strings, numbers, booleans, or lists of strings. Up to 1000 total values allowed (each array item counts s… |
| mode | – | – | Operational mode for the connector (specific behavior determined by connector type). |
| page_limit | integer | – | Maximum number of pages the connection will sync before being automatically disabled. Must be at least 1 if specified. Set to null to remove any limit. In-progress documents may continue processing a… |
| redirect_uri | string | yes | The URI where the user will be redirected after completing OAuth authentication. This must be a valid, accessible endpoint in your application. |
| source_type | string | – | The connector type to initialize (e.g., google_drive, notion, hubspot). Defaults to google_drive if not specified. Choose from supported connectors like cloud storage (S3, GCS, Dropbox), productivity… |
| theme | string | – | Visual theme for the Ragie Web UI presented to the user. Choose 'light' for light mode, 'dark' for dark mode, or 'system' to match the user's system preference. Defaults to system. |
| workflow | string | – | The workflow type for processing synced content. Choose 'parse' to extract and structure document content, or 'index' to prepare content for search and retrieval. |
No output schema declared.
No examples provided.
create_partition Create Partition ~302
Create a new partition to scope documents, connections, and instructions. Partition names must be lowercase alphanumeric with only underscores and hyphens allowed. Optional resource limits can be defined at creation time.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_processed_limit_max | integer | – | Maximum duration in minutes for audio processing in this partition. Must be at least 1. |
| description | string | – | Human-readable description of the partition's purpose. Automatic description generation can be enabled in the web dashboard. |
| media_hosted_limit_max | integer | – | Maximum size in megabytes for media hosted in this partition. Must be at least 1. |
| media_streamed_limit_max | integer | – | Maximum size in megabytes for media streamed from this partition. Must be at least 1. |
| metadata_schema | object | – | JSON Schema defining optional metadata fields for documents in this partition. Include detailed field descriptions to assist LLMs in generating dynamic filters. |
| name | string | yes | Unique identifier for the partition. Must be lowercase alphanumeric and may only contain underscores and hyphens. |
| pages_hosted_limit_max | integer | – | Maximum number of pages allowed for hosted documents in this partition. Must be at least 1. |
| pages_processed_limit_max | integer | – | Maximum number of pages allowed for processed documents in this partition. Must be at least 1. |
| video_processed_limit_max | integer | – | Maximum duration in minutes for video processing in this partition. Must be at least 1. |
No output schema declared.
No examples provided.
create_response Create Response ~254
Generate an LLM-powered response to a query using the deep-search model. Responses can be streamed in real-time or returned synchronously, with optional access to document retrieval tools across specified partitions.
| Name | Type | Req | Description |
|---|---|---|---|
| effort | string | yes | The computational effort level for generating the response. Choose low for quick responses, medium for balanced quality and speed, or high for more thorough analysis. |
| input | string | yes | The query or question to generate a response for. This text is processed by the LLM agent to produce relevant answers. |
| instructions | string | – | Custom instructions to inject into the agent's prompt, particularly during search and retrieval steps. Use this to guide the agent's behavior and response style. |
| model | string | – | The LLM model powering the agent. Currently only deep-search is supported. |
| stream | boolean | – | Whether to stream the response as it's generated (true) or wait for the complete response (false). Streaming allows real-time consumption of results. |
| tools | array | – | Array of tools available to the agent for generating responses. Currently supports the retrieve tool for document search. Each tool can specify which partitions to search; if omitted, the default par… |
No output schema declared.
No examples provided.
delete_authenticator Delete Authenticator ~53
Delete an authenticator connection method. All connections created by this authenticator must be deleted before this operation can succeed.
| Name | Type | Req | Description |
|---|---|---|---|
| authenticator_id | string | yes | The unique identifier (UUID) of the authenticator to delete. |
No output schema declared.
No examples provided.
delete_connection Delete Connection ~109
Schedules a connection for deletion. Optionally preserve associated files (they will be disassociated from the connection) or delete them along with the connection. Deletion is asynchronous and files may remain visible briefly after the request completes.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier (UUID) of the connection to delete. |
| keep_files | boolean | yes | Whether to retain files associated with this connection. If true, files are preserved but disassociated; if false, all files are deleted with the connection. |
No output schema declared.
No examples provided.
delete_document Delete Document ~76
Permanently delete a document by its unique identifier. Supports both synchronous and asynchronous deletion modes.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | When true, the deletion is performed asynchronously and returns immediately without waiting for completion. Defaults to false for synchronous deletion. |
| document_id | string | yes | The unique identifier of the document to delete, formatted as a UUID. |
No output schema declared.
No examples provided.
delete_instruction Delete Instruction ~46
Permanently delete an instruction and all entities it generated. This operation cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction_id | string | yes | The unique identifier of the instruction to delete, formatted as a UUID. |
No output schema declared.
No examples provided.
delete_partition Delete Partition ~89
Permanently deletes a partition and all associated data, including connections, documents, and partition-specific instructions. This operation cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | When set to true, the partition deletion is performed asynchronously, allowing the request to return immediately while the deletion completes in the background. Defaults to false for synchronous dele… |
| partition_id | string | yes | The unique identifier of the partition to delete. |
No output schema declared.
No examples provided.
get_connection Get Connection ~46
Retrieve a specific connection by its unique identifier. Returns the full connection details including configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier (UUID) of the connection to retrieve. |
No output schema declared.
No examples provided.
get_connection_stats Get Connection Stats ~50
Retrieves aggregated statistics for a specific connection, including total documents, active documents, and total active pages.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier (UUID) of the connection to retrieve statistics for. |
No output schema declared.
No examples provided.
get_document Get Document ~53
Retrieve a specific document by its unique identifier. Returns the full document details including metadata and content.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document to retrieve, formatted as a UUID (universally unique identifier). |
No output schema declared.
No examples provided.
get_document_chunk Get Document Chunk ~81
Retrieves a specific chunk from a document using both the document ID and chunk ID. Use this to fetch individual content segments within a larger document.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_id | string | yes | The unique identifier of the specific chunk to retrieve, formatted as a UUID. |
| document_id | string | yes | The unique identifier of the document containing the chunk, formatted as a UUID. |
No output schema declared.
No examples provided.
get_document_chunk_content Get Document Chunk Content ~165
Retrieves the content of a specific document chunk in the requested format. Supports streaming media content for audio and video documents, with optional file download capability.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_id | string | yes | The unique identifier (UUID) of the specific chunk within the document. |
| document_id | string | yes | The unique identifier (UUID) of the document containing the chunk. |
| download | boolean | – | Whether to return the content as a downloadable file attachment or as a raw stream. Defaults to false (raw stream). |
| media_type | string | – | The desired format for the returned content as a MIME type (e.g., text/plain, audio/mpeg, video/mp4, or various image formats). The requested format must be supported by the document type, or an erro… |
No output schema declared.
No examples provided.
get_document_content Get Document Content ~163
Retrieve the content of a document in your preferred format. Supports multiple media types including JSON (with metadata), plain text, and streaming formats for audio/video content. Non-textual media like images are returned as text descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document to retrieve, formatted as a UUID. |
| download | boolean | – | When true, the content is returned as a downloadable file with its original filename. When false (default), the content is returned as a raw stream. |
| media_type | string | – | The desired format for the returned content, specified as a MIME type (e.g., application/json, text/plain, audio/mpeg, video/mp4). If the document doesn't support the requested type, an error will be… |
No output schema declared.
No examples provided.
get_document_source Get Document Source ~86
Retrieve the original source file of a document. The source varies by origin: uploaded files are returned as-is, URL-sourced documents return the fetched content, and connection-synced documents return the format specific to that connection type (e.g., file from Google Drive, JSON from Salesforce).
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document, formatted as a UUID. |
No output schema declared.
No examples provided.
get_document_summary Get Document Summary ~86
Retrieve an LLM-generated summary of a document. The summary is automatically created when the document is first uploaded or updated. Note: This feature is in beta and may change; data files (xls, xlsx, csv, json) and documents exceeding 1M tokens are not supported.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document, formatted as a UUID. |
No output schema declared.
No examples provided.
get_element Get Element ~50
Retrieves a specific element from a document by its unique identifier. Use this to fetch detailed information about an individual element.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | string | yes | The unique identifier (UUID) of the element to retrieve. |
No output schema declared.
No examples provided.
get_partition Get Partition ~46
Retrieve detailed information about a specific partition, including its usage metrics (document and page counts) and configured limits.
| Name | Type | Req | Description |
|---|---|---|---|
| partition_id | string | yes | The unique identifier of the partition to retrieve. |
No output schema declared.
No examples provided.
get_response Get Response ~71
Retrieve a response by its unique identifier. Returns the response data along with its current status: `in_progress` for ongoing processing, `completed` for finished responses, or `failed` for responses that encountered an error.
| Name | Type | Req | Description |
|---|---|---|---|
| response_id | string | yes | The unique identifier (UUID) of the response to retrieve. |
No output schema declared.
No examples provided.
get_webhook_endpoint Get Webhook Endpoint ~53
Retrieve a specific webhook endpoint by its unique identifier. Use this to fetch configuration and status details for a registered webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | The unique identifier (UUID) of the webhook endpoint to retrieve. |
No output schema declared.
No examples provided.
ingest_document_from_url Ingest Document from URL ~384
Ingest a document from a publicly accessible URL for processing and retrieval. The document progresses through multiple processing stages (pending → partitioning → indexed → ready) before becoming available for retrieval, with optional extraction of images, tables, and media content based on the selected partition strategy.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | Optional external identifier for the document, such as an ID from an external system or the source URL where the file originates. |
| metadata | object | – | Optional key-value metadata to attach to the document. Keys must be strings; values can be strings, numbers, booleans, or lists of strings. Up to 1000 total values are allowed (each array item counts… |
| mode | – | – | Partition strategy controlling how the document is processed. For text documents, use `'hi_res'` to extract images and tables (slower, ~20x), or `'fast'` for text only. For audio/video, specify proce… |
| name | string | – | Optional human-readable name for the document. If not provided, a default name will be assigned. |
| url | string | yes | URL of the file to ingest. Must be publicly accessible via HTTP or HTTPS, between 1 and 2083 characters in length, and a valid URI format. |
| workflow | string | – | Optional processing stage to stop at. Set to `'parse'` to extract elements only, or `'index'` (default) to complete the full processing pipeline including indexing and summarization. |
No output schema declared.
No examples provided.
list_authenticators List Authenticators ~75
Retrieve a paginated list of all authenticators sorted by creation date in descending order. Use the cursor parameter to navigate through pages when more results are available.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Number of authenticators to return per page. Must be between 1 and 100 items; defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_connection_source_types List Connection Source Types ~39
Retrieve all available connection source types (such as Google Drive, Notion, etc.) along with their metadata to understand what integrations can be configured.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connections List Connections ~141
Retrieve all connections sorted by creation date in descending order. Results are paginated with a maximum of 100 items per page; use the cursor parameter to fetch subsequent pages when available.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter connections by metadata using comparison operators ($eq, $ne, $gt, $gte, $lt, $lte, $in, $nin) combined with AND/OR logic. Returns only connections matching the filter criteria. Refer to the M… |
| page_size | integer | – | Number of connections to return per page. Must be between 1 and 100 items; defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_document_chunks List Document Chunks ~225
Retrieve all chunks from a document, sorted by index in ascending order. Results are paginated with a maximum of 100 chunks per page; use the cursor parameter to fetch subsequent pages. Documents created before September 18, 2024 that haven't been updated may have chunks with index -1, sorted by ID instead.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier (UUID) of the document to retrieve chunks from. |
| end_index | integer | – | The inclusive ending index for filtering chunks by range. If specified alone, returns only the chunk at this index. If both start_index and end_index are omitted, all chunks are returned without inde… |
| page_size | integer | – | Number of chunks to return per page, between 1 and 100 (defaults to 10). Use this with the cursor parameter to control pagination. |
| start_index | integer | – | The inclusive starting index for filtering chunks by range. If specified alone, returns only the chunk at this index. If both start_index and end_index are omitted, all chunks are returned without in… |
No output schema declared.
No examples provided.
list_document_elements List Document Elements ~166
Retrieve paginated elements from a document, sorted by index in ascending order. Results are limited to 100 items per page, with cursor-based pagination for accessing subsequent pages.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier (UUID) of the document containing the elements to retrieve. |
| index_end | integer | – | Filter results to include only elements at or before this index position (inclusive). |
| index_start | integer | – | Filter results to include only elements at or after this index position (inclusive). |
| page_size | integer | – | Number of elements to return per page. Must be between 1 and 100 items (defaults to 10 if not specified). |
| type | array | – | Filter results by element type(s). Accepts an array of type values to match against. |
No output schema declared.
No examples provided.
list_documents List Documents ~159
Retrieve a paginated list of all documents sorted by creation date (newest first). Use the page_size parameter to control results per page and the filter parameter to search by metadata. When more results are available, a cursor will be provided for fetching the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Metadata filter expression to narrow results. Supports operators like $eq (equal), $ne (not equal), $gt/$gte (greater than), $lt/$lte (less than), $in/$nin (array membership), and logical AND/OR comb… |
| page_size | integer | – | Number of documents to return per page. Must be between 1 and 100 items. Defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_entities_by_document List Entities by Document ~85
Retrieve all entities extracted from a specific document. Returns a paginated list of entities identified during document processing.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier (UUID) of the document from which to retrieve extracted entities. |
| page_size | integer | – | Number of entities to return per page, between 1 and 100 items. Defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_entities_by_instruction List Entities by Instruction ~90
Retrieve all entities that were extracted from a specific instruction. Results are paginated to allow efficient browsing of large entity sets.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction_id | string | yes | The unique identifier (UUID) of the instruction whose extracted entities you want to retrieve. |
| page_size | integer | – | The number of entities to return per page, between 1 and 100 items. Defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_instruction_entity_extraction_logs List Instruction Entity Extraction Logs ~234
Retrieve entity extraction logs for a specific instruction, showing attempt-level results with both successful and unsuccessful outcomes. Results are sorted by creation date in descending order and paginated, with historical data available only from March 6, 2026 onwards.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Optional ISO 8601 timestamp to include only logs created on or after this date and time. |
| created_before | string | – | Optional ISO 8601 timestamp to include only logs created before this date and time. |
| document_ids | array | – | Optional list of document IDs to filter extraction logs. Only logs matching these document IDs will be included in results. |
| instruction_id | string | yes | The UUID of the instruction for which to retrieve entity extraction logs. |
| page_size | integer | – | Number of results to return per page. Must be between 1 and 100 items. Defaults to 10 if not specified. |
| status | string | – | Optional filter by extraction outcome status. Valid values are `extracted` (successful extraction), `not_found` (entity not found), or `error` (extraction failed). |
No output schema declared.
No examples provided.
list_instructions List Instructions ~30
Retrieve all instructions available in the system. Use this operation to discover and review the complete set of instructions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_partitions List Partitions ~77
Retrieve all partitions sorted alphabetically in ascending order. Results are paginated with a maximum of 100 items per page; use the cursor parameter to fetch subsequent pages when available.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Number of partitions to return per page. Must be between 1 and 100 items; defaults to 10 if not specified. |
No output schema declared.
No examples provided.
list_webhook_endpoints List Webhook Endpoints ~82
Retrieve all webhook endpoints sorted by creation date in descending order. Results are paginated with a maximum of 100 items per page, and a cursor is provided when additional endpoints are available.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Number of webhook endpoints to return per page. Must be between 1 and 100 items. Defaults to 10 if not specified. |
No output schema declared.
No examples provided.
search_document_chunks Search Document Chunks ~237
Search and retrieve relevant document chunks based on a semantic query, with optional filtering, reranking, and recency bias to support accurate LLM-based generation and reduce hallucinations.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Metadata filter to narrow results to documents matching specific criteria. Supports equality, inequality, comparison, and array membership operators that can be combined with AND/OR logic. |
| max_chunks_per_document | integer | – | Limit the number of chunks retrieved from any single document. Use this to diversify results across multiple documents rather than concentrating chunks from one source. |
| query | string | yes | The search query used to find semantically relevant document chunks. Can be a natural language question or statement. |
| recency_bias | boolean | – | Prioritize more recent documents over older ones in the ranking. Useful when document freshness is important for accuracy. |
| rerank | boolean | – | Enable semantic reranking of results for higher relevancy, improving accuracy and reducing hallucinations. Processing will be slower but returns a more focused set of highly relevant chunks. |
| top_k | integer | – | Maximum number of chunks to return in the results. Defaults to 8 chunks. |
No output schema declared.
No examples provided.
trigger_connection_sync Trigger Connection Sync ~51
Immediately schedules a connector to begin syncing data. This operation queues the sync to run as soon as possible.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier of the connection to sync, formatted as a UUID. |
No output schema declared.
No examples provided.
update_connection Update Connection ~199
Update a connection's metadata or partition strategy. Changes take effect after the next sync operation.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier (UUID) of the connection to update. |
| metadata | object | – | Custom metadata as key-value pairs where keys are strings and values are strings, numbers, booleans, or lists of strings. Up to 1000 total values allowed (each array item counts separately). Reserved… |
| page_limit | integer | – | Maximum number of pages to sync for this connection; the connection will be disabled once this limit is reached. Set to `null` to remove any existing limit. Must be at least 1 if specified. |
| partition_strategy | – | yes | The strategy for partitioning data during sync operations. |
No output schema declared.
No examples provided.
update_connection_enabled_status Update Connection Enabled Status ~117
Enable or disable a connection to control whether it syncs data. Disabled connections will not perform synchronization operations.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier (UUID format) of the connection to modify. |
| enabled | boolean | yes | Boolean flag to enable (true) or disable (false) the connection. |
| reason | string | – | Optional reason for disabling the connection. Valid values indicate specific failure conditions: 'connection_over_total_page_limit' when the connection exceeds page limits, or 'authentication_failed'… |
No output schema declared.
No examples provided.
update_connection_page_limit Update Connection Page Limit ~103
Set or remove page synchronization limits for a connection. When a limit is set, the connection automatically disables after syncing the specified number of pages, though some in-process documents may continue processing.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | The unique identifier of the connection to configure limits for. |
| page_limit | integer | – | The maximum number of pages this connection will synchronize before being disabled. Must be at least 1 if specified. Set to null to remove any existing limit. |
No output schema declared.
No examples provided.
update_document_file Update Document File ~277
Replace the file content of an existing document. The uploaded file will be extracted, processed, and indexed for retrieval. Supports text formats (plain text, markdown, email, HTML, XML, JSON, RST, RTF), images (PNG, WebP, JPEG, TIFF, BMP, HEIC), and documents (PDF, Word, Excel, PowerPoint, CSV, EPUB, ODT).
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document to update, formatted as a UUID. |
| file | string | yes | Base64-encoded file content for upload. The binary file to upload and process. Supported formats include text files (.txt, .md, .json, .html, .xml, .eml, .msg, .rst, .rtf), images (.png, .jpg, .jpeg,… |
| mode | object | – | Optional processing mode configuration that controls how the file is extracted and indexed. Accepts either an object with detailed settings or a scalar shorthand value. |
No output schema declared.
No examples provided.
update_document_from_url Update Document from URL ~224
Update a document by ingesting content from a publicly accessible URL. The document progresses through multiple processing states (pending → indexed → ready) before becoming available for retrieval, with optional high-resolution processing for extracting images and tables.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The unique identifier of the document to update, formatted as a UUID. |
| mode | – | – | Processing strategy for document ingestion. For text documents, use 'hi_res' to extract images and tables (slower, ~20x) or 'fast' for text-only extraction. For audio, use true/false to enable proces… |
| url | string | yes | Public HTTP or HTTPS URL of the file to ingest. Must be publicly accessible and between 1 and 2083 characters in length. |
No output schema declared.
No examples provided.
update_document_metadata Update Document Metadata ~185
Partially update a document's metadata with new or modified key-value pairs. Reserved keys (document_id, document_type, document_source, document_name, document_uploaded_at) cannot be modified. For connection-managed documents, updates create a metadata overlay applied on each sync.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | If true, the update runs asynchronously in the background and returns a 202 response; if false (default), it runs synchronously and returns a 200 response. |
| document_id | string | yes | The UUID identifier of the document to update. |
| metadata | object | yes | A partial metadata object with string keys and values that are strings, numbers, booleans, or lists of strings. Set a key to null to delete it. Up to 1000 total values are allowed across all metadata… |
No output schema declared.
No examples provided.
update_document_raw Update Document Raw ~74
Replace the raw content of an existing document with new text or JSON data. This operation overwrites the entire document content.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The new document content as text or JSON. Must contain at least one character. |
| document_id | string | yes | The unique identifier of the document to update, formatted as a UUID. |
No output schema declared.
No examples provided.
update_instruction Update Instruction ~369
Update an instruction's configuration, including its name, active status, scope, prompt, context template, entity schema, and metadata filters. Changes apply to documents created or updated after the patch is applied.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the instruction is active. Active instructions are automatically applied when documents are created or their files are updated. |
| context_template | string | – | An optional Mustache template that prepends document context to the content sent for extraction. Supports variables like document.name, document.type, document.source, and nested metadata values (e.g… |
| entity_schema | object | – | A JSON schema (object type at root) that defines the structure of entities extracted by this instruction. For multiple items, use an array property. For single values, wrap in an object with a single… |
| filter | object | – | An optional metadata filter that restricts instruction application to documents matching the filter criteria. Supports operators: $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, and can be combined with A… |
| instruction_id | string | yes | The unique identifier (UUID) of the instruction to update. |
| name | string | – | A unique name for the instruction. Must not conflict with existing instruction names. |
| prompt | string | – | A natural language instruction that defines what entities or information to extract from documents. Results are stored as entities matching the schema defined in entity_schema. |
| scope | string | – | The scope determines how the instruction is applied: 'document' analyzes the entire document (ideal for summaries or sentiment analysis), while 'chunk' analyzes individual document chunks (ideal for… |
No output schema declared.
No examples provided.
update_partition Update Partition ~147
Update a partition's configuration, including its description and metadata schema. The metadata schema defines an optional subset of document metadata as JSON Schema, useful for LLM-based filter generation.
| Name | Type | Req | Description |
|---|---|---|---|
| context_aware | boolean | – | Enable context-aware descriptions that provide additional semantic context for the partition to improve LLM understanding and filter generation. |
| description | string | – | A human-readable description of the partition's purpose and contents. |
| metadata_schema | object | – | A JSON Schema definition describing the structure and types of metadata fields available in documents within this partition. Include detailed field descriptions to assist LLMs in generating accurate… |
| partition_id | string | yes | The unique identifier of the partition to update. |
No output schema declared.
No examples provided.
What is the com.mcparmory/ragie MCP server?
com.mcparmory/ragie is an MCP server listed in the public MCP registry as com.mcparmory/ragie. Ingest, manage, and retrieve documents for RAG-powered AI applications. This page covers its PyPI package (mcparmory-ragie).
Is the com.mcparmory/ragie MCP server safe to use?
com.mcparmory/ragie scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/ragie MCP server expose?
com.mcparmory/ragie exposes 52 tools: list_documents, create_document, create_document_from_text, ingest_document_from_url, get_document, and 47 more. Their descriptions and schemas cost roughly 8,341 tokens of context every time the server is loaded.
Is the com.mcparmory/ragie MCP server still maintained?
com.mcparmory/ragie is still listed as active in the MCP registry. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.