Skip to main content
For autonomous agents and the humans deploying them

A general counsel your agent can call.

Give your agent a trusted legal execution layer. It can read entity state, draft from templates, route counterparties, and escalate to a Story attorney when a judgment call is required.

Attorney-Client Privilege Protected

Designed for real legal execution

Story gives your agent a structured legal workflow surface instead of forcing it to improvise with fragile prompts.

Agents move fast. Attorneys stay in control where legal judgment is required.

01 - Capabilities

What your agent can actually do

Read organization state

Access scoped company context, matter status, and structured legal metadata needed to make the next workflow decision.

Draft from approved templates

Generate first-pass drafts from Story-managed templates instead of ad hoc prompts so outputs stay aligned with policy and process.

Route counterparties

Move work to the right audience with role-aware routing and visibility boundaries that match real legal collaboration.

Escalate to real counsel

When legal judgment is needed, hand off directly to Story attorneys without losing context or restarting the process.

02 - Architecture

How the integration works

  1. Authenticate

    OAuth 2.1 + PKCE, scoped organization access

  2. Connect

    Attach your agent to Story MCP endpoints

  3. Orchestrate

    Run legal workflows with policy-aware routing

  4. Escalate

    Bring in Story counsel when human judgment is required

The agent handles deterministic workflow steps. Story attorneys handle privileged legal judgment. The protocol boundary keeps both sides in the right lane.

03 - Trust posture

Controls built for legal workflows

Least-privilege access

Every call is scoped to the organization and operation your token is authorized to perform.

Privilege-aware boundaries

Audience and visibility controls are enforced in-platform so agent automation cannot bypass disclosure rules.

Auditable execution trail

Actions are logged with system context so teams can review what happened, when, and by whom.

Attorney-supervised outcomes

AI assists process execution. Legal calls that require professional judgment escalate to licensed counsel.

04 - Quickstart

Connect in minutes

Use Story MCP to let your agent perform legal-operational steps without improvising legal logic from scratch.

You get repeatable execution speed from agents while keeping privilege, auditability, and attorney escalation where it belongs.

Example `claude_desktop_config.json` entry
{
  "mcpServers": {
    "story": {
      "url": "https://backend.story.law/mcp/story-agent",
      "type": "http"
    }
  }
}

Need help configuring your first integration? Request a sandbox key and we will walk your team through setup.

05 - Legal notices

No legal advice by default. Agent responses and automated workflow outputs are informational unless and until reviewed by a licensed attorney.

Jurisdiction matters. Availability, workflow behavior, and legal constraints may vary by matter type and governing jurisdiction.

Privilege depends on context. Attorney-client privilege and work-product protections depend on relationship, role, and disclosure posture.

Human escalation is required for legal judgment. High-impact decisions and privileged legal calls must be escalated to Story counsel or other authorized attorneys.

Execution authority is policy-bound. Signing, approval, and disclosure actions are controlled by platform permissions and legal workflow safeguards.

Platform terms govern usage. Use of Story MCP and related services is governed by applicable engagement terms, privacy commitments, and platform policies.

This page is for product and workflow information. It does not create an attorney-client relationship by itself.