Lightbringer documentation

Documentation for people and agents working with Lightbringer through the Model Context Protocol (MCP). It explains how the connection works, what an agent can and cannot do, the states a request moves through, and how invention data is handled. It is written from the same facts as llms.txt. Lightbringer is a patent service: registered patent attorneys draft, review, file and prosecute; the platform and the MCP connector bring that work to where you and your agents already work.

How the Lightbringer MCP works

• A remote server at mcp.lightbringer.com/mcp over Streamable HTTP. There is no server code to install; the connector metadata and the tool catalogue are public in the mcp-connector repository.
• Authorisation: OAuth 2.1 authorization code with PKCE (S256) and dynamic client registration, scopes mcp:read and mcp:write. The server advertises its authorization server through RFC 9728 protected resource metadata; unauthenticated requests get a 401 with a WWW-Authenticate header that points there. The authorization server publishes RFC 8414 metadata.
• Prerequisites: a Lightbringer account, an organisation, and MCP access switched on by an organisation moderator under Settings, then Advanced. A connection is bound to one organisation and to the user's existing permissions. Never paste passwords or access tokens into a chat.
• 20 tools (9 read-only, 11 not read-only) and 4 prompts. Every tool carries readOnlyHint and destructiveHint annotations; clients discover what is available through tools/list. The catalogue is on developer resources.
• Setup for Claude, Claude Code, ChatGPT, Codex, Cursor, Windsurf and any MCP client: Lightbringer MCP guide. Skills for the three workflows are installed separately from the connector; a connection alone does not install skills.

What an agent can do

• Capture innovations: identify ideas from a conversation or authorised technical sources, search existing records, register new innovations and enrich them over time without creating duplicates.
• Refine a description: start automated feedback, follow the task and read the findings. This checks clarity, completeness and technical depth; it does not establish novelty or patentability.
• Request patent preparation: ask Lightbringer to prepare a selected innovation for filing. The response confirms that a request was made or already existed; it returns no task and it is not a filing.
• Collaborate on reviews: read report and patent-draft reviews, attorney comments and proposed amendments; add comments, reply, approve or request changes within the user's existing permissions.
• Use portfolio and strategy context: retrieve records and strategy reports the organisation has granted access to.

What an agent cannot do

• File anything with a patent office. Submitting a disclosure sends it for review inside Lightbringer.
• Start a paid engagement or make a payment. Engagement, drafting, filing and prosecution are confirmed by an authorised human in the customer's organisation.
• Deliver an attorney review, a novelty search or a freedom-to-operate assessment. Automated analysis of a description is none of these; they are professional engagements with Lightbringer's attorneys.
• Reach records outside the connected organisation or beyond the user's permissions.
• Edit IP strategy or classify trade secrets through dedicated tools. These are not available through MCP today; use the platform or continue with the Lightbringer team.

The three states

A matter moves through three distinct states, and an agent should name the right one.

• Request received: Lightbringer has your disclosure or preparation request. Nothing is filed and no engagement exists yet.
• Engagement accepted: an authorised person in your organisation has confirmed the engagement with Lightbringer's attorneys, and attorney work begins.
• Application filed: a patent office has received the application, filed by Lightbringer's attorneys, a USPTO-registered practitioner or a partner attorney for the jurisdiction.

The current state of each matter is shown in the Lightbringer application. Milestone tracking after filing is not exposed through a dedicated MCP tool today.

Human decisions

Engaging Lightbringer for a filing, approving a draft for filing and instructing responses to a patent office are confirmed by an authorised person in the customer's organisation. Actions that change data are confirmed with the user first. Agents propose; people decide.

Security and data

• SOC 2 Type 2, encryption at rest and in transit, access controls: Trust Center.
• Lightbringer does not train AI on customer invention data: data security.
• Data an assistant reads through MCP sits in the user's session with that assistant's provider. Check the provider's data controls before sharing unfiled invention details.
• Automated feedback tasks and their findings expire 30 days after creation; reading them does not extend retention.
• Privacy policy and terms of service.

Where to go next

• Developer resources: every endpoint, metadata document, plugin, skill and listing, and what is not offered.
• API statement: Lightbringer has no public REST or GraphQL API; what exists instead.
• Patent FAQ: 300+ attorney-written answers, and patent guides.
• Pricing: Platform free with no time limit; Starter $7,200 USD / €5,999 EUR / 59,995 SEK per patent application per year plus official fees; Growth custom for 5+ applications per year. Sign up.