sifter-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIFTER_API_KEY | Yes | The API key for Sifter |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_siftsA | List sifts with their name, instructions, and document/record counts. |
| get_siftC | Get sift metadata and inferred extraction schema for a specific sift. |
| list_recordsB | Get extracted records from a sift. |
| query_siftA | Run a natural language query over a sift's extracted records. |
| list_foldersB | List folders with their name and document count. |
| get_folderA | Get folder metadata, linked sifts, and document list for a specific folder. |
| get_record_citationsB | Get per-field citation map for a record (page, bbox, source text for each field). |
| create_siftA | Create a new sift with the given extraction instructions. |
| update_siftB | Update an existing sift's name or instructions. |
| delete_siftA | Delete a sift and all its records. |
| upload_documentA | Upload a document to a folder. The folder is created if it doesn't exist. The document will be processed by all sifts linked to the folder. |
| run_extractionC | Enqueue extraction for a document on a specific sift. |
| get_extraction_statusA | Check extraction status for a document on a sift. |
| find_recordsA | Filter records with structured criteria (no LLM roundtrip). |
| aggregate_siftA | Run a MongoDB aggregation pipeline against a sift's records. |
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 15 tools
Each tool has a clearly distinct purpose: sift CRUD, document upload, folder management, record retrieval with two distinct methods, natural language and aggregation querying, extraction control, status checking, and citations. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_sift, list_records, upload_document). No mixing of styles or inconsistent verbs.
15 tools is well-scoped for the domain of document extraction and querying. It covers sift management, document upload, folder operations, record retrieval, multiple query methods, and extraction lifecycle without being excessive.
Core workflows (create/read/update/delete sifts, upload docs, extract, query, browse folders) are covered. Minor gaps like explicit folder deletion or sift-folder unlinking are not present but may be intentionally omitted.