MCP Integrations

MCP extends ChemAgent with external tool servers. Each server is discovered, loaded, and governed as an integration rather than being treated as unrestricted model access.

Integration lifecycle

1
Import
Add an approved server definition to the deployment.
2
Discover
Load the server and enumerate the tools it exposes.
3
Review
Evaluate names, arguments, side effects, authentication, and simulator scope.
4
Operate
Enable, reload, disable, and monitor the server from the management surface.

Operational status

✓
Ready or starting
The console distinguishes active integrations from those still loading.
✓
Needs authentication
Credentials or user authorization must be resolved before tool use.
✓
Failed or disabled
A failed server does not prevent unrelated approved tools from operating.

Approval boundary

Review every external capability

MCP tool descriptions are not a security boundary. Confirm the server owner, transport, credentials, inputs, outputs, and side effects before production use.