BitsBound MCP Server
Official# 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
| 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: admin@bitsbound.com
- Website: https://bitsbound.com
- Privacy Policy: https://www.bitsbound.com/privacy
- DPA: https://www.bitsbound.com/dpa
## License
MIT - BitsBound, Inc.
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.