DeltaVelocity

AI & MCP

MCP preview — connections are not yet enabled.

Staging preview · https://mcp.stg.deltavelocity.in/mcp

One connection, your choice of client

Connect your AI client to DeltaVelocity over Streamable HTTP at https://mcp.stg.deltavelocity.in/mcp. Your client supplies the model. Monty runs server-side: there is nothing to install for Monty.

Once enabled, add the URL in your client, start Connect or Login, and sign in to DeltaVelocity in your browser as a brand administrator. Review the application, callback, brand and requested permissions before approving. Return to the client to finish connecting.

Interactive clients use OAuth authorization code with S256 PKCE and rotating refresh tokens. Do not paste API keys, client secrets or bearer tokens into these setups. The client handles token refresh; a connection expires after 30 days even when it is refreshed. Sign in again after expiry or revocation.

Choose your client

Claude Code

  1. Add the remote HTTP server with the command below.
  2. Run claude mcp login deltavelocity, or open /mcp in Claude Code and authenticate. Complete the browser consent flow.
claude mcp add --transport http deltavelocity https://mcp.stg.deltavelocity.in/mcp
claude mcp login deltavelocity

Vendor documents remote HTTP OAuth and token renewal.

Official Claude Code documentation

Claude Desktop

  1. Open connector settings and add a custom remote connector using the URL below, where your plan and organization allow it.
  2. Choose Connect and finish browser sign-in and consent. Use the remote connector flow; no local server configuration is needed.
https://mcp.stg.deltavelocity.in/mcp

Vendor documents remote connectors with browser sign-in.

Official Claude Desktop documentation

Codex CLI

  1. Add the server, then log in using the commands below.
  2. Finish browser sign-in and consent, then return to Codex.
codex mcp add deltavelocity --url https://mcp.stg.deltavelocity.in/mcp
codex mcp login deltavelocity

Vendor documents remote MCP servers with browser sign-in.

Official Codex CLI documentation

Codex Desktop

  1. Use the app’s MCP settings to add a remote HTTP server with the URL below and start its login flow.
  2. Complete browser sign-in and consent. Consult the vendor’s setup documentation for the settings available in your app version.
https://mcp.stg.deltavelocity.in/mcp

Vendor documents remote MCP integration in Codex.

Official Codex Desktop documentation

Cursor

  1. Add this remote server to your Cursor mcp.json configuration.
  2. Use the server’s OAuth connection action and complete browser sign-in and consent.
{
  "mcpServers": {
    "deltavelocity": { "url": "https://mcp.stg.deltavelocity.in/mcp" }
  }
}

Vendor documents automatic OAuth for remote servers.

Official Cursor documentation

Antigravity

  1. Add the remote server using serverUrl in your MCP configuration.
  2. Start the automatic OAuth connection flow and complete browser consent. If the client requests a code handoff, follow its instructions; do not paste an API secret.
{
  "mcpServers": {
    "deltavelocity": { "serverUrl": "https://mcp.stg.deltavelocity.in/mcp" }
  }
}

Vendor documents automatic OAuth registration and token renewal.

Official Antigravity documentation

Devin

  1. In MCP settings, add an HTTP server using the URL below, select OAuth and choose Connect.
  2. Complete browser sign-in and consent. Use personal access for an individual connection where available.
https://mcp.stg.deltavelocity.in/mcp

Vendor documents HTTP servers with OAuth. Use a personal connection where available.

Official Devin documentation

OpenCode

  1. Add this remote server to your OpenCode configuration.
  2. Run opencode mcp auth deltavelocity and complete browser sign-in and consent.
{
  "mcp": {
    "deltavelocity": {
      "type": "remote",
      "url": "https://mcp.stg.deltavelocity.in/mcp"
    }
  }
}

Vendor documents automatic OAuth registration for remote servers.

Official OpenCode documentation

Permissions and ownership

Consent grants access to the signed-in brand and the permissions shown on the consent screen. Approve only the access you need. A connection cannot expand your current authority; disabling a user or brand, changing role or revoking the connection removes access.

Reading documentation does not grant permission to execute an operation. Discover the available tools, search for a capability and describe the operation before using it. Write operations require the corresponding scope and enabled backend write feature.

Analytics requires analytics:read; COD analytics also requires wallet:read. Billing reads and stored freight analytics require billing:read as applicable. Availability depends on your approved scopes and the enabled backend capabilities.

Manage or revoke connections in Dashboard → Settings → Developer → Connected apps. Removing a server from a client alone is not a substitute for revoking its DV connection.

Try a focused request

Ask: ‘Find the documentation for booking an order and explain the required fields.’

With the relevant read permission, ask: ‘Show the tracking status of shipment <shipment ID> for my brand.’

Before a write, ask the client to describe the operation and show the exact changes for your confirmation. Review IDs and effects before approving a shipment, cancellation or other write.

Troubleshooting and environments

Connections are not available during this preview. Check back for availability; API credentials cannot enable a connection.

If login loops, check that your client supports remote HTTP OAuth, finish the browser callback and confirm you signed in as a brand administrator. Client versions, plans and organization policies can affect connector availability.

A 401 can mean an expired, revoked, wrong-resource or wrong-environment token. Reconnect through browser sign-in. If refresh returns invalid_grant, sign in again rather than retrying an old refresh token. A 403 means the operation is not permitted; check scopes and current access instead of repeatedly retrying.

Use https://mcp.stg.deltavelocity.in/mcp for this environment. Production uses https://mcp.deltavelocity.in/mcp; staging uses https://mcp.stg.deltavelocity.in/mcp. Keep each connection in its own environment, use the exact resource URL without a trailing slash and do not substitute an API hostname. MCP tokens do not authenticate ordinary REST or dashboard requests.

These setup instructions follow vendor documentation. Available features depend on your client version, plan and organization policies. MCP connections to DeltaVelocity are not yet enabled.