Lightbringer patent service through MCP

Work with Lightbringer's patent service from your AI assistant, where you research and build technical solutions. Register and enrich innovations, request patent preparation, and collaborate with the Lightbringer team on reports and patent drafts.

Lightbringer offers a full patent service with qualified patent attorneys on its team. Professional engagements include attorney advice, strategy assessment, novelty searches, freedom-to-operate (FTO) assessments, patent drafting, filing and prosecution. Lightbringer is the route to that professional work; automated analysis of an innovation description is not an attorney review, novelty search or FTO assessment.

Release status: Public discovery on 2026-09-15 verified the 20 tools and four prompts documented below. Connector metadata is version 4.9.0, equal to the version the Lightbringer MCP service reports in serverInfo.version; workflow plugin packages are versioned separately. Repository releases, MCP registry publication and host-directory publication are separate steps. See the release and compatibility guide for verification scope and publication steps.

This is a metadata and documentation repository for a remote, hosted MCP server. Lightbringer operates the server; there is no server code to install or run from this repository.

What you can do

Capture innovations where you work. Identify ideas from an inventor conversation or authorised technical sources. Search for existing records, register new innovations, and enrich them over time without creating duplicates.
Use portfolio and strategy context. Retrieve accessible records and strategy reports to guide exploration. Dedicated IP-strategy editing and trade-secret classification tools are not currently available; use the platform or continue with the Lightbringer team when needed.
Refine an innovation description. Start automated feedback, follow its progress and read the findings. This checks the description rather than establishing novelty or patentability.
Request patent preparation. Ask Lightbringer to prepare a selected innovation for patent filing. Registration alone does not initiate this workflow. An explicit preparation request does not require an automated feedback or revision cycle first.
Collaborate with your patent team. Read reviews, attorney comments and proposed amendments; add comments, reply in discussions and respond to reviews using your existing permissions.

MCP access is available to Lightbringer platform subscribers, free or paid. Professional work is provided through separate paid engagements. The tools below define what can be initiated or consumed directly through MCP today; other service arrangements continue through the platform or Lightbringer team, including meetings where relevant. Agents cannot make payments.

Connect and get started

Use a compatible MCP client such as ChatGPT, Claude, Claude Code or Cursor. Support for installing bundled skills varies by host; a connection to the MCP endpoint alone does not install skills.

Setting	Value
Endpoint	`https://mcp.lightbringer.com/mcp`
Transport	Streamable HTTP
Auth	OAuth 2.1 (Authorization Code + PKCE, S256), with Dynamic Client Registration
Scopes	`mcp:read`, `mcp:write`

The server advertises its authorization server through RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource. Complete the host's sign-in flow and select the Lightbringer organisation to connect. Access is limited to that organisation and your existing permissions. Eligible users can enable MCP for an organisation during consent; other members can connect when MCP is already enabled. Follow the account or organisation remedy shown if connection is blocked. Never paste passwords or access tokens into chat.

Install the skills with the connector

The MCP server supplies available tools, schemas and general service instructions. Skills guide the assistant through a workflow using those tools; they do not grant additional permissions or add server capabilities.

Skill	How it uses MCP
`innovation-capture`	Explore authorised context, search for related innovations, register or update records, and optionally start automated feedback and follow its task.
`patent-preparation`	Resolve the selected innovation, preserve the user's explicit patenting intent, request preparation and explain the actual outcome.
`patent-review`	Read review artifacts, prepare sourced feedback, and post authorised comments or review responses.

agent-plugin is the canonical skills package. claude-plugin mirrors its complete skills tree with Claude-specific metadata. These are separate distribution packages for the same service. See the distribution guide for supported installation routes, release dependencies and host verification. A repository or registry listing does not itself establish approval or availability in a host's plugin directory.

After connecting and installing the matching skills, try:

Use Lightbringer's innovation-capture skill to identify potential innovations in the technical work we have discussed. Search for existing records, register new innovations and enrich relevant existing ones using supported facts. Preserve open questions and report anything that could not be saved. Do not request patent preparation; registration is the goal for now.

For a separate preparation request: “I want Lightbringer to prepare innovation X for patent filing.” For review work: “Help me respond to the patent team's review of X.”

Connect an MCP client directly

For clients accepting this configuration format:

{
  "mcpServers": {
    "lightbringer": {
      "type": "streamable-http",
      "url": "https://mcp.lightbringer.com/mcp"
    }
  }
}

Other hosts use their own connector UI or transport label; follow the matching plugin package. General guidance is available through MCP when the workflow skills are not installed.

Tools

The full production catalog verified on 2026-09-15 contains 20 tools: 9 annotated read-only and 11 annotated non-read-only. The table uses readOnlyHint, not OAuth scope. Actual availability depends on consented scopes and configuration; without the optional developer-feedback delivery channel, there are 19 tools: 9 read-only and 10 non-read-only. Clients should discover their available tools through tools/list.

Tool	Type	Purpose
`whoami`	read	Identify the connected user and organisation.
`search`	read	Find accessible innovation and document context.
`fetch`	read	Retrieve a record or document found through search.
`list_innovations`	read	Find existing innovations.
`get_innovation`	read	Read an innovation's current content.
`get_innovation_template`	read	Retrieve the structured registration template.
`list_reviews`	read	Locate report and patent-draft reviews.
`get_review`	read	Read review documents, comments and discussion.
`list_tasks`	read	Recover owned task IDs and recorded status in the connected organisation; optional innovation filter and pagination.
`delete_task`	write	Delete an owned task and cached findings in any state, without cancelling execution.
`register_innovation`	write	Validate and save an innovation in one request.
`update_innovation`	write	Replace selected sections of an existing innovation.
`request_patent_preparation`	write	Request Lightbringer's patent-preparation workflow.
`start_innovation_feedback`	write¹	Dispatch automated description analysis and return a task.
`get_task_status`	write¹	Refresh an automated feedback task using its `task_id` and save its status and available findings.
`respond_to_review`	write	Record an approve/request-changes response.
`add_comment`	write	Add a comment anchored to a review document passage.
`reply_to_comment`	write	Reply to an existing comment thread.
`add_discussion_comment`	write	Add a general review discussion comment.
`send_developer_feedback`	write²	Report tool problems or missing capabilities to Lightbringer.

¹ Both tools are available under read consent and annotated non-read-only: start_innovation_feedback dispatches background analysis; get_task_status refreshes active analyses and saves their status and available findings. Neither edits the innovation description.

² Available under read consent when developer feedback is enabled. Sends tool feedback to the Lightbringer engineering team.

The following tools carry destructiveHint: true: delete_task, update_innovation, request_patent_preparation, respond_to_review, add_comment, reply_to_comment, add_discussion_comment, and send_developer_feedback. Other tools advertise destructiveHint: false. All tools advertise openWorldHint: false. Preparation and review actions can still send email or in-app notifications, and developer feedback is sent to Lightbringer's engineering team. Annotations describe behavior; they do not grant access.

Registration, automated tasks and professional requests

Registration saves a record. register_innovation validates before saving. Validation errors mean nothing was registered; success returns the saved ID/link and any non-blocking warnings. Warnings do not mean registration failed. There is no separate MCP validation tool. Incomplete ideas that cannot satisfy the schema should remain explicitly pending registration rather than being filled with invented details.

Automated feedback returns a task. start_innovation_feedback returns one task_id for the complete feedback run, plus status, progress and per-analysis results. Use that same ID with get_task_status. Continue while queued or running; stop at succeeded, partially_succeeded or failed. Report successful findings alongside individual failures. The initial call returns after dispatch by default; ending a wait does not cancel the analysis.

Patent preparation is a professional service request. request_patent_preparation returns an innovation ID/link and outcome: requested | already_requested. It returns no task ID. The outcome confirms a new or existing preparation request, not completed preparation, a paid engagement, email delivery or a patent filing. get_task_status does not track preparation requests. Professional-service milestone tracking is not currently exposed through a dedicated MCP tool.

The four user-invoked MCP prompts are draft-invention-disclosure, start-innovation-feedback, request-patent-preparation and summarize-my-reviews. These are server-provided starting templates; the three plugin skills provide fuller workflow guidance.

Tasks and findings expire 30 days after creation; reading does not consume them or extend retention. Use list_tasks, optionally filtered by invention_id, to recover a lost task ID in the connected organisation. Follow next_cursor even if access filtering returns an empty page; listing reports recorded status without polling. delete_task permanently removes the user’s task and findings when requested, in any execution state, with write consent. Deletion does not cancel the analysis, delete the innovation or withdraw a service request.

Registry and related repositories

The connector's MCP registry identity is com.lightbringer/connector. server.json describes this remote connector; it does not bundle the workflow skills. Its version equals the version the Lightbringer MCP service reports in serverInfo.version on initialize: the registry schema defines the field as the equivalent of the MCP Implementation.version. Plugin packages are versioned separately. Connector metadata 4.9.0 was published to the registry on 2026-09-22 and verified as the latest entry. Publishing is a separate step after a repository release; a merge here does not update the registry.

Lightbringer

Links

README