> For the complete documentation index, see [llms.txt](https://help.paxton.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paxton.ai/help/integrations/using-paxton-in-claude-mcp.md).
# Using Paxton in Claude (MCP)
Connect your Paxton account to Claude and run legal research with verifiable citations, without leaving the conversation.
The Paxton connector gives Claude direct access to U.S. statutes, regulations, court rules, case law, and indexed agency decisions, and returns citations you can open and verify in Paxton.
> **Included with your subscription.** If you already have Paxton legal research access, the MCP connector is included at no separate fee and uses your existing account and organization access.
**What you can do in Claude**
* Search U.S. statutes, regulations, rules, and case law
* Search indexed administrative decisions, including EEOC and NLRB
* Retrieve the full text of any source Paxton returns
* Inspect citation relationships and available status information with the Paxton AI Citator
* Open source links to review the authority yourself
**Before you start**
* An active Paxton account with legal research access. New to Paxton? Create an account at [app.paxton.ai/sign-up](https://app.paxton.ai/sign-up), then connect once legal research is enabled on your account.
* A Claude account. The connector works in Claude on web, desktop, and mobile.
> **Note for firms on Claude Team or Enterprise.** A Claude workspace administrator may need to enable the Paxton connector before it appears for your users. If you do not see it, ask your workspace admin to approve it first.
**Connect Paxton to Claude**
1. In Claude, open **Settings > Connectors** and select the **Discover** tab.
2. Find **Paxton Legal Research** and click **Connect to Claude**. You can also start from the [Paxton Legal Research connector page](https://claude.com/connectors/paxton-legal-research).
3. Sign in with your Paxton credentials when prompted, then approve access.
4. Paxton now appears under **Your connectors**, and in the **connector list** in a new Claude chat when you click the + button next to the message box.
*The Paxton Legal Research connector under Settings > Connectors > Discover in Claude.*
If your admin has asked you to add the connector manually, open **Settings > Connectors > Add custom connector** in Claude and enter the connector URL:
```
https://paxton-mcp-connector-xmfvvq3waa-uc.a.run.app/mcp
```
**Run your first research question**
In a new Claude chat, click the + button next to the message box, hover over **Connectors**, and make sure **Paxton** is toggled on. Name the jurisdiction and be specific about the issue. The first time Claude uses Paxton, you'll be asked to approve it. Click **Allow**.
* "Using Paxton, find Seventh Circuit authority on whether a failure to accommodate claim requires an adverse employment action. Give me the supporting passages."
* "Search EEOC decisions on constructive discharge in retaliation cases and summarize how the Commission has analyzed the issue."
* "Pull the full text of the statute you cited and check its citator status."
Claude will show you which Paxton tool it used and return the authorities with links. Follow the citations and read the source before you rely on anything.
**What the connector can and cannot do**
| Can | Cannot |
| ------------------------------------------------- | --------------------------------------------------------------- |
| Search legal sources and administrative decisions | Access your Paxton matters, matter files, or uploaded documents |
| Retrieve full source text and citation status | Edit, upload, or save documents to Paxton |
| Open authorities in Paxton | Change anything in your Paxton account |
The connector is read only. For matter-centric work such as drafting against your case record, syncing your DMS, or building a timeline, keep working in the Paxton platform.
> **Legal research requires professional review.** Search results and citation relationships do not establish that an authority is controlling, current, or sufficient for a legal proposition. Always read the source and apply your own judgment.
**Troubleshooting**
**Paxton does not appear in the connector list.** Confirm the connection completed under **Settings > Connectors** in Claude. On Claude Team or Enterprise, confirm your workspace admin has enabled the connector.
**You are asked to sign in repeatedly.** Disconnect Paxton under **Settings > Connectors**, then reconnect and complete the sign-in in the same browser where you are signed in to Paxton.
**Claude answers without using Paxton.** In a new Claude chat, click the + button next to the message box, hover over Connectors, and make sure Paxton is toggled on. Say "using Paxton" in your prompt so Claude calls the connector instead of answering from its own knowledge.
**A narrow source is not returned.** The connector searches legal sources only. If the authority you need does not come back, search for it in the Paxton platform, where you can request sources on demand.
**Data and security**
The connector uses your existing Paxton account and organization access, so you see only what you are already entitled to see in Paxton. It cannot reach your matters or private files, and it cannot change anything in your account. Your documents and data are never used to train Paxton AI.
Still stuck? Contact Paxton support and we will help you get connected.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.paxton.ai/help/integrations/using-paxton-in-claude-mcp.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
