Which AI clients can use the CourtListener MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to CourtListener as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which CourtListener tools are available?

CourtListener reports its tools when your organization connects it. Admins then choose which ones each group can call.

How does CourtListener authenticate?

Sign in the way CourtListener requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

CourtListener

Research case law, PACER filings, citations, oral arguments, judges, financial disclosures, and court alerts.

Book a demo View documentation

Tools

Tools discovered when you connect

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Tools load when your organization connects this server

CourtListener can expose tools based on its deployed version and credentials. Runlayer discovers the available list when your organization connects the server.

Compatibility

Connect CourtListener to the clients your teams already use

27 AI clients can connect to CourtListener through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect CourtListener through Runlayer?

One approved path

Approve CourtListener once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.