How to Use the CourtListener MCP in CrewAI

Q: How do I configure the CourtListener MCP Server in CrewAI?

Install crewaitools. You pass your Vinkius endpoint directly into the mcps array on your Agent definition, or use MCPServerHTTP for advanced filtering.

Q: Can multiple CrewAI agents share CourtListener MCP search results?

Yes. When your researcher agent calls searchopinions, the results enter the shared memory pool. Your analyst agents read those case summaries immediately.

Q: How do I restrict which CourtListener tools a CrewAI agent can use?

Use toolfilter in your python setup. You give one agent access to getopinion for reading text, while restricting another agent to just searchdockets.

Deploy autonomous legal research crews in CrewAI to map case precedent and monitor federal dockets.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CourtListener MCP to CrewAI

Create your Vinkius account to connect CourtListener to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup CourtListener with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Deploy Autonomous Legal Teams

Your Researcher agent runs `search_dockets` to find active litigation and dump the raw results into the crew's shared memory. One agent is never enough for serious case prep. An Analyst agent picks up that data and hits `get_court` to pull jurisdiction rules. The two agents collaborate to build a complete profile of the upcoming trial without you writing a single loop.

Map Precedent with the MCP Server

A specialized agent recursively calls `list_citations` to trace legal logic back to the original precedent. Finding the exact origin of an argument takes hundreds of pages of reading. Another agent simultaneously runs `get_opinion` on every cited case to check if the ruling was overturned. The hierarchical execution ensures the heavy text analysis happens only after the MCP Server maps the citation tree fully.

Audit Judicial Conflicts

The `list_financial_disclosures` tool powers autonomous monitors that watch for judicial bias. A dedicated agent flags anything matching corporate defendants in your active cases. If it spots a match, a moderator agent takes over. It pulls the judge's full history via `get_judge` and escalates a warning to your legal team's dashboard.

Setup guide

Set up CourtListener MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke CourtListener tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="CourtListener Analyst",
    goal="Access and analyze CourtListener data via MCP.",
    backstory="Expert analyst with direct CourtListener access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent CourtListener transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="CourtListener Analyst",
        goal="Access and analyze CourtListener data via MCP.",
        backstory="Expert analyst with direct CourtListener access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent CourtListener transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CourtListener. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect CourtListener now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about CourtListener MCP in CrewAI

Install crewai[tools]. You pass your Vinkius endpoint directly into the mcps array on your Agent definition, or use MCPServerHTTP for advanced filtering.

Yes. When your researcher agent calls search_opinions, the results enter the shared memory pool. Your analyst agents read those case summaries immediately.

Use tool_filter in your python setup. You give one agent access to get_opinion for reading text, while restricting another agent to just search_dockets.

You define the execution strategy in your crew setup. Set it to sequential, and the system guarantees the docket search finishes before the analysis agent starts reading.

We execute your tools in ephemeral V8 isolates. The exact court cases and judge names your agents look up are destroyed the moment the run completes. Nothing touches a database.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript