INDIVIDUAL MCP TOOL

record_research

Adds research findings, each with its source, quote and confirmation status, to the work record.

ailawframework.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://ailawframework.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for record_research and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ailawframework]
url = "https://ailawframework.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "ailawframework": {
      "type": "http",
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: ailawframework
Remote MCP URL: https://ailawframework.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ailawframework": {
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "ailawframework": {
      "type": "http",
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "ailawframework",
  "transport": "streamable-http",
  "url": "https://ailawframework.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

start_task — Opens a work record for one legal task and returns the clarifying questions the framework needs answered (step 1, define the task), less any already answered in `answers`.
record_answers — Adds the user’s answers to the clarifying questions to the work record.
assess_and_decide — Scores the AI option on adoption, efficiency and governance (step 2), caps governance by the recorded evidence, scores the manual route, and returns the decision, its reasons and the order of preference.
plan_human_work — Sets the level of each of the seven stages of the task (step 3) from the recorded answers, research and decision, and returns what the lawyer and the AI may and may not do at each stage.
work_record — Returns the work record as markdown (steps 4 and 5): the task, the evidence, the decision, the plan, what the AI did, and the checks, approval and release left for the lawyer.
search_library — Searches the framework’s published practice areas, tasks, jurisdiction versions, jurisdictions, firm-wide obligations and software profiles.
get_task_guidance — Returns one task from the practice library: how AI may be used, its level, what the lawyer must review, its checkpoints, restrictions and sources, and its jurisdiction versions.
get_jurisdiction_guidance — Returns the framework’s notes for one jurisdiction, and which stored AI instruments apply to a task in a court or tribunal.