Connect Scope to your AI
Pick your AI. Add Scope. Start dispatching.
Same five categories of legal-services professionals across every surface. No app to install, no card on file. Your AI calls Scope; Scope returns quotes in seconds.
Limited release
The connector is live and every step below works. Scope is opening to a small group of design partner firms and founding professionals first, so real dispatches to real professionals are not switched on yet. See what works today.
Step 1
Pick the AI you already use
Scope connects to the assistant you have open right now. Picking one swaps the instructions in step 2.
Step 2
Connect
Add Scope to Claude as a connector. Nothing to install on your side.
Connector URL
https://scope.bid/api/mcp/legalYour client opens Scope's sign-in and consent screen - no keys to paste.
- Open Claude in your browser and go to your connector settings.
- Add a custom connector and paste the URL above.
- Approve the consent screen, then start a new chat and ask for a professional.
Menu names differ by Claude plan and version, so the wording above is the shape of the flow rather than an exact click path.
Step 3
Confirm it worked
One question tells you the connection is live and reading your firm's account.
Want the demo instead
Demo mode is a separate, explicit path with zero setup. Send Authorization: Bearer scope_pk_demo_2026 or the header X-Scope-Demo-Mode: true and every response comes back stamped demo_mode: true with sample data: fictional matters, fictional professionals, no dispatch and no money. The steps above use no demo token, so they take you to a real Scope account, not the demo.
Why no app, no account, no card?
Scope is a protocol layer the AI calls directly. There is nothing to install on your side beyond adding the connector to the AI you already use. The professional keeps every dollar of their published price. Scope's fee is a separate line on the firm's invoice, billed at completion - never a deduction from the professional, and never part of a legal fee the firm bills its client.
Building against Scope rather than connecting to it? The developer story lives at /mcp: transports, tools, tokens, and the self-hosted gateway.