BitsBound MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITSBOUND_API_KEY | Yes | Your BitsBound API key. Get it at https://account.bitsbound.com/api-keys |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| process_contractA | Process a contract through the full 8-stage BitsBound pipeline. ⚠️ BEFORE CALLING THIS TOOL: You MUST gather the following information from the user: REQUIRED - Ask the user:
RECOMMENDED - Ask if not obvious: 3. paperOwnership: "Did the counterparty draft this contract (their paper) or did you draft it (our paper)?" 4. dealValue + dealValueCurrency: "What's the estimated deal value?" 5. industry: "What industry is this contract for?" 6. additionalContext: "Any special context about this deal or relationship I should know?" FOR EMAIL GENERATION - Ask: 7. emailRecipient: "Should I generate a negotiation email to send to the counterparty?" 8. If yes: recipientName, senderName (your name), any additionalContext for the email tone After gathering this context, call the tool. The response includes "importantNote" with when to check back (~45 min). Pipeline: (1) Context Loading, (2) Data Extraction, (3) Party Identification, (4) Research, (5) AI Analysis with 18+ analyzers, (6) Instant Swarm™ redlining, (7) Email Generation, (8) Synthesis. |
| get_analysis_statusA | Check the status of a running or completed contract analysis. Returns progress through the 8-stage pipeline (Context→Extraction→Parties→Research→Analysis→Swarm→Email→Synthesis). When complete, returns deliverables with CLICKABLE BROWSER LINKS: (1) redlinedDocxUrl - presigned URL to download the redlined DOCX (works directly in browser, valid 1 hour), (2) negotiationEmailUrl - URL to view the negotiation email in browser. ALWAYS display both URLs to the user as clickable links. |
| ask_sacA | Ask the Supreme AI Co-Counsel (SAC) questions about an analyzed contract. SAC has full context of the contract and all analysis results. Great for clarifying risks, understanding clauses, or getting negotiation advice. |
| generate_redlineA | Generate a redlined Word document with real OOXML Track Changes (w:ins, w:del) applied directly to the original document. Returns the redlined DOCX as base64. |
| generate_negotiation_emailA | Generate a professional negotiation email to send to the counterparty, explaining requested changes and their rationale. |
| extract_clauseA | Extract and analyze a specific clause type from an analyzed contract. Returns the clause text, risk analysis, and suggested improvements. |
| compare_playbookA | Compare an analyzed contract against a company playbook to identify deviations from pre-approved positions and required approvals. |
| instant_swarmA | PARALLEL REDLINING of entire contract. Spawns N independent SAC agents for N sections simultaneously - maximum parallelization with no lock contention. Each agent (IP, Liability, Indemnification, Payment, Term, etc.) independently analyzes and redlines its section, then all branches merge into a single DOCX with real Track Changes. Returns merged document + per-section results. Requires a completed analysis (use process_contract first). This is the flagship feature - full attorney-quality redlines across the entire contract in parallel. |
| quick_scanA | INSTANT contract analysis (5-10 seconds). Get immediate risk assessment, contract classification, top concerns, and key terms WITHOUT waiting for the full 15-30 minute analysis. Perfect for initial triage or quick questions. Use this FIRST before deciding if a full analysis is needed. |
| ask_clauseA | INSTANT clause Q&A (2-5 seconds). Ask about specific clauses directly WITHOUT needing a prior analysis. Examples: "What does the indemnification clause say?", "Is there a limitation of liability?", "What are the termination terms?" |
| check_dealbreakersA | INSTANT dealbreaker check (3-5 seconds). Quick pass/fail screen against your playbook rules. Identifies blockers, missing required clauses, and who needs to approve. Use before spending time on full analysis. |
| download_fileA | Download a file from BitsBound (e.g., the redlined DOCX with Track Changes). Returns the file as base64-encoded content that can be saved locally. The downloadUrl is provided by get_analysis_status when analysis is complete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| process_contract | 📄 Process Contract - Upload a DOCX and get partner-level redlines with Track Changes, risk analysis, and a negotiation email |
| quick_scan | ⚡ Quick Risk Scan - Get instant risk assessment in 5-10 seconds without waiting for full analysis |
| ask_about_contract | 💬 Ask About a Clause - Upload a contract and ask specific questions about any clause or term |
| check_dealbreakers | 🚨 Check Dealbreakers - Quick pass/fail check against your playbook rules |
| continue_analysis | 📊 Continue Previous Analysis - Resume working with a previously analyzed contract |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Contract Analysis | Full analysis results including all 17 analyzer outputs, risk scores, and recommendations |
| Company Playbook | Pre-approved clause library and negotiation rules |
| Redlined Contract | The redlined DOCX with Track Changes |
TDQS
Scored across 12 tools
Each tool has a distinct purpose with clear boundaries. For example, ask_clause is for instant clause Q&A without prior analysis, extract_clause works on already analyzed contracts, and ask_sac provides contextual advice. Even overlapping areas like check_dealbreakers and compare_playbook serve different functions (quick pass/fail vs. detailed deviation analysis).
All tool names follow a consistent verb_noun pattern (e.g., ask_clause, generate_redline, process_contract) using lower_snake_case. The only slight deviation is 'instant_swarm' which is an adjective_noun but still fits the overall style. No mixing of conventions.
12 tools cover the full contract analysis lifecycle (quick scan, full process, status, clause extraction, redlining, email generation, comparison, etc.) without being excessive. Each tool serves a clear step in the workflow, making the count well-scoped.
The tool surface covers the core domain thoroughly: triage, full analysis, redlining, negotiation email, and comparison. A minor gap is the lack of a tool to list or manage past analyses, but the essential workflows are complete.