About bitsbound-contract-automation
BitsBound MCP Server analyzes contracts for Claude Desktop and Claude.ai, producing redlines and clause and risk analysis. It includes actual OOXML Track Changes in generated DOCX files and can draft negotiation emails using deal context.
Key features
- 01Contract analysis and redlines
- 02OOXML Track Changes in DOCX
- 03Clause extraction and analysis
- 04Risk scores and favorability dashboards
- 05Negotiation email generation
Use cases
- 01Review a contract and create a redline
- 02Extract and assess contract clauses
- 03Draft negotiation emails using deal context
MCP support
The MCP server exposes tools to process contracts, check analysis status and deliverables, extract clauses, and generate negotiation emails. It connects to Claude Desktop locally or through the remote HTTP/OAuth endpoint for Claude.ai.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEBitsBound 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:
- Name: BitsBound
- URL:
https://bitsbound-mcp-server.onrender.com/mcp - Client ID:
bitsbound-mcp - 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
| Tool | Description |
|---|---|
process_contract | Upload and analyze a contract - produces redlined DOCX with Track Changes |
get_analysis_status | Check analysis progress and retrieve deliverables |
extract_clauses | Extract specific clause types from a contract |
generate_negotiation_email | Create 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
- Email: [email protected]
- Website: https://bitsbound.com
- Privacy Policy: https://www.bitsbound.com/privacy
- DPA: https://www.bitsbound.com/dpa
License
MIT - BitsBound, Inc.
Comments
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.