Contract Automation

com.bitsboundPublished by bitsbound.comv1.0.8Updated Oct 24, 2026

AI contract automation with partner-level redlines, OOXML Track Changes, and risk analysis.

Overview

AI-generated overview

A local MCP server that lets an assistant analyze contracts, produce Word redlines with real Track Changes, score risk and draft negotiation emails.

What you can do
Upload and analyze a contract, producing a redlined DOCX with real Word Track Changes revisions and partner-level redlines, with deal context such as value, industry and aggressiveness level taken into account. Check analysis progress and retrieve the resulting deliverables. Extract specific clause types from a contract. Generate a professional negotiation email, including recipient details. Report risk scoring and favorability dashboards.
When to use it
Useful for legal, sales or procurement work where someone wants an assistant to review a DOCX contract, propose redlines, pull out particular clauses, assess risk, or draft a negotiation email, especially from Claude Desktop.
Requirements
Runs as a local stdio process via npx from the npm package @bitsbound/mcp-server, so Node.js and network access are needed. A BitsBound API key is required, supplied as the BITSBOUND_API_KEY environment variable; the README also describes a remote HTTP/OAuth 2.0 connector option using the API key as client secret. Desktop only.
Before you install
Requires a BitsBound API key, which the README shows as a live secret value in configuration; keep it private. Contract files and deal context are sent to BitsBound's service for analysis, so confidential documents leave the machine. The server writes redlined DOCX deliverables and generates emails, so review outputs before sending or relying on them.

Installation

In SourceWeft

  1. Open Contract Automation in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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):

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.

Source: README.md at commit d5cc5a7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.8LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.