Give your coding agent
the right API context.

Published OpenAI developer plugin

Open Velox TriFit Developer ↗

Use the listing's available installation flow for your account. This is the developer-guidance plugin, not an API-key entitlement or permission to generate. If you prefer direct MCP configuration in a coding client, use the public endpoint below. You do not need a local copy of the full account-connected TriFit plugin to read these docs.

Find the public MCP server

Open the official MCP Registry listing ↗

Registry version 2.0.0 was independently verified active and latest on 24 October 2026, pointing to the current unified endpoint. It supersedes the initial 1.1.0 legacy documentation endpoint. See the exact registry record and publication evidence. The identifier stays io.github.Velox-XR/velox-trifit-developer; this is not a second server or a worker-version change.

GitHub's separate curated registry onboarding is pending. The public listing request has been submitted; it is not confirmation of GitHub inclusion. You can configure the documentation endpoint directly while curation is pending.

Native Codex CLI and GitHub Copilot CLI completed all four read-only documentation tool calls against /partner/trifit/mcp on 24 October 2026 without a TriFit sign-in. VS Code UI, GitHub hosted-agent execution and authenticated try-on have not been established by these checks. Listing, client setup and search recommendations are separate checks.

Current Velox TriFit MCP endpoint

https://studio.v3lox.com/partner/trifit/mcp

Transport: Streamable HTTP. Authentication: none for public documentation. This is a protocol endpoint, not an HTML tutorial. Opening it directly in a browser is not a connection test.

The inventory checked on 24 October 2026 contains 18 tools: five public guidance tools and 13 account/guest tools require OAuth and user consent. The public tools include the four below plus get_partner_application_guide. The full connection is not a read-only server; uploads and try-ons remain subject to authentication, permissions and allowance.

• search: find relevant public documentation.
• fetch: retrieve a document by its returned ID.
• get_integration_example: retrieve a JavaScript or TypeScript integration example.
• get_partner_access_requirements: explain how to apply for your own partner access.

Codex CLI

Merge this restricted entry into your Codex MCP configuration; preserve your other servers. The local name describes the documentation task, not a separate server:

[mcp_servers.velox-trifit-docs]
url = "https://studio.v3lox.com/partner/trifit/mcp"
enabled_tools = ["search", "fetch", "get_integration_example", "get_partner_access_requirements"]

Start a new session if your client requires it, confirm the four documentation tools are available, then run the read-only test below. For client-specific configuration locations and policy controls, see OpenAI's MCP documentation.

VS Code with GitHub Copilot

Merge this into .vscode/mcp.json in your project. Keep existing entries; do not replace the whole file if it already contains other servers.

{
  "servers": {
    "velox-trifit-docs": {
      "type": "http",
      "url": "https://studio.v3lox.com/partner/trifit/mcp"
    }
  }
}

Review VS Code's server trust prompt, start the server and use the tool picker to enable only the four documentation tools listed above. This JSON alone does not enforce the selection. Do not sign in to TriFit for a documentation-only task. Availability depends on your client version, selected agent and organization policy. See VS Code's MCP setup guide.

GitHub Copilot cloud agent & code review

In your repository, an administrator can open Settings → Copilot → MCP servers and merge this configuration. A VS Code workspace file alone does not configure GitHub's hosted agent.

{
  "mcpServers": {
    "velox-trifit-docs": {
      "type": "http",
      "url": "https://studio.v3lox.com/partner/trifit/mcp",
      "tools": [
        "search",
        "fetch",
        "get_integration_example",
        "get_partner_access_requirements"
      ]
    }
  }
}

The hosted agent may invoke allowed tools autonomously. These four are read-only public documentation tools on the current endpoint; no credentials, wildcard or generation tools belong in this configuration. GitHub currently does not support OAuth-authenticated remote MCP servers here. This anonymous subset still requires hosted-client validation: CLI success is not proof of mixed-auth compatibility there. If the client rejects it, report the limitation rather than silently choosing the legacy endpoint. See GitHub's configuration and validation instructions.

Verify with a read-only task

Use the Velox TriFit developer MCP server to search for the Partner API getting-started guide, fetch the relevant documentation and explain the available SDK and backend authentication flow. Cite the source links. Do not connect an account, request a key, upload, generate or change any settings.

A successful test returns relevant documentation through MCP, with source links and no media activity. Seeing a server name in configuration is not enough. If it fails, check client policy, tool selection, network reachability and the exact endpoint; do not add a private key or enable account tools.

Next, follow the mobile integration prompt or API quickstart. Read the public integration skill as optional task guidance, not as permission to run paid operations. Generated Swift or C# code is an example, not a shipped native Velox SDK.

Documentation and package versions may differ from the deployed service. Check cited source versions and the assigned environment before live use. Search-engine indexing and agent recommendations are controlled by those providers, not guaranteed by connecting MCP.