6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search a public catalog of practitioner-written legal Agent Skills.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Lawve AI MCP server connects Claude, ChatGPT and other MCP agents to a public catalog of legal Agent Skills — methodology documents written by practicing lawyers and legal technologists. Anthropic's directory lists two read-only tools that search the catalog and fetch one skill's manifest. It reaches no case file, client document or filing system.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
https://lawve.ai/en/learn/mcp-setup; that path returned 404 on 2026-08-23, as did llms.txt, llms-full.txt and the .md suffix on the same host. No /learn/ route exists anywhere in Lawve's 12,212-URL sitemap. The directory's privacy_policy field is stale in the same way, pointing at https://lawve.ai/en/privacy, which also 404s — so two directory fields carry the same dead /en/ prefix, suggesting the site dropped a locale prefix after the listing was written. The server itself is fully alive — a dead doc URL and a dead server are different findings. The working sources are Lawve's own posts and legal pages, reached through the sitemap and linked below.available_skills; the authenticated endpoint prevented any prompts/list call, so its real state is unknown.No. Both tools operate on Lawve's public skills catalog, which is a library of published methodology documents, not a document management system. The connector holds no integration with a matter system, a DMS or a file store, and its single application scope is marketplace:read. Nothing in the surface reaches a client file.
Neither. Both listed tools are read-only, and the scope confirms it. The catalog does contain drafting skills, so a search result can return instructions that tell your agent how to draft. Your agent then does the drafting locally, using your own tools. Nothing is filed, sent or submitted through this connector.
Yes, in two places. Lawve's Terms of Use open with the sentence that Lawve does not provide legal advice, adding that output is not a substitute for professional judgment. Its Anthropic partnership post repeats that skills are starting points for professional review, not legal advice. Both statements are unusually prominent.
Nothing directly. We found no privilege waiver language and no privilege guarantee in Lawve's terms or privacy policy, so we record that as silence rather than as reassurance. The terms do require that content you publish does not unlawfully disclose confidential or privileged information, which addresses publishing rather than connector use.
Anthropic's directory lists two, and Lawve publishes no tool list of its own to check that against. The two names are lawvable_search_skills and lawvable_get_skill_manifest. Because no vendor enumeration exists, we cannot report a clean diff, only that there is no second list to diff against.
One application scope, marketplace:read. The server's RFC 9728 resource descriptor declared exactly that scope on 2026-08-23, and its authorization server advertises it alongside openid, offline and offline_access. The scope names read and no listed tool carries a write verb, so the grant and the tool surface agree.
Yes. Lawve's privacy policy describes the site as a public knowledge hub whose published resources can be viewed by anyone, and its skill pages load without signing in. The connector's value is bringing that catalog into a conversation, not unlocking private content. Sign-in is still required at the MCP endpoint.
Treat it as untrusted. The catalog is community-published, so a skill manifest is text written by a third party that arrives as agent instructions. Lawve runs a security review and shows a pass or fail badge per skill, but review is not endorsement under its own terms. Read a manifest before acting on it.
/learn/ route exists (retrieved 2026-08-23) · retrieved 2026-08-23robots.txt, Allow: / with no Content-Signal line (retrieved 2026-08-23) · retrieved 2026-08-23www-authenticate header naming the resource metadata document; RFC 9728 metadata at https://mcp.lawve.ai/.well-known/oauth-protected-resource/mcp; authorization server metadata at https://auth.lawve.ai/.well-known/oauth-authorization-server (2026-08-23) · retrieved 2026-08-23privacy_policy field points at https://lawve.ai/en/privacy, which 404s on the same dead /en/ prefix as the nominated documentation URL; the working page is linked here instead.Connect Lawve AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.