Modaic MCP server
The Modaic MCP server connects MCP clients to the API over HTTPS using Streamable HTTP.
Set up
Create a Modaic API key with the scopes needed for your work. Configure your MCP client with the server URL and a bearer authorization header. For example, a client that supports remote MCP server configuration can use:
{
"mcpServers": {
"modaic": {
"url": "https://modaic.dev/api/v1/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Store the key securely using your client's secret management where available. Connect and ask the client to list the Modaic tools. Tool calls can create, change, or delete data and can incur usage charges. Review actions in your client before approving them.
Use tools
Each tool corresponds to an endpoint in the API reference. Tool names describe the operation, such as list_models and run_inference. Supply API path values in path, query parameters in query, and JSON request fields in body, using the field names in the API reference. Use an empty object for path when the endpoint has no path parameters. The optional idempotencyKey sets the Idempotency-Key header.
Responses include the HTTP status, content type, encoding, and body. Binary responses are base64 encoded. A redirect is returned as a location rather than followed; never send your Modaic API key to a download or upload URL. Responses over 5 MB are rejected. For large files, use the API's upload and download workflows directly.
The server currently supports API keys. OAuth sign-in is not yet available.