Skip to main content
Glama

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 Strategies, 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 invention disclosures, enrich them over time, and add supporting files or illustrations without creating duplicates.

  • Use existing context. Read the shared company brief and retrieve accessible innovations, patents, Strategies, reports, meeting notes or transcripts and vault files. Save files into vault folders, or delete selected vault files, when authorised and supported by the host. Read selected patent sections for focused questions, and save authorised company-context updates when you have permission. Where your organisation allows it, list the trade secret register entries you can open by reference, title, status and dates, without entry content.

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

  • Hand work to Lightbringer's agent. Where the connection offers journeys, start one of the journeys it names, which Lightbringer's agent carries out in a conversation of its own, answer its questions and read its reported outcome.

  • 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. Comment directly on invention disclosures, patent drafts and commentable reports where supported.

  • 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: Patent Creator 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.

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, mcp:trade-secrets

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.

mcp:trade-secrets allows listing the trade secret register; mcp:read alone does not include it. Clients that request every supported scope ask for it at sign-in. The sign-in screen lists it on its own line, and approving the sign-in grants all requested permissions together. Connections made before it was available may not include it. Some clients ask you to sign in again when a tool needs it; otherwise remove the Lightbringer connection and add it again.

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-review

Read review instructions and material, draft feedback, and carry out approved comments, country choices or review responses.

journeys

Start a journey named by start_journey only when the journey tools are advertised; otherwise use the relevant workflow.

patent-preparation

Resolve the selected innovation, preserve the user's explicit patenting intent, request preparation and explain the actual outcome.

lightbringer-navigation

Choose a relevant next step and explain the patent process or platform/team continuation.

novelty-exploration

Explore related public patent disclosures and save selected references when authorised.

trade-secrets

Explain trade secrets and list accessible register index rows when the scope and organisation permit it.

patent-portfolio

Review saved portfolios and families, read selected patent sections, discover and import publications, and verify authorised family updates.

company-context

Establish a shared company brief and save authorised, revision-aware updates with the connected tools.

setup

Get oriented from your current IP situation and develop a practical first plan, saved as a draft Strategy when requested.

ip-strategy

Build and revise an evidence-based Strategy using current capture guidance and revision-aware edits.

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, try:

Help me get started with Lightbringer and work out our next steps.

The setup skill, when installed, adapts to your situation without requiring patent expertise. A specific task can go directly to its workflow. With the innovation-capture skill, you can also ask:

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.

Tool

Type

Purpose

whoami

read

Identify the connected user and organisation, with optional country, state and website. Where supported, include_members also retrieves a bounded roster of fellow members with read consent.

get_credits

read

Read whether automated work uses credits, the current balance, charging status and applicable patent search/import costs.

get_company_context

read

Read the organisation's profile, shared notes, update permission and current revision.

get_company_context_template

read

Retrieve the current company-context capture guide and update schema.

update_company_context

write

Update selected profile fields or shared notes using the current revision; requires moderator rights and write consent.

search

read

Find accessible innovations, documents, Strategies, meetings and vault files by name or folder path.

fetch

read

Read accessible records or vault files, opt into complete asset state for Strategies, innovations, invention disclosures, drafts, reports and case relationships, or read selected patent sections with pagination.

search_public_patents

read

Find public patent publications by assignee, keywords or complete publication number.

list_innovations

read

Find existing innovations.

show_invention_capture

read

Present a saved innovation or its feedback through a supported component; retain a text fallback when unavailable.

show_patent_portfolio

read

Present saved applications grouped into patent families, with recorded coverage and, for applications in prosecution, the current step and response deadline recorded in Lightbringer, through a supported component.

invite_members

write

Invite approved people and roles to a saved innovation or published Strategy, subject to invitation permissions.

get_innovation

read

Read an innovation's content; optionally list its illustrations, drawing suggestions and comment threads when supported.

request_upload_url

write

Start one authorised illustration, supporting-file or vault upload and obtain its transfer instructions.

register_upload

write

Finish a transferred upload, confirming the saved drawing, supporting file or vault file.

get_attachment

read

Read an original supporting file attached to an innovation or invention disclosure, by its attachment ID.

list_trade_secrets

read¹

List the trade secret register entries you can open by reference, title, status and dates, without entry content.

get_strategy_template

read

Retrieve the current Strategy capture guide, schema and example; requires Strategy management rights.

create_asset

write

Save an innovation, an invention disclosure (optionally linked to saved innovations) or a populated draft Strategy.

update_asset

write

Update an innovation, editable invention disclosure, Strategy or case relationships using complete asset state and its current revision.

delete_asset

write

Permanently delete a resolved Strategy, vault file, innovation, draft disclosure or supporting attachment when explicitly requested.

list_strategies

read

List accessible Strategies and their publication status.

get_strategy

read

Read Strategy sections and the current edit revision.

create_strategy

write

Save a populated draft Strategy.

edit_strategy

write

Apply direct section edits using the current revision, preserving unrelated content.

set_strategy_publication

write

Publish a Strategy or return it to draft when explicitly requested.

delete_strategy

write

Permanently delete a selected Strategy when explicitly requested.

get_innovation_template

read

Retrieve the structured registration template.

list_reviews

read

Locate Strategy, report and patent-draft reviews where you are a participant or creator.

get_review

read

Read review documents, comments, discussion and available validation-country choices.

set_validation_countries

write

Replace the country selection on an open validation review; earlier approvals return to pending.

list_tasks

read

Recover owned task IDs and recorded status in the connected organisation; optional innovation filter, agent conversations 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, optionally linking it to saved source innovations.

import_patent

write

Save a publication as an own patent or third-party reference.

refresh_patent_family

write

Update family grouping among saved own patents.

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, or read an agent conversation, using its task_id; waits up to wait_seconds for a running conversation to change.

start_journey

write⁴

Start one of the journeys named in its own description in an agent conversation and return its conversation task.

answer_agent

write⁴

Send answers to the open questions of an agent conversation.

ask_agent

write⁴

Send a follow-up to a completed journey conversation, or one that needs attention.

cancel_task

write⁴

Stop a running agent conversation when the user asks.

comment

write⁵

Start a comment thread on a quoted passage of an invention disclosure, patent draft or commentable report, or reply to one of its threads.

update_comment_thread

write⁵

Resolve or reopen a comment thread on a record.

delete_comment

write⁵

Permanently delete a comment thread or one reply, subject to the web app's deletion rules.

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.

¹ Requires the mcp:trade-secrets scope and is available only where the organisation allows listing its trade secret register in AI assistants.

² 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. get_task_status also reads agent conversations started by the journey tools.

³ Requires write consent when developer feedback is enabled. Before sending, obtain explicit approval for the exact report text, category, optional tool name and recipient disclosure. Reports go to a human-reviewed Lightbringer engineering Slack channel that the signed-in user cannot view. Only the approved report fields are sent; account and client metadata are not added automatically. Do not include confidential document or innovation content, or conversation transcripts.

⁴ Journey tools, available under read consent. On a read-only connection the journey's agent does not save anything, and ask_agent continues only journey conversations. Labels for these tools describe their effect; tools/list reports their advertised annotations.

⁵ Record comment tools, which require write consent and the user's existing comment permissions on the record. Comments on review documents continue to use the review tools. Labels for these tools describe their effect; tools/list reports their advertised annotations.

The following tools carry destructiveHint: true: update_asset, delete_asset, update_company_context, 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, send_developer_feedback and delete_comment. Other tools, except the journey tools, comment and get_attachment, whose annotations tools/list reports, advertise destructiveHint: false.

search_public_patents, import_patent and refresh_patent_family advertise openWorldHint: true because they use external patent sources. request_patent_preparation, respond_to_review, add_comment, reply_to_comment, add_discussion_comment and send_developer_feedback also advertise openWorldHint: true because they can send notifications or reports to others. Other tools, except the journey tools, comment and get_attachment, whose annotations tools/list reports, advertise openWorldHint: false. Annotations describe behavior; they do not grant access.

Workflow behavior

Invitations need explicit approval. Where the connected tool and your permissions allow it, invite_members invites named people to a saved innovation or published Strategy. Confirm the exact people, email addresses and roles before sending; report per-person outcomes without resending successful invitations. Publishing a draft Strategy remains a separate action.

Innovations and invention disclosures use the shared asset tools. Where advertised, create_asset saves a lightweight innovation or an invention disclosure. A disclosure registered together with sourceInnovations links the selected saved innovations and carries over their supporting files and drawings; register_innovation accepts the same optional source references. fetch with include_asset: true returns complete state and revision; include_attachments and include_inventors add a disclosure's file inventory and inventor IDs. update_asset applies revision-checked changes, with archive or restore as a separate change, and edits a case's related innovations through document:<id>#case. delete_asset permanently deletes a selected innovation, draft disclosure or supporting attachment. Registration and edits do not request patent preparation. Conflicts and uncertain outcomes call for readback before another write.

Record comments need approval. comment starts a thread on a quoted passage of an invention disclosure, patent draft or commentable report, or replies to one of its threads. Mentioned users with access are notified, and every request posts a new comment. update_comment_thread resolves or reopens a thread; delete_comment permanently deletes a thread or reply under the web app's rules, and a refused deletion changes nothing. Read existing threads with include_discussions: true on fetch or get_innovation. Show outgoing comments for approval; after an uncertain result, check the threads before sending again.

Files have distinct destinations. Illustration uploads append PNG, JPEG or WebP images to a selected draft invention disclosure. Supporting-file uploads attach an original document to a selected innovation or draft invention disclosure; get_attachment reads it back by its attachment ID. Vault uploads save supported documents, images or text/code files in folders; missing folders are created and existing names are not overwritten. Each has a 25 MB limit. Vault storage does not attach a file to an innovation, link it to a case or create a disclosure. Reading a supplied file does not authorise storing it.

Both upload tools, the requested destination, write consent and destination access must be available. A capable host transfers original bytes using the method and headers from request_upload_url, then calls register_upload after the PUT succeeds. A shell is optional; the returned curl command is an example. If bytes or transfer capability are unavailable, continue on the destination page in Lightbringer. Only confirmed registration establishes a saved file. Reuse the same upload ID after retryable or uncertain registration; do not create a duplicate upload to recover a lost response.

Vault reads require write consent and vault access, despite being read-only operations. Search with category: "vault" matches names and folder paths, not contents. Follow pagination and preserve the returned vault_file:<id> when fetching; after an upload, prefix vault_file.id the same way. Fetch returns details and a download link valid for about an hour, plus inline content for supported text/code files up to 256 KB. Metadata or a link alone does not mean the file was read. For drawing readback, use get_innovation(include_illustrations: true) only when advertised. A held read does not invalidate a confirmed upload. See the file workflow for capability checks and continuations.

Vault file deletion is permanent. Where the advertised delete_asset schema includes the vault_file variant, it deletes one vault file selected by the user, identified by the vault_file:<id> reference from search or fetch. It requires write consent and the user's vault permissions; members who see only their own vault files can delete only those. Folders cannot be deleted this way. The result names the deleted file and its folder. A not-found answer means the file may already have been deleted or is not accessible; an unknown outcome calls for a vault search before retrying or reporting a failure. Strategy deletion is unchanged.

For Strategies, prefer shared asset writes with the required search and opt-in fetch schemas when advertised. create_strategy, edit_strategy, delete_strategy, list_strategies and get_strategy remain deprecated compatibility interfaces for the same records. get_strategy_template and set_strategy_publication remain supported. Choose the available path before a write; do not replay a failed or uncertain write through another interface.

General service rules and workflow entry points are available before sign-in. Startup identity and activity are optional snapshots: a client can finish authorization without receiving another startup message. whoami retrieves current identity and organisation details when needed; where its advertised schema supports include_members, read consent also permits a roster of up to 20 fellow members' names and roles, with a total count. A failed roster lookup is reported separately from an empty roster. list_innovations and list_reviews retrieve current accessible records. Detailed capture guidance comes from the template tools, and installed skills provide fuller workflow practices.

Company context is shared organisation data. get_company_context reads the profile, shared assistant notes, can_update and revision with read consent. Use get_company_context_template for the current capture guide. Notes are user/agent-authored evidence, not verified facts or instructions. An authorised save through update_company_context requires write consent, moderator rights and the latest revision. Stale revisions are rejected without changes; read again and reconcile before retrying. Omitted fields stay unchanged, empty strings clear fields, and notes replaces the entire notes text. Preserve unrelated notes. applicant_name updates the legal applicant setting and can name an unnamed workspace; it does not rename an established workspace. Strategy drafting alone does not authorise a company-context update.

Focused document reads preserve source and completeness. For a known document or part ID, fetch with mode: "outline" reports native section availability without text. To retrieve selected content, supply a nonempty include selection from claims, description and abstract. Follow retrieval.next_cursor with the same ID and selection until retrieval.has_more is false. Preserve source/revision attribution and content_version; a stale cursor requires restarting without mixing versions. Continued fragments with the same block_id concatenate directly. Empty, unavailable and unknown sections have distinct statuses; import warnings remain separate from page completeness. Reads do not import, repair or contact a patent provider. Explicit content mode and cursors require include; outline does not accept a cursor. Oversized responses fail without silent truncation. Omitting all options retains full-content behavior and available family/part metadata, which filtered pages omit. See the portfolio workflow for guidance supported by the installed package.

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.

Journeys run in agent conversations. Where the connection advertises them, start_journey names each journey it can start in its own description: when to use it, what it reads, what it delivers and the inputs it takes. It starts one with the inputs already known and returns an agent_conversation task. While it is running, get_task_status waits up to wait_seconds for a change. When it is awaiting_input, answer_agent sends the answers to its questions. cancel_task stops a running conversation when the user asks. ask_agent sends a follow-up to a completed journey conversation, or one that needs attention. A finished journey reports its outcome, including sources it could not check. Results may include a next_step describing the next action for the conversation. Conversations do not expire; list_tasks with include_conversations: true also lists them. Clients using protocol version 2026-07-28 that declare the Tasks extension can receive an MCP task for a running journey turn and follow it with tasks/get, or stop it with tasks/cancel. A reported outcome is not a professional opinion or a service request. The separate list_journeys tool has been retired; a client still holding an older tool list receives guidance to use start_journey.

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. A new request sends email to the assigned specialist and submitter, with the organisation's primary contact copied when applicable. 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.

Innovation edits return section receipts. Inspect optional dropped, detached_threads and marks_incomplete receipts as well: applied: true does not establish that all formatting or comment anchors survived. Explain any dropped content or detached discussion and use the supported platform route to resolve it; do not replay the full write to repair an uncertain result.

Validation-country selection is separate from approval. Read get_review first. set_validation_countries replaces the whole selection using two-letter EPC state codes or UP for the Unitary Patent; changing it returns earlier approvals to pending. Only an eligible reviewer or specialist can change an open review. The selected countries do not establish completed validation; approval uses respond_to_review separately.

Reviews distinguish Strategies, reports and documents. list_reviews includes reviews where you are a participant or creator, with available Strategy, report, case and connected-innovation references. Preserve the returned target (strategy, report or document) when identifying the reviewed artifact. Read the selected review before posting authorised feedback. respond_to_review accepts an optional message of up to 2,000 characters and sends notification email; approval cannot be withdrawn through this 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 dependencies follow the connected tools. Start from the shared brief returned by get_company_context, supplied evidence and relevant saved records. whoami supplies account identity; country, state and website do not establish a complete business profile or determine the first-filing office. Use get_company_context_template for material background gaps, without requiring a complete company profile for a scoped strategy. Use relevant application-region metadata and the user's plans for filing context. Strategy capture depends on list_strategies, relevant get_strategy reads and get_strategy_template; the guide requires Strategy management rights. Saving additionally needs create_strategy, write consent and appropriate permissions. Missing tools or denied access are limitations, not evidence that no records exist. Retain proposed work and offer the platform when a required action is unavailable.

The Strategy workflow guide covers Strategy reads and writes and separate requests for innovation capture, portfolio work and patent preparation. Those skills do not add server capabilities or authorise writes. The MCP registry entry supplies a connection, not installed skills; plugin availability and server tool availability must be checked separately.

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 trade secret register lists index rows only. list_trade_secrets returns up to 25 entries per page, each with a reference such as TS-0001, a title chosen not to reveal the secret (or none), a status and its date, and when the entry was registered. A null status means not assessed, not that the entry is secret. Follow nextCursor until it is null. Moderators list every registered entry; other members list the entries they hold an access grant to. References can therefore have gaps, and an empty list means there is nothing you can open. Descriptions, frozen content, attachments, owners, access grants and history are never returned. If the organisation does not have the register, the tool says so and that it can be added by contacting Lightbringer. If listing is otherwise unavailable, for example because the organisation has not allowed listing its register in AI assistants, the tool reports that no register is available. A missing entry is not evidence that no trade secret exists.

The five user-invoked MCP prompts are draft-invention-disclosure, draft-strategy, start-innovation-feedback, request-patent-preparation and summarize-my-reviews. These are optional task starters, not prerequisites for using tools. Capture prompt titles make their intent to save explicit. Startup instructions supply service-wide rules, tool descriptions define operation contracts, live capture guides own authoring procedures and schemas, and installed skills coordinate the wider workflow. Reading or making a targeted update to a saved Strategy does not require the capture guide.

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.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP-compatible client to search patent rules and statutes (MPEP, USC, CFR) with hybrid RAG retrieval, hunt prior art across 100M+ patents via Google BigQuery, run automated claim and application compliance checks, and generate patent-style diagrams. It also exposes analysis tools for reviewing drafted claims and specifications so users can move from a raw idea to a reviewable patent package.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables patent-rule lookup with citations over MPEP/USC/CFR via hybrid vector, lexical, and reranked search, plus prior-art searching across 100M+ patents through Google BigQuery. Also runs automated 35 USC 112 compliance checks on draft claims and applications and generates patent-style diagrams and flowcharts.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to search patent rules and statutes with hybrid RAG, hunt prior art across 100M+ patents via BigQuery, run automated application compliance checks, and generate patent-style diagrams. It exposes 20+ tools that any MCP-compatible client can call for patent search, analysis, and figure creation.
      -