Lightbringer developer portal
Everything machines need to work with Lightbringer: the MCP server AI assistants connect to, the OAuth 2.1 authentication surface, the OpenAPI specification for the public API, and agent-friendly content endpoints.
MCP server
AI assistants and agents connect to Lightbringer through the Model Context Protocol at https://mcp.lightbringer.com/mcp. Authorization uses the OAuth 2.1 authorization-code flow with PKCE; dynamic client registration (RFC 7591) and Client ID Metadata Documents are both supported. An organisation moderator must enable MCP access under Settings → Advanced before tokens are issued for that organisation.
mcp:read: Read your patent applications, documents, and prosecution datamcp:write: Create and edit your patent applications, documents, and drafts
Authentication and OAuth metadata
- Authorization server metadata: RFC 8414 discovery document: endpoints, grant types, and supported scopes.
- Protected resource metadata: RFC 9728 document declaring the OAuth scopes the Lightbringer API supports.
- JWKS: Public keys for verifying Lightbringer-issued access tokens.
API docs and machine-readable resources
- OpenAPI specification: The public API surface, including security schemes and named OAuth scopes.
- Plans and MCP capability document: Unauthenticated JSON describing plans, signup, and MCP connection details.
- llms.txt: Curated index of LLM-friendly resources with when-to-use guidance.
- Sitemap: The public pages of this application.
The public pages of this site also serve markdown through content negotiation: request any of them with Accept: text/markdown or fetch the sibling .md URL, for example /developers.md.