mcpField
B
Bitsbound Mcp Server

Bitsbound Mcp Server

Local
github.com/BitsBoundLegal & Government0Updated 44w ago
Repository

About Bitsbound Mcp Server

Bitsbound Mcp Server is a contract-analysis MCP server for legal teams using Claude Desktop or Claude.ai. It produces DOCX redlines with actual OOXML Track Changes and supports clause review and negotiation preparation.

Key features

  1. 01Contract processing and redlines
  2. 02OOXML Track Changes in DOCX
  3. 03Clause extraction and analysis
  4. 04Risk scoring and favorability views
  5. 05Negotiation email generation
  6. 06Deal-context-aware analysis

Use cases

  1. 01Reviewing contract clauses and risks
  2. 02Preparing customer-favorable redlines
  3. 03Drafting negotiation emails

MCP support

It exposes contract processing, analysis-status, clause-extraction, and negotiation-email tools to MCP clients. It can be configured for Claude Desktop or connected remotely from Claude.ai using HTTP/OAuth 2.0.

#contract#legal#redlines#analysis#negotiation#document

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "bitsbound": {
      "command": "npx",
      "args": [
        "-y",
        "@bitsbound/mcp-server"
      ],
      "env": {
        "BITSBOUND_API_KEY": "<BITSBOUND_API_KEY>"
      }
    }
  }
}
Run commandnpx -y @bitsbound/mcp-server
Environment variables to set
BITSBOUND_API_KEYSecret

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@bitsbound/mcp-server

Tools

4

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
filePathstringNoRECOMMENDED: Absolute path to DOCX file (e.g., "/Users/john/Documents/contract.docx"). Server reads file directly.
docxBase64stringNoAlternative: Base64-encoded DOCX content. Use filePath instead when possible.
fileNamestringNoOriginal filename. Auto-extracted if using filePath.
contractVerticalenumNoContract type. Determines analyzers and party options.saas | ma | vc | employment | nda | equipment-lease | equipment-financing | security-agreement | loan | commercial-lease | professional-services | miscellaneous
representingPartystringNoWho you represent: saas(customer/vendor), ma(buyer/seller), vc(investor/founder), employment(employer/employee), nda(disclosing-party/receiving-party), equipment-lease(lessee/lessor), equipment-financing(debtor/secured-party), security-agreement(debtor/secured-party), commercial-lease(tenant/landlord), professional-services(client/service-provider), loan(borrower/lender)
aggressivenessLevelnumberNoRedline aggressiveness 1-10. Default: 5
dealValuenumberNoOptional: Deal value for risk calibration
dealValueCurrencyenumNoCurrency. Default: USDUSD | EUR | GBP | CAD | AUD
additionalContextstringNoOptional: Deal context, priorities, relationship notes
paperOwnershipenumNoWho drafted? their-paper=counterparty (default), our-paper=we draftedtheir-paper | our-paper
enableEmailGeneratorbooleanNoGenerate negotiation email? Default: true
emailContextobjectNoEmail context
emailContext.recipientNamestringNo
emailContext.senderNamestringNo
emailContext.additionalContextstringNo

Details

From the project README

BitsBound MCP Server

AI-powered contract analysis with partner-level redlines for Claude Desktop and Claude.ai.

Features

  • Contract processing with partner-level redlines
  • Real OOXML Track Changes (w:ins/w:del) - not markup, actual Word revisions
  • Clause extraction and analysis
  • Risk scoring and favorability dashboards
  • Negotiation email generation
  • Deal context awareness (value, industry, aggressiveness)

Installation

Claude Desktop (Recommended)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "bitsbound": {
      "command": "npx",
      "args": ["-y", "@bitsbound/mcp-server"],
      "env": {
        "BITSBOUND_API_KEY": "sk_live_your_api_key"
      }
    }
  }
}

Get your API key at: https://account.bitsbound.com/api-keys

Claude.ai Custom Connectors (HTTP/OAuth 2.0)

For remote MCP access via claude.ai:

  1. Name: BitsBound
  2. URL: https://bitsbound-mcp-server.onrender.com/mcp
  3. Client ID: bitsbound-mcp
  4. Client Secret: Your BitsBound API key (sk_live_xxx...)

OAuth 2.0 endpoints:

  • Discovery: /.well-known/oauth-authorization-server
  • Authorize: /oauth/authorize
  • Token: /oauth/token

Tools

ToolDescription
process_contractUpload and analyze a contract - produces redlined DOCX with Track Changes
get_analysis_statusCheck analysis progress and retrieve deliverables
extract_clausesExtract specific clause types from a contract
generate_negotiation_emailCreate a professional negotiation email

Example Usage

Please analyze this contract and create a customer-favorable redline with aggressive changes

Claude will ask for:

  • Contract file (drag & drop DOCX)
  • Deal context (value, industry)
  • Aggressiveness level (1-10)
  • Email recipient details

Registry

  • MCP Registry: io.github.taytrom/bitsbound-contract-automation
  • npm: @bitsbound/mcp-server

Support

License

MIT - BitsBound, Inc.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.