MCP server¶
Connect an MCP-compatible agent to https://api.gradient-dynamics.com/mcp. The server is part of the central Gradient Dynamics API service. It provides engineering operations, discovery, resources and prompts; it is not a separate solver or a local geometry installation.
The transport is stateless Streamable HTTP. Compatible clients initialize the session, send the initialized notification and use the negotiated protocol version for subsequent requests. There is no separate legacy SSE endpoint or local stdio wrapper to launch for the hosted connection.
Authentication¶
Use the client’s OAuth flow when supported/enabled, or a personal Gradient Dynamics bearer key. Retrieve the key from Studio’s Developer settings where available. Ordinary engineering tools do not require a customer model-provider key. The agent host’s model service and Gradient Dynamics compute have separate responsibilities and billing.
An illustrative manual client configuration is:
{
"mcpServers": {
"gradient-dynamics": {
"url": "https://api.gradient-dynamics.com/mcp",
"headers": {"Authorization": "Bearer YOUR_GRADIENT_API_KEY"}
}
}
}
Use the client’s secure secret mechanism where available; never commit a real key. Configuration fields vary by client. Existing connection guides cover Claude, Cursor, Codex/ChatGPT and headless workflows.
Progressive discovery¶
Use tools/list, search_tools, get_tool_schema and get_request_schema. Compact tool descriptions are an index, not a complete numerical contract. Query mesh/solver control catalogues for the task and follow pagination. Discovery is filtered by configuration and permission; execution checks access again.
Tools, resources and prompts¶
Tools initiate or inspect engineering operations. Resources include gd://guide, capability/template/model summaries where permitted, and resource templates gd://jobs/{job_id} and gd://artifacts/{artifact_id}. Use resources/list and resources/templates/list for the connected catalogue. prompts/list discovers workflow prompts with an optional engineering objective; do not put credentials in objectives.
MCP results carry structured data and error status. Follow returned job or operation IDs. Interactive geometry, mesh and result viewers open in a browser; embedded host rendering and attachment forwarding depend on the host. Static pictures supplement inspection rather than proving mesh quality or convergence.