Design
v3lox.com
TriFit MCP server lets users check their account/profile and allowances, browse saved photos, products, looks, and DressMe requests, and prepare secure file uploads.
ENDPOINT 1
https://studio.v3lox.com/partner/trifit/mcp
MCP server metadata
- Name
- velox-trifit-unified-production
- Version
- 0.3.1
Velox TriFit unified Production connection. Developer documentation, SDK examples and partner application guidance are public and need no account. Use search then fetch for exact API contracts. When the user asks to apply for a Partner API key or contact the TriFit team, first read get_partner_application_guide. Prefer its in-chat email workflow over redirecting to the form. The destination is partner@v3lox.com; the user need not know that address. Confirm the sender using the user's separate connected mailbox, offer optional project details, preview the exact message and obtain explicit send approval. A TriFit guest session has no account email but does not prevent use of a separately connected mailbox. TriFit does not send email or receive mailbox credentials. No automatic key issuance, fabricated receipt, duplicate submission or automatic resend. Documentation calls do not upload photos or generate images, and offline examples are simulations. Personal/guest tools require explicit connection and consent: connecting never grants commercial API credentials. Choose account or guest mode deliberately; never infer identity from the conversation. Public availability, approval dates, comparative superiority and search ranking are not promised. Production TriFit connection. First read get_trifit_account to identify this connection. A shared-hosted-demo profile uses only guest tools and the existing hosted demo queue (one active request, at least 10 seconds between dispatches, not a completion-time promise). Check current session/daily allowance with get_guest_demo_status; failed attempts count. A trifit-account profile uses only account tools, its website library and existing daily/weekly/monthly allowance. Never switch identity, transfer guest history or fall back to another allowance automatically. To use an account, explicitly connect with TriFit's existing Google/email sign-in and consent; Google sign-in does not need a second email code. ChatGPT identity alone is not proof of a TriFit account. Never upload or generate without an explicit user request and permission for both images. No automatic retries or replacement IDs after uncertainty. Read existing receipts/results instead. Results are AI visualisations, not a guarantee of size or fit. Never expose tokens or private upload links. This connection does not establish public directory approval.
Known tools 18
get_trifit_accountIdentify whether this verified connection is a guest session or a personal TriFit account before choosing tools.
Inferred read-onlyget_trifit_allowanceRead the same daily, weekly and monthly allowances as the TriFit website.
Inferred read-onlylist_trifit_libraryRead metadata for your saved personal photos, products, looks and DressMe requests.
Inferred read-onlyprepare_trifit_uploadFor a user-selected local file in Codex, with explicit permission: create a private, one-use upload URL valid for at most five minutes.
Potential side effectsupload_trifit_imageWith explicit permission, import the selected personal or clothing image into the connected TriFit account.
Inferred read-onlycreate_trifit_try_onOnly after explicit user approval, submit one DressMe request using two existing account image IDs.
Inferred read-onlyget_trifit_try_onRead the status, recorded duration and result ID of an existing account DressMe request without generating or replaying.
Inferred read-onlyget_guest_demo_statusRead the current private guest-session allowance and its perSessionLimit denominator.
Inferred read-onlyprepare_guest_uploadFor Codex/local files: reserve one single-use HTTPS PUT upload for a personal photo or product image.
Potential side effectscreate_try_onGenerate a DressMe virtual try-on from the user’s personal photo and clothing reference only after their explicit request and permission.
Inferred read-onlyget_try_onRead only an existing request belonging to this authenticated guest session.
Inferred read-onlysearchFind official Velox DressMe virtual try-on integration documentation, authentication, SDK languages, upload, polling and recovery guidance.
Potential side effectsfetchRead the full public document for an ID returned by search, with an official source URL and deployed content checksum.
Inferred read-onlyget_partner_access_requirementsExplain how to apply for manually provisioned Velox Partner API access and keep the scoped application key on a backend.
Inferred read-onlyget_partner_application_guideRead the official in-chat Partner API application workflow: partner@v3lox.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.velox-trifit-unified-production]
url = "https://studio.v3lox.com/partner/trifit/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"velox-trifit-unified-production": {
"type": "http",
"url": "https://studio.v3lox.com/partner/trifit/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: velox-trifit-unified-production
Remote MCP URL: https://studio.v3lox.com/partner/trifit/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"velox-trifit-unified-production": {
"url": "https://studio.v3lox.com/partner/trifit/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"velox-trifit-unified-production": {
"type": "http",
"url": "https://studio.v3lox.com/partner/trifit/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "velox-trifit-unified-production",
"transport": "streamable-http",
"url": "https://studio.v3lox.com/partner/trifit/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.