Westlaw MCP Server & Agent Skill

What is the Westlaw API, and what can an agent read from it?

There is no general public Westlaw search API. Thomson Reuters lists Westlaw APIs, such as Westlaw US Litigation Analytics, on its Developer Portal, which requires a Thomson Reuters sign-in to view.

• API: Thomson Reuters Developer Portal APIs (e.g. Westlaw US Litigation Analytics API) (REST)
• Access: Partner or license program
• Authentication: not published by Thomson Reuters

Customer- and partner-gated. The Developer Portal (developerportal.thomsonreuters.com) redirects to a Thomson Reuters login; access to Westlaw APIs is arranged through Thomson Reuters for licensed customers and partners.

Authentication for Westlaw APIs is documented only inside the sign-in-gated Developer Portal and could not be verified. The portal itself signs users in through auth.thomsonreuters.com.

What can an agent read from Westlaw?

• Litigation analytics — Westlaw US Litigation Analytics API: analytics from the Westlaw Litigation Analytics feature.
• Research via CoCounsel Legal — Through the CoCounsel Legal MCP integration, research and drafting grounded in Westlaw, Practical Law and KeyCite.
• Citation validity — KeyCite validity signals, surfaced through CoCounsel Legal.

What can an agent write to Westlaw?

This skill only reads Westlaw data; it documents no write calls, so an agent built on it cannot change a Westlaw record.

Research queries and matter facts entered into Westlaw or CoCounsel can reveal client strategy and are attorney work product; treat them as client confidential.

How do I connect Westlaw to an AI agent over MCP?

Thomson Reuters announced in May 2026 an MCP integration that connects Claude to CoCounsel Legal, which reasons over Westlaw. It is for CoCounsel Legal subscribers, not a general Westlaw API.

The practical path is to host a small MCP server that wraps the Thomson Reuters Developer Portal APIs (e.g. Westlaw US Litigation Analytics API), or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Westlaw agent skill do?

The Westlaw skill is one SKILL.md file named iblai-connect-westlaw. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Westlaw SKILL.md

Save it as .claude/skills/iblai-connect-westlaw/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Thomson Reuters' documentation on October 20, 2026. Test it against your own Westlaw setup before you rely on it.

What can I ask a Westlaw agent to do?

• “Ask CoCounsel for Delaware authority on fiduciary duty in squeeze-out mergers, with KeyCite status”
• “Is Smith v. Jones still good law?”
• “Pull litigation analytics on how long employment cases before Judge Lee take to reach trial”
• “Draft a research memo on the enforceability of non-competes in California”

How do I run a Westlaw agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Westlaw MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Legal — what ibl.ai deploys in this sector

Which ibl.ai agents work with Westlaw data?

• Case Research — Legal
• Brief Drafting — Legal

Which ibl.ai platform skills does a Westlaw agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting Westlaw to an AI agent?

Which other data sources can an AI agent connect to alongside Westlaw?

Which other Legal systems have a connector?

• Clio Manage — Legal practice management system
• Docusign eSignature — Electronic signature platform
• iManage Work — Legal document and email management system
• Ironclad — Contract lifecycle management system
• LexisNexis — Legal research content and AI API
• NetDocuments — Cloud legal document management system
• PACER — U.S. federal court records system
• RelativityOne — E-discovery and legal review platform

Every connector, grouped by sector, is on the connectors hub.