- Home
- Resources
- Integrations
- Lawstronaut
Claude Lawstronaut connectorWhat Claude can do in your Lawstronaut account.
The Claude Lawstronaut connector exposes 15 tools. All 15 read Lawstronaut's legal corpus and 0 write anything. Below: how Claude narrows a jurisdiction down to one text, gets the original file, spots recent changes, and what it will not do for you.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can search Lawstronaut
Lawstronaut gathers legislation, regulations, case law, guidance and enforcement actions from official sources in more than 170 jurisdictions. With the connector, Claude queries that corpus while it answers, and each result can be traced back to where it came from.
Start from the right country code. Lawstronaut tells Claude to call list_jurisdictions first, so it knows which codes the other tools accept before searching anything.
Drill down, then read. Claude can walk the classification (domains, subdomains, categories, subcategories, law types), filter documents with list_documents, and pull a full text or a Markdown version of the one that matters.
Show the source. get_source_url returns a signed link to the original file, such as a PDF, valid for a limited time. Handy when a colleague asks where a quote comes from.
Watch what moved. horizon_scan looks at recent legal documents and answers plain questions about new rules.
What Claude will not do with this connector: by default its sheet exposes reading only, so no tool saves, annotates or files anything in your account. Nothing runs on its own either, so no alert fires when a law changes. Other connectors are listed on the Integrations hub.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and a service you already use, here Lawstronaut, so Claude can query it as it answers.
- Tool
- One named action the connector hands Claude, like listing jurisdictions. Claude picks the ones it needs on its own while replying.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use. Given once per person, and it can be withdrawn later.
- Approval
- The confirmation Claude waits for before an action that changes an account. It appears in the conversation at the moment it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as a legal database.
Connect Lawstronaut to Claude in three steps
- 01
Find Lawstronaut
Open Claude's settings, go to Customize, then Connectors, and search for Lawstronaut. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first; members then connect one by one.
- 02
Connect from its row
Click Connect on the Lawstronaut row and sign in through the window the service opens itself. If the link fails later, Disconnect it and connect again.
- 03
Review the access
Read the authorization screen before accepting. It belongs to the service, not to Claude, and it sets what the access covers. You can take that access back later from the same place.
The 15 Lawstronaut tools, all in reading
Lawstronaut gives Claude 15 tools: 15 that read your account, 0 that change something in it.
Every tool on the sheet reads the corpus. Names stay exactly as Claude shows them.
- 15 read
Tools index
What Claude reads (15)
15 toolsFifteen tools that browse, filter and retrieve legal texts without changing anything.
list_jurisdictions
Returns every country or state covered by the Lawstronaut corpus, with its name, code and type. Lawstronaut asks Claude to call it first, since the other tools only accept a valid code.
list_portals
Shows the official legal portals and websites of one jurisdiction, which can be narrowed by name, tag or language. Results also report how many links were collected from each portal.
list_domains
Retrieves the broad legal domains of a jurisdiction, the top level of Lawstronaut's classification, with paging when the list runs long. A name filter is available too.
list_subdomains
Goes one level below a domain and lists its subdomains, which a domain identifier selects. Claude can filter them by name and page through them.
list_categories
Brings up the categories found under a subdomain, the next rung of the classification, searchable by name and returned page by page so a long list stays readable.
list_subcategories
Opens a category and returns the subcategories it contains, selected by its identifier. A name filter keeps the list short when a category is large.
list_law_types
Gives the types of legal text available under a subcategory, the last step of the classification, with a filter on the type name and paging.
list_authority_types
Enumerates the kinds of authority behind the texts of a jurisdiction, optionally restricted to one portal or one authority type, with paging when the jurisdiction has many of them.
list_issuing_authorities
Names the bodies that issued texts in a jurisdiction, such as a ministry or an agency, and can be narrowed to a portal or to one authority.
list_documents
Searches the documents of a jurisdiction with structured filters (portal, title, section, address, status, publication or collection date, authority, tag) and paging. Only crawled content comes back.
get_document_text
Pulls the full plain text of the documents matching your filters in one jurisdiction, so Claude can read a statute end to end rather than a summary.
get_markdown
Fetches the same documents in Markdown, a lightweight format that keeps headings and lists, using the same filters as the plain-text tool, so Claude can keep the layout.
get_document_with_version
Brings back one document at one specific version, rather than whichever wording is current. Like the other fourteen tools, it only reads and leaves the corpus as it is.
get_source_url
Produces a signed link to the original source file of a document, a PDF for instance. Lawstronaut says the link only works for a limited time.
horizon_scan
Scans recently published legal documents across jurisdictions to surface what changed lately, in answer to plain questions about new rules.
What Claude asks before acting
By default, Claude stops and asks before each action it takes on an account for someone. With Lawstronaut, every listed tool reads, and no source describes a prompt for any of them.
The publisher marks all 15 tools as read only, and no source describes a specific confirmation for any of them. On Team and Enterprise workspaces, owners still decide whether members may let some actions pass without a prompt, and they can restrict what a connector may do for the whole organization. Claude also uses only the rights of the person who connected, nothing beyond: a source your access does not open stays closed to it.
Which plans can use it
No official source publishes plan availability connector by connector, and none of the 819 directory sheets displays it.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before members connect. For Lawstronaut's current state, its sheet in the official directory is the only place to check.
Where the Lawstronaut connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no alert goes out by itself when a regulation is published or repealed.
Everything here comes from the publisher: the directory sheet and the tool list its server publishes. No Claude help page covers Lawstronaut. The partner badge is not a security audit, and Anthropic states it neither picks the tools a publisher exposes nor guarantees they behave as announced. A read-only sheet is also a floor, not a promise: an administrator can open actions that appear on no public sheet. Anthropic's own advice on every sheet applies: only connect a publisher you know.
Need help connecting Lawstronaut to Claude?
A person reads every message.