Resources · Claude connector

Claude CourtListener connectorWhat Claude can do in your CourtListener account.

The Claude CourtListener connector exposes 14 tools. 9 read US court records and citations, 4 change the alerts on your account, and 1 is a generic gateway whose effect no source spells out. Below: what Claude finds, what it changes and where it stops.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can search CourtListener

CourtListener is the legal research platform run by a nonprofit: US court opinions from federal and state courts, the RECAP archive of PACER filings, judges and oral arguments. With the connector, a paralegal or a journalist asks Claude a research question in plain English and Claude queries that database itself, with the same filters as the website.

Check a brief before it goes out. Paste the draft and analyze_citations pulls every case citation, matches it against the database and labels each one good, bad or ambiguous, with the canonical case name, court and date.

Research a question across courts. search covers case law, dockets, judges and oral arguments, and get_endpoint_item opens one opinion or docket in full once you have its ID.

Keep watch on a case. subscribe_to_docket_alert signs your account up for email updates on a docket, and create_search_alert sets a recurring alert on a query, from real time to monthly.

What it will not do: the alerts are emails from CourtListener, not Claude reacting to a new filing, because a connector only works while Claude answers you. The data is US law only. And the four alert tools change your CourtListener account, so they are the ones to watch. If you want a filing to trigger a chain of actions on its own, that is an automation tool's job, a different trade listed on the Integrations hub.

Vocabulary

Five words before you connect

The Claude vocabulary this page uses, in one minute.

Connector
A link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
Tool
One named action the connector opens to Claude. Claude chooses which to call on its own, and the directory sheet lists every name.
Authorization
The service's own sign-in screen, where you grant the access Claude will use. Given once per person, and it can be revoked.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the conversation at that moment.
MCP
The shared standard connectors run on, which is what lets an assistant like Claude talk to an outside service such as CourtListener.
Connect

Connect CourtListener to Claude in three steps

  1. 01

    Find CourtListener

    Open Claude's settings, go to Customize and then Connectors, and look up CourtListener. On a Team or Enterprise workspace, an Owner or Primary Owner enables it before members can each sign in.

  2. 02

    Sign in to your account

    Click Connect on its row. CourtListener opens its own sign-in window, where you log in with your CourtListener account. If the link breaks later, Disconnect and connect again.

  3. 03

    Review the permissions

    Read the authorization screen before you approve it: that screen belongs to CourtListener and decides what the access covers. You can also cut access from your CourtListener profile, and the publisher says it stops at once.

Tools

The 14 tools, by what they touch

CourtListener gives Claude 14 tools: 9 that read your account, 4 that change something in it, and 1 no official source describes.

Nine tools read, four change your alerts, and one generic gateway has no stated effect. Names stay exactly as Claude shows them.

  • 9 read
  • 4 write
  • 1 not documented

What Claude reads (9)

9 tools

Searches, lookups and citation checks that leave your account as it is.

get_endpoint_schema

Fetches the description of one API endpoint: which filters it accepts and which fields it returns. Claude reads it so a later query is built correctly.

When it helps
a question about financial disclosures needs fields the plain search does not expose.

Sourcegithub.com · October 1, 2026 ↗

get_endpoint_item

Opens a single record, an opinion, a docket or a judge, from its CourtListener ID, so Claude works from the full item instead of a search snippet.

When it helps
a search turned up the right ruling and you want its complete metadata before quoting it.

Sourcegithub.com · October 1, 2026 ↗

get_choices

Lists the accepted values of a coded field, like court identifiers or case statuses, so Claude does not guess a code that the database would reject.

When it helps
you ask for rulings from a specific state supreme court and Claude needs its exact court ID.

Sourcegithub.com · October 1, 2026 ↗

get_counts

Returns the total number of results for a query already run. Some queries only compute that figure on request, so it comes as a separate call.

When it helps
a reporter wants to know how many dockets mention a term before reading any of them.

Sourcegithub.com · October 1, 2026 ↗

get_more_results

Fetches the next page of a previous search or gateway call, which is how Claude goes past the first batch of matches.

When it helps
the first page of a broad search on algorithmic discrimination is not enough to map the case law.
Watch out
paging state lives on the server for one hour of inactivity.

Sourcegithub.com · October 1, 2026 ↗

extract_citations

Pulls every legal citation out of a block of text, including statutes, short cites, id. and supra. It runs on the server alone, with no API call and no rate limit.

When it helps
you want the list of authorities in an opposing brief before checking any of them.

Sourcegithub.com · October 1, 2026 ↗

analyze_citations

Goes one step further than extraction: each unique case citation is checked against the database and comes back labelled good, bad or ambiguous, with the canonical name, court and date.

When it helps
a junior associate's memo has to be cite-checked before the partner reads it.
Watch out
large jobs come back in batches with a job ID.

Sourcegithub.com · October 1, 2026 ↗

resume_citation_analysis

Picks up a citation check that hit the per-call ceiling and verifies the citations still waiting, using the job ID the first run handed back.

When it helps
a long appellate record carries more citations than a single pass can verify.

Sourcegithub.com · October 1, 2026 ↗

What Claude changes (4)

4 tools

Alert and subscription tools that modify your CourtListener account state.

create_search_alert

Approval: see the rule

Saves a query as an alert on your CourtListener account, delivered in real time, daily, weekly or monthly.

What Claude asks for
the publisher says the client should prompt for confirmation; no source states that Claude does, so the general approval rule below applies.
When it helps
you want a daily email for new filings that mention a given statute.

Sourcegithub.com · October 1, 2026 ↗

delete_search_alert

Approval: see the rule

Removes one of your saved search alerts, identified by its ID, so the matching emails stop.

What Claude asks for
no source confirms a prompt from Claude for this deletion; the approval rule further down is what covers it.
When it helps
a matter closed and the alert on its subject now only clutters your inbox.

Sourcegithub.com · October 1, 2026 ↗

subscribe_to_docket_alert

Approval: see the rule

Signs your account up for email updates on one specific docket, so new entries in that case reach your inbox.

What Claude asks for
how Claude confirms this subscription is not described anywhere; the default approval rule is the reference.
When it helps
you follow a federal lawsuit against a company you cover and want each new filing.

Sourcegithub.com · October 1, 2026 ↗

unsubscribe_from_docket_alert

Approval: see the rule

Ends the email updates for a docket you previously followed, which edits your alert settings on CourtListener.

What Claude asks for
no published page details a confirmation step here, so rely on the general rule in the approvals section.
When it helps
a case settled and its docket no longer needs watching.

Sourcegithub.com · October 1, 2026 ↗

Effect not documented (1)

1 tool

The publisher names this tool's purpose but never says whether it only reads, so it stays in its own group.

call_endpoint

Its publisher presents it as a generic gateway to any endpoint of the CourtListener API with custom parameters, but no official text says whether it only reads or can also change data. This page draws no conclusion from that. Claude's general approval rule, below, is the only reference for it.

Approvals

What Claude checks with you first

By default, Claude stops and asks for confirmation before each action it takes on an account for someone.

CourtListener's documentation says the four alert tools modify your account and that a client should prompt before calling them, adding that alerts can also be managed on the website. It recommends; it does not describe what Claude shows. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt each time, and can restrict what a connector does for the whole organization. Claude works only with the rights of the person who connected.

Plans

Which Claude plans include it

No official source publishes plan availability connector by connector. It is a real hole in the catalog, not a gap in our research.

The general rule is the only published one: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner opens a connector for the organization before members connect. The connector's sheet in the official directory is the only place showing its live state, so check it from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers, so nothing happens on its own when a new opinion is published.

This connector is documented by its publisher alone: no Claude help article covers it. Its tool list is an observed floor, not a promise, since an administrator can open actions no public sheet shows. The directory badge is no security audit, and Anthropic states on every sheet that it does not pick a publisher's tools or guarantee their behavior. For a connector from a very different field, see the Claude affinity connector.

Need help

Need help connecting CourtListener to Claude?

A person reads every message.

FAQ

Questions about the Claude CourtListener connector

01What can Claude do with the CourtListener connector?
Claude can research US court records in CourtListener from a conversation. It searches case law, dockets, judges and oral arguments, opens a single opinion or docket by ID, pages through results and counts them. It also extracts citations from a text and verifies each case citation against the database, labelling it good, bad or ambiguous. Four more tools manage search alerts and docket subscriptions on your account, and a generic gateway reaches the rest of the API.
02Can Claude change anything in my CourtListener account?
Yes, four documented tools change your account, all of them about alerts. Claude can create or delete a search alert and subscribe to or unsubscribe from email updates on a docket. The publisher says these tools modify your account state and that alerts can also be managed on the website. The search and citation tools only read. One more tool, the generic API gateway, is not described as reading or writing, so this page does not say either way.
03Does Claude ask before it creates or deletes an alert?
By default, Claude asks for confirmation before each action it takes on an account for someone. CourtListener's documentation adds that a client should prompt before the alert tools run, but no source describes Claude's own prompt for them, so the general rule is what applies. On Team and Enterprise workspaces, owners can let members skip the prompt for certain actions, or restrict the connector to research only for the whole organization.
04Which Claude plans is the CourtListener connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. The connector's sheet in the official directory is the one place that shows its current state for your account, so check it there.
05Does Claude see my whole CourtListener account?
Claude works with the access of the account you signed in with and nothing more. You sign in with your CourtListener account through Claude's sign-in flow, with no separate API token, and the publisher describes the search and read tools as pure proxies to CourtListener. The server keeps only short-lived paging and citation job state, which expires after an hour of inactivity. Revoking the connection from your CourtListener profile stops all access immediately.
06How many citations can Claude check in one go?
The analysis tool verifies up to 250 unique case citations per call, an estimated ceiling the publisher sets to stay within request budgets. A longer document does not fail: the tool returns a job ID, and Claude continues with the resume tool until every citation is checked. Plain extraction has no such ceiling on the API side, since it runs entirely on the server without calling the database. Searches, for their part, return at most 100 items per call.
07Claude or an automation tool for CourtListener?
They do different jobs, so pick by use. Claude with this connector is for research in a conversation: asking a question, reading opinions, cite-checking a brief, or setting an alert because you asked. An automation tool runs on its own, for instance to push every new docket entry into a case tracker without anyone asking. CourtListener's own email alerts cover part of that need, but chaining further actions belongs to automation, not to this connector.