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.

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 existing context. Retrieve accessible innovations, patents, strategy reports and meeting notes or transcripts to guide your work. Trade-secret classification is not exposed through the current tools.

• Develop an IP strategy. Follow the current capture guide, save a populated draft, and revise it using the current record revision. Publication and deletion are separate explicit actions and require appropriate permissions.

• 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.

• Import portfolios and build patent families. Find public publications by company name or publication number, import your own patents or third-party references, and group saved own patents into families.

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.

Related MCP server: USPTO Patent MCP Server

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.

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.

See the release and compatibility guide for package status and verification results.

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.”

For portfolio work: “Find publications filed under these company names and import our portfolio.” For family grouping: “Group these saved patents into families.”

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 table describes each tool's purpose. Its read/write labels follow readOnlyHint, not OAuth scope. Availability depends on consented scopes, permissions and service configuration; clients should discover their available tools and schemas through tools/list.

¹ 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_strategy, edit_strategy, set_strategy_publication, 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. search_public_patents, import_patent and refresh_patent_family advertise openWorldHint: true because they use external patent sources. The other 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.

Workflow behavior

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.

Patent imports save publications. Imports distinguish your own portfolio from third-party references and return saved-record links and processing warnings. Own-patent imports automatically attempt family grouping. A targeted family refresh can add missing relationships among saved own patents; it does not import more publications, remove existing relationships, or update patent text, assets or legal status.

Saved-portfolio reviews use saved records. Paginate search across application and patent categories and use fetch for selected records. Optional family overviews describe accessible saved members, jurisdictions, recorded statuses, priority provenance and coverage limits. Group by the current groupingKey and count families, applications and recorded publications separately, without counting one family's totals for each member. Keys can change, lists can be truncated and coverage remains unverified.

A per-record family.refresh assessment checks stored references without changing records. Known missing_links can justify an authorised refresh; unresolved references require investigation. Unknown data or old/null timestamps alone do not justify refresh. Review-only requests do not authorise writes. After authorised updates, fetch affected records again to verify the resulting family; if family data is absent, report that limit. See the portfolio skill for workflow details.

Strategy creation saves a draft. Use get_strategy_template for capture and get_strategy before revision-aware edits. Replacements apply directly; conflicts require rereading and reconciliation, and edits intersecting pending review changes can be rejected. Creation and edits require Strategy management rights. Publication is a separate explicit action; multiple Strategies may be published at once. A saved Strategy does not itself import patents, request preparation or execute the actions written in it.

The five user-invoked MCP prompts are draft-invention-disclosure, draft-strategy, start-innovation-feedback, request-patent-preparation and summarize-my-reviews. These are server-provided starting templates; the 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 tracks the service's serverInfo.version, while plugin packages are versioned separately. Repository merges, registry publication and host-directory publication are separate steps. See the release and compatibility guide for version and publication status.

• Canonical skills and portable plugin

• Claude plugin and marketplace

• Homepage

• Product announcement

• Privacy policy