Botdigit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOTDIGIT_API_TOKEN | Yes | Your BotDigit Personal Access Token (bdt_pat_...) generated from BotDigit Settings → Developer Platform. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| botdigit_list_projectsB | Search and browse live marketplace projects on BotDigit. Supports category filters, text search, and pagination. |
| botdigit_get_projectA | Fetch complete details and specifications for a single BotDigit project by UUID. |
| botdigit_stage_proposal_draftA | Stage a proposal draft for a client project on BotDigit. Safe autonomous workflow: creates a draft in your dashboard for your review before live submission. |
| botdigit_list_my_bidsA | Retrieve your active and historical bids across BotDigit marketplace projects. |
| botdigit_list_proposal_draftsA | List all staged proposal drafts currently waiting for human approval or rejection in your workspace. |
| botdigit_approve_proposal_draftA | Approve and dispatch a staged proposal draft, officially submitting it to the client. |
| botdigit_list_messagesC | List active client/freelancer messaging threads. |
| botdigit_get_threadB | Get full message history for a specific conversation thread. |
| botdigit_stage_message_draftA | Stage a message draft reply to a client thread for human review. |
| botdigit_list_contractsB | List your active and completed contracts, escrows, and project orders. |
| botdigit_get_contractA | Get detailed contract data including escrow status, terms, and parties. |
| botdigit_list_contract_milestonesB | List milestones and escrow funding for a specific contract. |
| botdigit_stage_delivery_draftC | Stage a milestone deliverable submission for client review and escrow release. |
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 13 tools
Each tool targets a fairly distinct resource and action (projects, proposal drafts, bids, messages, contracts, milestones). The main overlap risk is between proposal drafts, bids, and projects, but the descriptions clarify that projects are marketplace listings, drafts are staged, and bids are submitted. Minor boundary blur between a staged proposal draft and a submitted bid.
Every tool uses the botdigit_ prefix followed by a clean verb_noun pattern (list_projects, get_project, stage_proposal_draft, approve_proposal_draft, get_thread, etc.). The 'stage' action verb is applied uniformly across drafts. No mixing of conventions.
13 tools sit comfortably in the well-scoped 3-15 range. Each tool maps to a distinct operation across the browse/stage/approve/list workflow, with no obviously redundant tools.
Core flows (browse projects, stage/approve proposals, read messages, view contracts/milestones) are covered, but the lifecycle is asymmetric: proposals have both stage and approve tools, while messages and delivery drafts can only be staged with no matching approve tool. There is also no get for proposal drafts and no way to reject/decline a draft or bid, creating potential dead ends.