Back to Directory/Media & Images

OpenMayhem

Use OpenMayhem text, embedding and media models with explicit cost controls.

Media & ImagesJavaScriptv1.0.0

OpenMayhem MCP

OpenMayhem's local stdio bridge forwards MCP messages to the hosted OpenMayhem service. It does not bundle a stale catalog: list_models and get_model read the live catalog, availability, capabilities, limits, routes, and prices from OpenMayhem. Account balance and payment logic remain on the hosted service, and the bridge contains no provider data or credentials.

Install

Download openmayhem-mcp-v1.0.0.mcpb from the v1.0.0 release and install it in an MCPB-compatible client. The client asks for a restricted OpenMayhem API key and stores it as a sensitive setting.

Clients that support remote Streamable HTTP can connect directly:

URL: https://mcp.openmayhem.ai/mcp
Header: X-OpenMayhem-API-Key: your restricted OpenMayhem API key

Create and revoke API keys at openmayhem.ai. Complete setup, tool, payment, and client instructions are at openmayhem.ai/docs/mcp.

Billing

Model discovery, request estimation, token counting, balance checks, job reads, cancellation, and owned-artifact lookup do not spend model credit. Model execution is paid. Every paid tool requires a current estimate and an explicit maximum cost.

The bridge does not calculate charges or handle payment information. Requests use the existing OpenMayhem account, balance, reservation, receipt, and settlement paths.

Requirements

  • Node.js 22 or newer
  • A restricted OpenMayhem API key
  • HTTPS access to mcp.openmayhem.ai

License

MIT

Setup from the maintainer

This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.

Package

https://github.com/Trac-Systems/openmayhem-mcp/releases/download/v1.0.0/openmayhem-mcp-v1.0.0.mcpbother

Compatible MCP Clients

OpenMayhem works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More