Remote MCP · live
Connect TryDrobe’s virtual try-on MCP server to your coding agent. Codex, Claude Code, and other Streamable HTTP clients can create virtual clothing try-ons with secure, expiring account keys and the same credit balance you already use in TryDrobe.
Tool call
create_virtual_try_on
personImageUrl: https://…/person.jpg
garmentImageUrl: https://…/jacket.jpg
idempotencyKey: look-2026-08-03
Definition / 01
A virtual try-on MCP server exposes clothing try-on capabilities as typed Model Context Protocol tools. Instead of writing a custom REST integration, an MCP-compatible client discovers the available tools, understands their inputs, and calls them during a task. TryDrobe provides account usage, try-on creation, and job status tools over one remote Streamable HTTP endpoint.
Connection / 02
The server URL is always https://trydrobe.com/mcp. Keep the API key in an environment variable, then use the matching client configuration below.
Open MCP / API in the TryDrobe dashboard, name the key, and choose a 30-day or 90-day expiry.
Set TRYDROBE_API_KEY in your shell or secret manager. Do not commit the td_mcp_ key to source control.
Point the client to https://trydrobe.com/mcp and source the Authorization bearer token from the environment.
Provide public HTTPS links for the person photo and garment image. The client can call the typed tools and return the result.
Client / Codex
Codex supports remote Streamable HTTP MCP servers with bearer-token authentication. Add this table to ~/.codex/config.toml, set TRYDROBE_API_KEY in the environment that launches Codex, and restart the client.
Codex CLI, the IDE extension, and the Codex desktop app share MCP configuration for the same Codex host. Use /mcp or the MCP settings screen to confirm the server is connected.
[mcp_servers.trydrobe]
url = "https://trydrobe.com/mcp"
bearer_token_env_var = "TRYDROBE_API_KEY"Client / Claude Code
Claude Code supports remote HTTP MCP servers and expands environment variables inside.mcp.json. The shared file can contain the configuration below without containing the secret itself.
Set TRYDROBE_API_KEY before opening Claude Code. Project-scoped MCP files require approval when Claude Code first discovers them. Use /mcpor claude mcp get trydrobe to inspect the connection.
{
"mcpServers": {
"trydrobe": {
"type": "http",
"url": "https://trydrobe.com/mcp",
"headers": {
"Authorization": "Bearer ${TRYDROBE_API_KEY}"
}
}
}
}Tool registry / 03
The server exposes three focused tools. Each returns structured content so an MCP client can reason about credits, job state, errors, and result URLs without scraping text.
Check the account credit balance, estimated try-ons remaining, recent MCP usage, and current limits.
Submit public HTTPS person and garment image URLs to create a virtual clothing try-on for 2 account credits.
Check a job by ID and receive a fresh, expiring signed result URL after generation succeeds.
Choose the right integration
| Integration | Authentication | Billing | Best for |
|---|---|---|---|
| TryDrobe MCP | Expiring account API key | 2 shared credits per try-on | Codex, Claude Code, and persistent MCP clients |
| Stripe MPP API | Payment authorization per request | $0.35 per paid request | Anonymous shopping agents and commerce automation |
Security / 04
MCP calls use the same account-level privacy boundary as the TryDrobe app. Keys are shown once, stored only as hashes, and can be revoked from the dashboard at any time.
Choose an automatic expiry when the key is created.
Separate Codex, Claude Code, and automation credentials.
Per-key creation limit protects account credits.
Account concurrency limit prevents runaway generation.
Results stay under the authenticated user’s storage namespace.
Person and garment URLs are not persisted in the MCP job table.
FAQ / 05
A virtual try-on MCP server exposes clothing try-on actions as typed Model Context Protocol tools. An MCP client such as Codex or Claude Code can discover those tools, submit person and garment image URLs, check usage, and retrieve the generated result.
Yes. Add the TryDrobe Streamable HTTP endpoint to Codex config.toml and provide an expiring TryDrobe API key through the TRYDROBE_API_KEY environment variable. Codex can then use the TryDrobe MCP tools during a task.
Yes. Claude Code supports remote HTTP MCP servers and environment-variable expansion in .mcp.json. Add the TryDrobe endpoint and send TRYDROBE_API_KEY as a bearer token in the Authorization header.
A successful TryDrobe MCP virtual try-on costs 2 account credits. Web, mobile, and MCP usage share the same credit balance. Failed generation or storage attempts are refunded automatically.
The MCP job record does not persist the input person or garment image URLs. Generated results are stored in the authenticated user’s private storage path and are returned through expiring signed URLs.
The MCP server uses an authenticated TryDrobe account and its shared credit balance. The separate agent API is anonymous and charges each request through Stripe Machine Payments Protocol, so it does not use account API keys or credits.
Ready to connect
Create an expiring API key, connect the remote MCP endpoint, and use your existing TryDrobe credits from Codex or Claude Code.