@dropspot/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DROPSPOT_API_KEY | Yes | Your Drop Spot API key generated from Settings → Developer API & MCP (for example, ds_live_...). | |
| DROPSPOT_API_BASE_URL | No | The Drop Spot API base URL, for example https://godropspot.com/api/v1. | https://godropspot.com/api/v1 |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_intake_requestA | Create a new Drop Spot client document intake request (dossier). Generates a zero-password magic upload link and optionally emails the client. |
| list_intake_requestsB | List client intake requests in the Drop Spot workspace. Filter by status or client email. |
| get_intake_requestB | Retrieve full details for an intake request by ID, including checklist items, upload progress, and file metadata. |
| review_itemA | Approve or reject a document uploaded by a client. If rejected, sends automated feedback asking the client to re-upload. |
| get_file_download_linkA | Generate a secure, temporary presigned download URL for an uploaded file so an AI or operator can inspect the document contents. |
| list_clientsA | List and search clients in the Drop Spot directory. Filter by name, email, or company. |
| get_clientA | Retrieve detailed profile information for a specific client, including their active and historical document requests. |
| create_or_update_clientC | Add a new client to the directory or update an existing client’s contact details, phone, company, or notes. |
| list_templatesC | List available checklist templates (including starter packages for tax returns, KYC, and mortgage underwriting). |
| get_templateB | Get full details and checklist items for a specific reusable template. |
| create_templateC | Create a new reusable document checklist template with predefined items and categories. |
| update_templateB | Edit an existing custom checklist template (update name, description, or checklist items). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Client Intake Requests | Real-time JSON dossier feed of all open document requests in the active workspace. |
| Workspace Client Directory | Complete client roster including names, emails, phone numbers, and company metadata. |
| Checklist Templates | All reusable document checklist templates available in the workspace. |
TDQS
Scored across 12 tools
The set splits cleanly into three resource families (intake requests, clients, templates) with one-off actions (review_item, get_file_download_link) that have clearly stated purposes. Minor friction: review_item's name doesn't say what it reviews (a document), and get_file_download_link slightly overlaps with get_intake_request, which also returns file metadata, but descriptions disambiguate.
Nearly all tools follow a verb_noun snake_case pattern (create_intake_request, list_clients, get_template, update_template). Deviations are minor: review_item drops the noun subject, and create_or_update_client uses a compound verb, but neither breaks readability or predictability.
Twelve tools is well within a healthy range and each maps to a concrete operation across the three resources. No redundant or filler tools are present.
Intake requests only support create/list/get — there is no update, cancel/archive, delete, or resend-magic-link operation, which are natural lifecycle steps for a dossier. Templates and clients similarly lack delete, so the surface covers the happy path but leaves dead ends for cleanup and correction workflows.