lmwharton/sieve-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIEVE_API_KEY | Yes | Your Sieve API key (get one free at https://app.sieve.arceusxventures.com/settings) | |
| SIEVE_API_URL | No | API base URL | https://api.sieve.arceusxventures.com |
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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sieve_screenA | Run a Sieve IMPACT-X Quick Screen on a startup. Analyzes the company across 7 dimensions (Innovators, Market, Product, Advantage, Commerce, Traction, X-Factor) and returns an analysis ID. Takes 2-5 minutes to complete. Upserts -- if the company was previously screened, returns the existing deal (set confirm=true to re-screen). Two ways to use:
|
| sieve_statusA | Check the progress of a Sieve analysis. Returns which IMPACT-X dimensions are complete with their scores, overall progress percentage, and current phase. |
| sieve_resultsA | Get the full results of a completed Sieve analysis. Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/ Need More Info), executive summary, key strengths, and key concerns. |
| sieve_usageA | Check your Sieve API usage for the current billing period. Shows screens used, monthly limit, tier, and organization name. |
| sieve_dealsA | List deals in your Sieve pipeline. Search by company name or list all deals. Returns deal metadata including Sieve scores for screened deals. |
| sieve_memoA | Get or generate an investment memo for a deal. If generate=false (default), retrieves the existing memo. If generate=true, creates a new memo (~15-30 seconds). Requires a completed screen. |
| sieve_dataroom_addA | Add a document to a deal's data room. Creates the deal if needed. This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room. Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal. Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL). |
| sieve_dataroomA | List all documents in a deal's data room. Shows what files and content have been uploaded for a deal, along with their processing status. |
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 8 tools
Each tool has a clearly distinct purpose: listing documents, adding documents, listing deals, running screens, checking status, retrieving results, getting memos, and checking usage. No two tools overlap in functionality.
All tools share the 'sieve_' prefix, but naming patterns are mixed: some are plain nouns (e.g., sieve_dataroom, sieve_deals) while others use verb_noun (e.g., sieve_dataroom_add). This minor inconsistency prevents a perfect score.
With 8 tools, the set covers the full document screening lifecycle without unnecessary duplication. Each tool serves a necessary role, and the count feels appropriate for the domain.
The tool set covers the primary workflow: add documents, screen, check status, get results, and generate memos. However, it lacks update or delete operations for documents or deals, which could be useful but are not critical for core use.