Lightbringer API statement
Lightbringer has no general REST or GraphQL API for working with your inventions or patents. Agents do that through the MCP server. A small OpenAPI specification at app.lightbringer.com/openapi.json describes the public endpoints only: plans and pricing, and the OAuth endpoints MCP clients use. There is no SDK on npm or PyPI, and no sandbox. If you arrived here looking for an API, this page tells you what exists instead and how to integrate.
What exists
- The Lightbringer MCP server at mcp.lightbringer.com/mcp (Streamable HTTP). It uses OAuth 2.1 authorization code with PKCE (S256) and dynamic client registration, with the scopes mcp:read and mcp:write. The endpoint answers 401 with a WWW-Authenticate header until the OAuth flow is complete. Setup for each client: Lightbringer MCP guide.
- OAuth metadata: authorization server metadata (RFC 8414) and protected resource metadata (RFC 9728).
- 20 MCP tools and 4 prompts for capturing invention disclosures, getting review feedback, searching records the organisation has granted access to, requesting patent preparation and taking part in attorney reviews. The catalogue is on developer resources.
- Plugins and skills for Claude Code and other MCP hosts, listed on developer resources.
- llms.txt and documentation for agents that read before they connect.
What does not exist
No REST or GraphQL API for inventions, patents or other account data. No OpenAPI specification beyond the public plans and OAuth endpoints. No SDKs. No sandbox or test environment. No JSON error model or versioning policy for an API, because there is no API. No function-calling schema files. No markdown versions of pages through Accept headers, Link headers or bot user agents. No agent_auth identity endpoints. Nothing on this list is hidden behind a login; it does not exist.
How to integrate instead
- 1. The user signs up at app.lightbringer.com/signup and creates or joins an organisation. The platform is free to start.
- 2. An organisation moderator switches on MCP access under Settings, then Advanced. Access is scoped to that organisation.
- 3. The agent connects to the MCP server, completes the OAuth flow, and works through the tools. Submitting a disclosure sends it for review inside Lightbringer; it does not file anything. Engagement, drafting and filing are confirmed by an authorised human. Agents cannot make payments.
Questions about integration: hello@lightbringer.com.