Amentum's Model Context Protocol server lets AI agents query ocean, atmosphere, geomagnetic, gravity, and aviation radiation data through standard tool calls. It gives agent workflows access to the same model-backed data available through Amentum's production web APIs.
Use MCP when an agent needs to choose the right environmental dataset, call the relevant tool, and return a result grounded in deterministic backend data rather than generated guesses.
Tool responses come from Amentum APIs for ocean, atmosphere, geomagnetic, gravity, and aviation radiation services.
Standard MCP clients can discover available tools, required inputs, parameter types, and structured responses.
MCP access is included with API subscription. The same API key is used for web API and MCP access.
MCP does not replace APIs. It enables agent-driven use of the same scientific services that your software can already call directly.
Architecture: User / Agent → LLM → Amentum MCP server → Amentum APIs.
Create an account in the developer portal, generate an API key, and subscribe to the services your agent needs.
Endpoint pattern:
https://mcp.amentum.io/mcp/{service}/
Available services:
ocean, atmosphere, avrad,
geomag, gravity.
Example client config:
{
"mcpServers": {
"amentum-ocean": {
"url": "https://mcp.amentum.io/mcp/ocean/",
"headers": {
"API-Key": "${AMENTUM_API_KEY}"
}
}
}
}
Input: "Plan a lower-risk route from Brisbane to Noumea for the next 48 hours."
Tools invoked: wave forecast, ocean currents, bathymetry.
Result: route notes with wave exposure, current assistance, and shallow-water warnings.
Input: "Estimate radiation exposure for SYD to LAX at cruise altitude today."
Tools invoked: aviation radiation dose along flight path.
Result: dose estimate with flight context and the model inputs used.
Input: "What is the ocean depth at 33.86 S, 151.21 E?"
Tool invoked: GEBCO bathymetry.
Result: water depth from the Amentum bathymetry API, returned as structured fields.