MeduxMedux
Overview / MCP / Bionic

Use Medux MCP in Bionic

Add the Medux-hosted remote MCP server to Bionic (LM Studio), verify it, and call Medux media tools from your agent.

Browse API Reference
Setup guides by agent
Claude CodeCodexCursorGitHub CopilotVisual Studio CodeOpenCodeMistral VibeDevin DesktopCommand CodeBionic

How to start

1

Sign in and get your Medux API key. It looks like sk-medux-... — copy it once and store it safely.

2

Open your Code Project in Bionic and add Medux as a remote MCP server in the app's MCP settings, using the endpoint below and an Authorization header. LM Studio uses Cursor-style mcp.json notation, so the entry looks like this.

{ "mcpServers": { "medux": { "url": "https://mcp.medux.io/api/mcp/v1", "headers": { "Authorization": "Bearer sk-medux-..." } } } }

The menu labels can differ between Bionic versions. If the app offers an Edit mcp.json option, paste the entry above there; otherwise add a remote server and enter the endpoint and header by hand. The key is stored in plain text, so keep the file private.

3

Verify the connection. Confirm medux appears in Bionic's MCP server list with its medux_* tools, then run a prompt that needs a Medux tool. If it fails, remove and re-add the server.

4

Use it from a prompt. Start Bionic in the folder that holds your files and mention Medux so it picks the right tool.

Use Medux to generate a 1024x1024 image of a red fox in watercolor style.
5

How a call works: Bionic chooses a medux_* tool and fills in its parameters. For a local file it first calls medux_file_create_upload_url, uploads the file to the returned upload_url with an HTTP PUT (using the returned content_type), then passes the file_id to the tool. Most tools run as async tasks, so it polls medux_task_query with the task_id until the result URL is ready.

6

To find the exact tool for a capability, open Playground, switch to For AI Agents, and read the MCP tab for its mcp_tool_id.

What this means

  • Server not connecting: confirm the URL is exactly the endpoint above, including /api/mcp/v1.
  • 401 Unauthorized: the key is missing or wrong. Re-copy it and keep the Bearer prefix.
  • Remote servers blocked: check that remote MCP is allowed in the app's settings.
  • Local-file upload fails: upload URLs expire. Ask the agent to request a new one and send the exact content_type it returns.
  • Insufficient credits: top up or upgrade on the Pricing page. MCP calls use the same credits as the public API.