Connect ABIGAIL to any MCP client
ABIGAIL runs a Model Context Protocol server. Point any MCP capable client at one URL and it gains 55 patent prosecution tools, running against the same account and the same docket as this web app.
https://mcp.abigail.app/mcpSigning up and buying credits happen here on the web. Everything after that happens inside your client.
Sign up at abigail.app. Every MCP tool runs against your account, so this comes first.
In your client, add a custom MCP server and paste the URL below. Any client that speaks streamable HTTP MCP works.
Your client discovers the authorization server and opens the ABIGAIL sign-in page. Approve it once. There is no key to copy.
Look up an application, read your docket, draft a response, export a document. Every result comes back as JSON.
Every tool requires a signed-in ABIGAIL account. A request without a valid token is answered with HTTP 401 and a WWW-Authenticate challenge, which is what a compliant client needs to find the authorization server on its own. Your client runs the OAuth 2.1 flow with PKCE for you, so there is no key to copy and no secret to store.
Auto-draft responses to all USPTO communication types with a 10-expert AI pipeline.
Step-by-step ROA wizard: parse claims, run experts, select strategies, generate DOCX.
Lookup any application, analyze rejections, search prior art, generate forms, and file with USPTO.
Every output is verified against source documents. Anti-hallucination architecture drops unverifiable claims.
MPEP-verified deadline calculator with extension fees, holiday adjustments, and urgency grouping.
Prepare complete filing packages with documents, fees, and step-by-step Patent Center instructions.
Streamable HTTP transport, stateless: one POST per JSON-RPC message
Every tool result is JSON, so an integration can parse it rather than read it
Read-only tools are annotated in the protocol, so writes are distinguishable from lookups
Dynamic client registration, so there is no manual onboarding step