
Scope
Dispatch litigation and legal-services matters to Scope vendors and read matter status from AI coding workflows without a separate legal ops UI.
Overview
Scope is an MCP server for the Operate phase that lets agents dispatch litigation matters to legal-services vendors and query Scope API data over stdio.
What is this MCP server?
- Scope MCP (npm @jackgillen15-dev/scope-mcp v0.1.1) dispatches litigation work to legal-services vendors
- Read tools work on demo matters without SCOPE_API_TOKEN; writes need a bearer token from scope-bid.vercel.app/settings
- Configurable SCOPE_API_BASE (default https://scope-bid.vercel.app) and optional SCOPE_ORG_SLUG for multi-tenant buyers
- Stdio transport for Claude Code, Cursor, and other MCP clients
- Hosted docs at scope-bid.vercel.app/mcp
- Server version 0.1.1 on npm
- Default API base: https://scope-bid.vercel.app
- 3 environment variables documented (SCOPE_API_BASE, SCOPE_API_TOKEN, SCOPE_ORG_SLUG)
Community signal: 1 GitHub stars.
What problem does it solve?
Legal teams using AI workflows still re-enter matter details in Scope’s web UI to dispatch vendor work, breaking context and slowing bids.
Who is it for?
Legal ops builders, litigation support shops, and Scope customers wiring vendor dispatch into Claude Code or Cursor.
Skip if: General indie SaaS founders with no litigation vendor workflow or anyone seeking legal advice without a Scope account.
What do I get? / Deliverables
After you register the npm server and token, your agent can read Scope matters and dispatch work from the editor while you stay in one thread.
- Matter reads and demo exploration via Scope API tools
- Dispatch of litigation work to vendors through scope_dispatch_matter (authenticated)
- Org-scoped operations when SCOPE_ORG_SLUG is configured
Recommended MCP Servers
Journey fit
Operate covers running the business after ship; legal spend and vendor dispatch are ongoing operational decisions, not greenfield product build. Iterate subphase fits adjusting how work gets outsourced—re-dispatching matters, checking bids, and tightening legal ops loops from the agent environment.
How it compares
Legal-services vendor dispatch MCP, not a generic task manager or contract-drafting skill.
Common Questions / FAQ
Who is Scope for?
Teams on the Scope platform who want MCP tools to list matters, use demo data without a token for reads, and dispatch litigation work with an API token for writes.
When should I use Scope?
Use it during Operate when you routinely outsource litigation tasks through Scope and want agents to trigger dispatch and check matter state from MCP.
How do I add Scope to my agent?
Install @jackgillen15-dev/scope-mcp, set SCOPE_API_BASE if needed, add SCOPE_API_TOKEN from scope-bid.vercel.app/settings for write tools, optionally set SCOPE_ORG_SLUG, and register stdio in your MCP client.