Fenix MCP Connector

Bring your AI assistant into your patent practice

The Fenix connector exposes your firm's Fenix workspace to MCP-compatible AI assistants — Claude, Harvey, and others — so an assistant can read and act on live matter data, always as an authenticated person, within that person's permissions.

Overview

Fenix is a patent prosecution platform for law firms and in-house IP teams. It manages the full lifecycle of a patent matter: intake and matter creation, application drafting, USPTO data import, office action response, claim management, attorney review and certification workflows, and docketed task tracking.

The connector serves this platform over the Model Context Protocol (Streamable HTTP transport). Each law firm has its own dedicated MCP server URL:

https://mcp.fenix.ai/<firm>/mcp

The firm tenant is fixed by the URL path before any credential is read, so it cannot be influenced by the caller. Long-running operations, such as USPTO import pipelines, complete within a single request.

Authentication

Every connection resolves to a person, never to a firm — there are no shared firm-wide tokens. Two credential types are supported:

OAuth 2.1 — interactive clients

Standards-based discovery (RFC 9728 protected-resource metadata) with dynamic client registration and PKCE. Users sign in through the firm's existing Fenix identity provider — Google Workspace, Azure AD, SAML, or Duo — and approve an explicit consent screen. Access tokens are RS256-signed JWTs verified against a published JWKS, live for 15 minutes, and are audience-bound (RFC 8707) to the single firm's MCP server: a token issued for one firm fails validation at any other firm's endpoint on the audience check alone. Refresh tokens are supported.

Personal access codes — headless clients

Generated by each user on their own Fenix profile settings page, individually revocable, with a 90-day default expiry. Same identity, scoping, and audit plumbing as OAuth.

Security model

  • Tenant isolation. One database per firm; the tenant is derived from the URL and nothing else — no tool accepts a tenant or database override. Audience-bound tokens make cross-tenant replay fail cryptographically, independent of application logic.
  • Role-based tool scoping. Every tool maps to a scope, and every Fenix role to a default scope set. Effective scopes are the intersection of the user's role and the credential's scopes — a credential can only narrow what its owner may do, never widen it. Out-of-scope tools are not even visible to the assistant, and each handler re-checks its scope server-side.
  • Full audit trail. Every tool call is logged with the resolved person identity and credential ID.
  • Rate limiting is enforced per credential.
  • No third-party data sharing. All data served is the firm's own matter data, scoped to the authenticated user's permissions at the moment of the call.

What the connector can do

The server registers roughly ninety tools, gated per tenant plan and per user role. A live capability listing is always available in-band: the schema resource enumerates every resource and action the authenticated connection can reach.

Matter & project management

Create patent projects, assign attorneys and inventors, manage the assignment queue, track and complete project tasks, and archive matters.

USPTO integration

Populate a matter directly from USPTO records — application data, claims, and cited references — and import office actions with their references.

Office action response

Build the OA response shell, retrieve cited-reference text, and draft and sign office action responses.

Drafting & claims

Work with patent application templates, read and edit claim limitations, and save versioned documents.

Review & certification

Attorney review queues, checklist workspaces with per-item attestation, checklist certification, and e-signature of forms.

Practice operations

Time logging, user lookup, and session context — plus interactive artifacts like the Fenix patent editor delivered straight into the client.

Getting connected

  1. Add https://mcp.fenix.ai/<your-firm>/mcp as a custom connector in your MCP-compatible assistant.
  2. Sign in with your normal Fenix login when the browser window opens, and approve the consent screen.
  3. Headless or CLI setups: generate a personal access code under your Fenix profile → Settings → Connect your assistant.

Not on Fenix yet, or want the connector enabled for your firm? Reach us at contact@fenix.ai.

Experience the power of

AI Patent Management today

✨ Try Fenix.AI

Transform your patent workflow in under 5 minutes. Yes, really.