MCP-style integrations

Some Solarsens integrations are easiest to understand as agent or MCP-style connectivity patterns: an external client authenticates, discovers capabilities, and calls platform operations in a structured way.

When to use this model

Use this guide when documenting integrations for:

• external tools that call Solarsens APIs
• internal automation services
• AI agents or workflow engines
• clients that need a tool-like abstraction over platform capabilities

Document the integration flow

1. Explain how the client authenticates.
2. Describe the capabilities or endpoints the client can call.
3. Show the expected inputs and outputs.
4. Document common errors, retries, and permission failures.
5. Clarify any limits, latency expectations, or sequencing requirements.

Documentation standard

For every integration page, include:

• prerequisites
• auth requirements
• endpoint or capability mapping
• example request and response payloads
• error handling behavior
• notes about permissions and plant scope