Skip to main content
If your framework already supports remote MCP, you can connect directly without installing @agentmuxer/sdk.
The examples below show the connection settings to add to an existing agent. For complete runnable examples, use the SDK guides. Check compatibility for supported integrations and runtime requirements.

Configure your framework

Read AGENTMUXER_API_KEY from your server’s environment and reject startup if it is missing:
Add this item to the Responses API’s tools array:
OpenAI receives the application key and connects to AgentMuxer. require_approval controls OpenAI’s approval step; AgentMuxer’s payment policy still applies. See OpenAI remote MCP.

Permissions and spending

These connections expose AgentMuxer’s tools, including purchases. Your framework owns model configuration, tool selection, permissions, and connection lifecycle. AgentMuxer enforces the account balance, application spending limit, and payment-confirmation policy. Before using a headless workflow, confirm that it can handle your account’s payment approval requirements. Model-provider charges are separate. Keep application keys out of browser bundles, prompts, tool arguments, and logs.

Use an SDK helper

See the OpenAI, Claude, and Vercel integration options.

Troubleshooting

Resolve authentication, tool, and purchase errors.