How do I find my CourtListener API Key?

Log in to your [**CourtListener account**](https://www.courtlistener.com/profile/api/), and you will find your API Key under the **API Tokens** section. Copy and paste it below.

Can the agent search for both opinions and dockets?

Yes. Use the `search_opinions` tool for legal judgments and `search_dockets` for case records. Your agent will return matching results from the Free Law Project database.

Is it possible to list judicial citations via the agent?

Yes. The `list_citations` tool allows your agent to retrieve all precedents and subsequent citations for any opinion by providing its Opinion ID, helping you map the legal landscape.

CourtListener MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: CourtListener
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to CourtListener through Vinkius, pass the Edge URL in the `mcps` parameter and every CourtListener tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="CourtListener Specialist",
    goal="Help users interact with CourtListener effectively",
    backstory=(
        "You are an expert at leveraging CourtListener tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in CourtListener "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About CourtListener MCP Server

Empower your AI agent to orchestrate your entire legal research workflow with CourtListener, the world's leading free and open platform for legal data. By connecting CourtListener to your agent, you transform complex legal searches into a natural conversation. Your agent can instantly search for opinions, audit court dockets, and retrieve detailed judge information without you ever touching a technical portal. Whether you are conducting case law research or monitoring judicial activity, your agent acts as a real-time legal assistant, ensuring your research is always grounded in open and accessible data.

When paired with CrewAI, CourtListener becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CourtListener tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Opinion Auditing — Search for legal opinions by keyword and retrieve detailed metadata, including court name and date filed.
Docket Oversight — Query court dockets to stay on top of ongoing litigation and case filings in real-time.
Judicial Intelligence — Retrieve detailed information about judges and their financial disclosures to maintain strict control over your research context.
Citation Discovery — List citations for specific opinions to understand the legal network and precedents.
Court Governance — List all available courts and their metadata to ensure your jurisdictional research is accurate.

The CourtListener MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect CourtListener to CrewAI via MCP

Follow these steps to integrate the CourtListener MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from CourtListener

Why Use CrewAI with the CourtListener MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CourtListener through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

CourtListener + CrewAI Use Cases

Practical scenarios where CrewAI combined with the CourtListener MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries CourtListener for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries CourtListener, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain CourtListener tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries CourtListener against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

CourtListener MCP Tools for CrewAI (10)

These 10 tools become available when you connect CourtListener to CrewAI via MCP:

get_court

Get details for a specific court

get_judge

Get details for a specific judge

get_opinion

Get details for a specific opinion

list_citations

List citations for an opinion

list_courts

List all courts

list_financial_disclosures

List judge financial disclosures

list_judges

List judges

list_opinions

List opinions

search_dockets

Search for court dockets

search_opinions

Search for legal opinions

Example Prompts for CourtListener in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with CourtListener immediately.

"Search for court opinions about 'copyright fair use'."

"Show me details for judge ID 1234."

"Check for dockets related to 'SpaceX' in 2024."

Troubleshooting CourtListener MCP Server with CrewAI

Common issues when connecting CourtListener to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

CourtListener + CrewAI FAQ

Common questions about integrating CourtListener MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.