CoCounsel Legal

Hand legal work to Thomson Reuters' CoCounsel from Claude.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the CoCounsel Legal connector does

The CoCounsel Legal MCP server hands legal work from Claude to Thomson Reuters' CoCounsel agent, which reasons over Westlaw and Practical Law. Anthropic lists five tools. One of them routes any legal request into CoCounsel's whole catalogue, and one uploads your documents to Thomson Reuters. Sign-in is OAuth.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

CoCounsel Legal tools (5)

  • start_cocounsel_chat
  • ask_cocounsel
  • upload_file
  • list_cocounsel_files
  • get_cocounsel_output

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The tool count is not the capability count. ask_cocounsel dispatches into a catalogue of 17 skills and 10 workflows documented by Thomson Reuters on 2026-08-23. No client-side allowlist can constrain the routing, because skill selection is natural language resolved server-side with no inspectable parameter. Approving the tool approves the catalogue.
  • The surface is not bounded by any published list. Thomson Reuters states new skills become reachable through the same tool automatically, without reconnecting. Its own help sidebar already links a "Skill: Web Search" that appears in no table and has no page in its help sitemap. Any tool census of this connector — Anthropic's, ours, or the vendor's — is a snapshot, not a ceiling.
  • A write path exists and it carries privileged material. upload_file sends contracts, briefs and case files to Thomson Reuters' platform. It is user-initiated and cannot fire implicitly, but it is the tool to think hardest about before connecting.
  • Retention and deletion of uploaded files are undocumented for this product. The connector guide names no retention period, no deletion mechanism and no storage location, and the connector has no delete tool. Deletion is possible only manually in the CoCounsel web app. The nearest published retention default — indefinite, until the user deletes — belongs to a different CoCounsel product.
  • CoCounsel Legal has no security page. Thomson Reuters publishes security pages for CoCounsel Tax, Audit & Accounting and the CoCounsel-for-Outlook add-in, and none for CoCounsel Legal. Those two give opposite answers on whether user content improves the product, and this connector publishes neither.
  • Privilege is not addressed anywhere we could find. Zero hits across the connector guide, help centre article, GenAI Terms, General Terms, privacy statement, Data Security Addendum, AI Usage Policy and a sweep of the help sitemap's slugs. A peer legal connector, Consilio's Aurora, warns explicitly about waiver risk. We record Thomson Reuters' silence as an absence, not as an assurance.
  • No application scopes exist. The RFC 9728 descriptor advertises openid, profile, email and offline_access; the Auth0 authorization server behind it advertises fourteen scopes that are all OpenID identity claims plus offline_access. Nothing at the OAuth grant separates reading research from uploading a client file.
  • The MCP App widget could not be audited. The directory sets has_mcp_app: true and the vendor names a get_cocounsel_token tool for displaying that view, explicitly not exposed to the model. Its bundle is behind the OAuth wall; we did not authenticate. What it renders and what its controls do is unknown, not absent.
  • The vendor's tool table publishes labels, not identifiers. None of the five snake_case names appears literally on Thomson Reuters' guide, so our diff is a semantic match and a silent rename would be invisible to it.
  • Thomson Reuters' AI Usage Policy requires professional review. Clause 4 bars using Output to assist in providing legal advice or recommendations unless a licensed professional reviews it first, and bars automated decision-making. This constrains unattended agentic use, not just redistribution.
  • The connector was replaced, and the previous endpoint is still answering. Anthropic's directory now points at cocoagent-service.cocounsel.thomsonreuters.com. The former host, legal-mcp.thomsonreuters.com, still returned a 401 auth challenge and still served its old four-tool connector guide on 2026-08-23 — it is simply no longer the connector Anthropic lists. If you configured this server manually before 2026-08-23, check which host your client holds.
  • This is a pilot and Thomson Reuters says it may withdraw it without notice. Anthropic's directory carries that statement, adding that it may be modified or suspended "in whole or in part".
  • Output is AI-generated and needs checking. Reports carry Westlaw citation links precisely so each authority can be opened at source. Thomson Reuters directs you to westlaw.com and Practical Law to verify each citation.
  • US-focused, three jurisdictions at a time. Research targets up to three US jurisdictions in a single run. The guide describes no non-US coverage.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or annotation state is published here.
  • No rate limits are published. The connector guide states no request quota, concurrency cap or throttle. The General Terms reserve a right to apply metering or usage restrictions, which is a reservation rather than a documented limit.
  • Run duration is stated only loosely. Document review and shorter drafting "usually complete in a few minutes"; a concise research run takes several minutes; an expanded run "can take 10 minutes or more". No upper bound is given.

Frequently asked questions

How many tools does the CoCounsel Legal MCP server have?

Five in Anthropic's directory, and the count tells you almost nothing. One of the five, ask_cocounsel, is a natural-language dispatcher that routes into Thomson Reuters' CoCounsel catalogue server-side. That catalogue is 17 skills and 10 workflows on Thomson Reuters' own help page as of 2026-08-23, so the reachable operation count is 27, not five.

Does the CoCounsel connector upload my client documents to Thomson Reuters?

Yes, when you ask it to. The upload_file tool opens a file-picker in the Claude chat and attaches your document to your CoCounsel session on Thomson Reuters' platform. Claude's own paperclip button does not reach CoCounsel. Nothing leaves your machine without that deliberate tool call, but a contract or brief is privileged material by construction.

How long does Thomson Reuters keep a file uploaded through the connector?

Thomson Reuters does not say for this product. The connector guide states the file stays available for the rest of that chat, names no retention period, and never says ending the session deletes it. Deletion exists only as a manual action in the CoCounsel web app, not through Claude. The nearest published default, indefinite retention until the user deletes, is documented for a different CoCounsel product.

Does using the CoCounsel connector waive attorney-client privilege?

Thomson Reuters does not address the question in its connector documentation. That is an absence, not an all-clear. A competing legal connector in this catalogue, Consilio's Aurora, warns explicitly that sending privileged material to a third-party AI environment may risk waiver. Thomson Reuters publishing no equivalent warning is not a statement that no risk exists.

What OAuth permissions does the CoCounsel Legal connector request?

Four, and none of them narrows anything. The server's RFC 9728 descriptor advertised openid, profile, email and offline_access on 2026-08-23. The first three are OpenID identity claims and the fourth is a refresh token. No scope separates reading a research memo from uploading a client contract, so consent is all-or-nothing.

Can I store Westlaw content the CoCounsel connector returns?

Not as a knowledge base or an index. Anthropic's directory carries Thomson Reuters' Usage Terms barring use of connector content as a knowledge base, index, embeddings store or retrieval source for any AI system, including retrieval-augmented generation. The General Terms separately bar indexing the Property. Building a firm vector store from retrieved memos is prohibited on the face of those clauses.

Can an AI agent act on CoCounsel output without a lawyer reviewing it?

Thomson Reuters' AI Usage Policy says no. Version 1.0, dated 2026-01-23, bars using the Output to assist in providing legal advice, decisions or recommendations unless reviewed by a licensed or qualified professional first. That policy is incorporated into the agreement and sits at the top of its precedence order, so it binds agentic chaining.

What subscription do I need for the CoCounsel Legal MCP connector?

A CoCounsel Legal package subscription on an active Thomson Reuters account. Anthropic's directory adds that you must have switched to the next generation of CoCounsel. A Claude administrator must also enable the connector for your organisation once before anyone can connect, and Thomson Reuters directs entitlement questions to your firm's administrator.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put CoCounsel Legal to work.

Connect CoCounsel Legal once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio