Claims MCP server
{
"mcpServers": {
"scope-claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@latest"
],
"env": {
"SCOPE_API_TOKEN": "<scope_api_token>"
}
}
}
}{
"mcpServers": {
"scope-claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@latest"
],
"env": {
"SCOPE_API_TOKEN": "<scope_api_token>"
}
}
}
}{
"mcpServers": {
"scope-claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@latest"
],
"env": {
"SCOPE_API_TOKEN": "<scope_api_token>"
}
}
}
}{
"servers": {
"scope-claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@latest"
],
"env": {
"SCOPE_API_TOKEN": "${input:scope_api_token}"
}
}
},
"inputs": [
{
"id": "scope_api_token",
"type": "promptString",
"description": "Scope api token",
"password": true
}
]
}{
"mcpServers": {
"scope-claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@latest"
],
"env": {
"SCOPE_API_TOKEN": "<scope_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @scope-bid/scope-claims-mcpversion 1.0.9
What it does
Three MCP servers that connect AI assistants to Scope.bid's vendor dispatch platform for legal services, insurance claims, and AEC work. Users can send vendor requests and receive bids back in ten minutes through tools that manage matters, rosters, negotiations, and vendor credentials.
- Dispatch IME requests, surveillance coordination, and peer reviews to credentialed vendors in the insurance claims vertical and receive competitive bids.
- Send legal matters (court reporters, records retrieval, translation, experts) to vendors and track live quotes and roster management.
- Request subcontractor prequalification, bonding capacity checks, and safety records for AEC projects through vendor dispatch.
Tools this server exposes
| Tool | Does |
|---|---|
| scope_dispatch_matter | Send a matter to vendors and receive live quotes. |
| scope_briefing | Get a daily briefing across all open matters. |
| scope_get_matter | Retrieve details of a specific matter. |
| scope_list_matters | List all matters in an organization. |
| scope_list_categories | List available service categories for dispatch. |
| scope_list_vendors | List available vendors. |
| scope_list_roster | List vendors in your organization's roster. |
| scope_set_vendor_tier | Assign or update a vendor's tier classification. |
| scope_remove_from_roster | Remove a vendor from your roster. |
| scope_award_matter | Award a matter to a selected vendor. |
| scope_roster_audit | Audit your vendor roster for compliance or status. |
| scope_vendor_health | Check the health and performance metrics of a vendor. |
| scope_spend_rollup | Get aggregated spending data across vendors and matters. |
| scope_credential_alerts | Receive alerts about vendor credential changes or expirations. |
| swp_clarify | Clarify details within an existing Scope Work Protocol negotiation session. |
| swp_accept | Accept terms in a Scope Work Protocol negotiation session. |
| swp_reject | Reject terms in a Scope Work Protocol negotiation session. |
| swp_session_status | Check the status of a Scope Work Protocol negotiation session. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.