mcpField
C

contract-automation

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

About contract-automation

BitsBound MCP Server provides contract analysis for legal and business teams, producing DOCX redlines with actual OOXML Track Changes alongside clause and risk analysis. Deal context informs revisions, and it can also draft negotiation emails.

Key features

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

Use cases

  1. 01Reviewing a contract and producing proposed revisions
  2. 02Extracting specified clause types
  3. 03Assessing risk and contract favorability
  4. 04Drafting a negotiation email

MCP support

The MCP server exposes tools to process contracts, check analysis status, extract clauses, and generate negotiation emails. It can connect through Claude Desktop or Claude.ai Custom Connectors.

Configuration

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

mcp.json · Universal config
{
  "mcpServers": {
    "com-bitsbound-contract-automation": {
      "command": "npx",
      "args": [
        "-y",
        "@bitsbound/mcp-server"
      ]
    }
  }
}
Run commandnpx -y @bitsbound/mcp-server

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-server1.0.8

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

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.