AI & MCP

Choose your client

https://mcp.stg.deltavelocity.in/mcp

claude mcp add --transport http deltavelocity https://mcp.stg.deltavelocity.in/mcp
claude mcp login deltavelocity

codex mcp add deltavelocity --url https://mcp.stg.deltavelocity.in/mcp
codex mcp login deltavelocity

https://mcp.stg.deltavelocity.in/mcp

{
  "mcpServers": {
    "deltavelocity": { "url": "https://mcp.stg.deltavelocity.in/mcp" }
  }
}

{
  "mcpServers": {
    "deltavelocity": { "serverUrl": "https://mcp.stg.deltavelocity.in/mcp" }
  }
}

{
  "mcp": {
    "deltavelocity": {
      "type": "remote",
      "url": "https://mcp.stg.deltavelocity.in/mcp"
    }
  }
}

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.

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.

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

If a connection is unavailable, check that you are using the correct environment and contact support. For interactive clients, use browser sign-in instead of pasting API credentials.

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.

Write confirmation safeguards

Where enabled, shipment cancellation requires a fresh preview and an explicit YES to the exact operation. Discover the enabled capabilities and their current descriptions before acting. Authorization and shipment state are checked again after YES.

The confirmation questionnaire uses form elicitation in negotiated 2026-07-28 MRTR sessions. Legacy 2025 stateless sessions cannot elicit this confirmation and fail closed with confirmation_unsupported. General elicitation support does not establish compatibility with this exact flow: Codex and desktop Cursor remain untested for it; Grok Build is unverified.

For supported shipments, shipments.cancel performs only the exact previewed courier/channel fulfillment effects. Where safe ownership and quantity evidence exists, Shopify shipment cancellation cancels only the Shopify Fulfillments listed in the fresh preview after YES. We do not send separate fulfillment-order cancellation requests. Shopify can adjust/create fulfillment orders for the cancelled items so they can be fulfilled again. Parent order and sibling fulfillments are not cancellation targets. Shopify documents these automatic effects at https://shopify.dev/docs/api/admin-graphql/2026-04/mutations/fulfillmentCancel. Missing, ambiguous or historical unmapped fulfillment ownership is blocked with confirmation_scope_unsupported. Changed fulfillment mappings require a fresh preview and approval. Parent Shopify order cancellation is unavailable. Review shipment IDs, courier, channel and all fulfillment effects before YES. A shipment waiting in OutForDelivery is refused. There is no local force, RTO or rebooking fallback.

Business result contract

Where enabled, business Python accepts actual source business data and exact source record field projections. Derived output uses only metrics and tables, with at least one entry and no extra keys. A metric has a short identifier name, a finite numeric value and sources containing zero-based provenance indices of successful business calls. Optional unit is one of count, percent, ratio, INR, kg, grams, cm3, days, hours, minutes or seconds; optional dimensions must match fields from one coherent actual source row. A table has source (the provenance index of one successful business call) and rows containing exact source record field projections. docs.* capabilities, search and describe calls cannot be business evidence; docs.* reads still occupy a provenance position but cannot be cited.

For example, after a successful business call at provenance index 0, a derived numeric metric can be returned as {"metrics":[{"name":"cod_share_percent","value":25,"sources":[0],"unit":"percent"}]}. The example value is illustrative; compute it from the actual returned data. Free-form conclusions and invented source values are rejected. Public stdout is empty; printing is not a result channel.

Provenance is owned by the host and lists every successful capability call in order, including docs.* reads; source indices refer to these positions. Shape and provenance checks do not prove numeric honesty or immunity to misleading semantics. Inspect the source data before using a derived value for a decision. Documentation answers identify the pinned guide revision and artifact hashes; website publication may be newer than the backend bundle.