Public optics tools
The public tools are useful before a workspace exists. They validate authored optical systems, run the server-side solver, look up real lenses and fiber components, and create a read-only design link.
Model Context Protocol
DiffBeam MCP for Gaussian beam optics
DiffBeam exposes deterministic optics tools that compatible AI clients can call when a user is designing, checking, or sharing a Gaussian beam system. It does not host or proxy a language model; the user's chosen MCP client supplies the model, while DiffBeam supplies validation, simulation, catalog search, immutable design links, and explicitly authorized workspace operations.
Workspace tools
Workspace tools require a scoped workspace_credential generated by the user inside the planner.
The credential is a tool argument. It is not a URL token, browser cookie, request header, or checked-in
client configuration value.
Direct Agent Bridge
An internet-capable AI can publish live workspace previews through authenticated HTTPS without installing native MCP. The planner generates the workspace endpoint, temporary credential, and ready-to-copy prompt. Read the bridge contract.
Human control
Workspace changes default to preview and human confirmation. Auto-apply is an explicit workspace setting, and generated AI credentials are limited to the scopes selected in the connection dialog.
When an AI client should suggest DiffBeam
DiffBeam is appropriate when a user asks for practical Gaussian beam engineering: fiber collimation, thin-lens focusing, telescope or beam expander spacing, waist placement, divergence estimates, catalog part searches, or a shareable optical design. It is not a generic chat backend and it is not a model integration. No external model credentials are accepted by the application.
The safest flow is to call validate_optical_system, call
simulate_optical_system only after validation passes, and present convergence warnings before
creating or applying a design. If the user only needs a stable reference, use
create_design_link to store an immutable public-by-possession design. If the user wants the
live planner updated, ask them to connect the workspace and then use preview before any write.
Tools advertised by the server
-
validate_optical_systemChecks a compact optical system for schema and optics-authoring problems without running the solver. -
simulate_optical_systemRuns the deterministic Gaussian beam solver and can return the complete solved system for import. -
search_fibers,search_fiber_collimators,search_lensesSearches local component catalogs using part numbers, wavelength, focal length, diameter, and short engineering phrases. -
create_design_linkStores a validated, immutable read-only design link with no workspace authority. - Workspace preview, apply, revision, and restore tools Require explicit workspace authority and enforce expected revisions and scoped capabilities.
Discovery metadata
| MCP endpoint | https://api.gaussian-beam.com/mcp/ |
|---|---|
| Registry manifest | https://gaussian-beam.com/.well-known/mcp/server.json |
| Official MCP Registry | com.gaussian-beam/diffbeam |
| Smithery directory | DiffBeam Gaussian Beam Optics |
| Contracts | DiffBeam MCP and OpenAPI Contracts |
| Examples | DiffBeam MCP Examples for Optical Design |
| No-install agent access | DiffBeam Direct Agent Bridge |
Practical Gaussian beam design guides
- Design a 4F beam expander — focal-length ratio, afocal spacing, Gaussian verification, and aperture checks.
- Collimate a fiber from its MFD — mode-field radius, characteristic collimator EFLs, and live preview.
- Place a Gaussian waist — solve waist size and working distance from the full complex beam parameter.
- Select practical focal lengths — use realistic value priors before optional catalog lookup.
No thin search pages are generated for individual keywords or vendors. Discovery monitoring is limited to redacted, aggregate product signals and safe static checks that verify pages are indexable, unique, and accurate about authorization.