Connect an AI assistant

Connect your Quiver merchant account to an assistant to work with deliveries, returns, products and stock transfers.

Connections are not open yet. The Quiver connector page is live, but assistant requests currently return 503. The setup below is for use once connections open. Quiver sign-in is not available yet. The dashboard activity panel is visible; new connections remain closed.

Before you start

You need a Quiver merchant account, permission from your business to connect it, and an assistant that supports remote MCP connections. Your assistant's plan and workspace settings may affect which connections you can add.

Use this server address, including /mcp:

https://mcp.quiver.co.uk/mcp

The website at mcp.quiver.co.uk is the starting page. The address ending in /mcp is the endpoint your assistant connects to.

Set up your assistant

Connect with an API key

When connections open, assistants that accept custom request headers can use your Quiver API key. Find it in Settings → Integrations in the Quiver dashboard. Add it as the value of the x-api-key header in the assistant's secure connection settings.

Do not paste the key into a conversation or commit it to a repository. The same key may be used by your store integration, so rotating it also means updating any integration that uses it.

Claude

Add a custom connector from Claude's connector settings, name it Quiver, and enter the server address above. If your account offers request headers, add x-api-key there. A workspace owner may need to add the connector before members can use it.

Quiver sign-in is being prepared. If Claude asks for an OAuth client ID or a sign-in option that Quiver has not provided, contact us rather than guessing the settings.

See Claude's custom connector instructions for its current menus and account requirements.

ChatGPT

Custom MCP apps depend on your ChatGPT plan and administrator settings. Once Quiver sign-in is ready, an authorised workspace user can create an app with the server address above, select OAuth, complete sign-in, and scan the tools. We will add Quiver's verified sign-in settings here before this option opens.

See OpenAI's MCP app instructions for current availability and workspace controls.

Codex

For an API-key connection, add this to your personal ~/.codex/config.toml:

[mcp_servers.quiver]
url = "https://mcp.quiver.co.uk/mcp"
env_http_headers = { "x-api-key" = "QUIVER_API_KEY" }

Set QUIVER_API_KEY in the environment used to launch Codex, using your key from Quiver settings. Restart Codex after setting it. The configuration stores the environment variable name, not the key itself.

See OpenAI's MCP configuration guide.

Cursor

Add this to your personal ~/.cursor/mcp.json. Merge it with any servers already listed:

{
  "mcpServers": {
    "quiver": {
      "url": "https://mcp.quiver.co.uk/mcp",
      "headers": {
        "x-api-key": "${env:QUIVER_API_KEY}"
      }
    }
  }
}

Set QUIVER_API_KEY in the environment used to launch Cursor, then restart it. See Cursor's MCP instructions.

What you can ask it to do

Once connected, start with a lookup before asking it to change anything:

Deliveries: find and check bookings, get quotes, create or update deliveries, cancel a delivery, mark it ready for collection, and download labels.
Returns: find and check returns, arrange a return, update it, or cancel it.
Products: search your catalogue, look up products, and create or update a product.
Stock transfers: find, create, update, accept or cancel transfers.
Restock recommendations: find, create, update, accept or decline recommendations.
Locations: list your locations, look up a known location, create or update a location, or delete one.
Warehouse stock: check on-hand, reserved, available and incoming stock held at Quiver, by product ID or SKU and warehouse.
Billing: view approved receipts and invoice documents, bills and charge/refund evidence, outstanding payments, prepaid payments, account credit and masked payment details. The connector cannot issue refunds or collect payment. Refreshing account credit synchronizes Quiver's billing ledger.
Reports: read delivery-performance figures and completed stock-ledger history. Stock history uses physical inventory-item IDs, rather than SKU or product IDs.

For example: “Show me the deliveries we booked today”, “Check delivery 12345”, or “Find the product called Blue Mug”.

These tools are configured for launch. Customer connections remain closed while final connection checks are completed.

Delivery-performance figures use Quiver's fixed reporting periods and have coverage limits; they are not a custom-period on-time report. Your assistant should explain those limits and any delays plainly, then suggest useful next steps. Stock history contains completed entries only and does not support date filtering. Ask your assistant to fetch all needed pages and avoid treating partial data as a complete report.

Searches return bounded results. Delivery searches can cover longer periods when you give explicit dates. Results are paginated, with at most 100 per page; ask your assistant to fetch every required page before summarising. Dates and delivery times use London time.

Permissions and real actions

The connector uses the credential you supply to access your merchant account. It can read and change data; it is not a read-only connection and does not currently offer separate Quiver permission scopes for each tool. A shared API key gives the assistant that key's access and does not identify an individual user.

Use your assistant's tool controls to limit what it can do. Review the details before approving bookings, updates, cancellations, catalogue changes or transfers. Confirmation behaviour depends on your assistant and its settings.

Bookings use normal Quiver billing. Cancelling after a courier is on the way can leave the full charge payable. Cancellation can also notify the customer and mark a Shopify order unfulfilled again. Downloading labels updates the booking's parcel count. A quote can create or import a missing product, so it is not always a read-only action.

Usage tracking

The AI assistants section in Settings → Integrations shows the last 30 days of connector activity: apps used, people who signed in, action counts and delivery bookings. Activity appears after an assistant starts using your account.

Quiver records the merchant account, signed-in user identifier and work email where available, the app name reported by the client, the action, its outcome and duration, any delivery or return number created, and the time. API-key activity cannot be attributed to a particular person. App names are supplied by the client, so they are attribution rather than proof of identity.

Usage records are kept for 400 days. The connector does not retain the contents of requests or responses. Your assistant provider receives the information you ask it to work with under your agreement with that provider. See Quiver's privacy notice.

Ongoing monitoring

The connector responds when your assistant calls it. It does not keep watching after you close a chat. An assistant that supports scheduled tasks can make repeat checks while it has a valid connection, subject to that assistant's settings.

We plan to start persistent monitoring with delivery exceptions and overdue collections, then add warehouse stock thresholds. Those background alerts are not available yet. They need a saved schedule, an agreed notification destination and duplicate-alert controls; this guide will be updated when they are ready.

Troubleshooting

What you see	What to do
503: “Quiver MCP is not enabled yet”	Connections have not opened. Check the connector page; changing your key will not fix this.
401 or credentials rejected	Check the key in Quiver settings and the `x-api-key` header. For sign-in connections, reconnect when sign-in is available.
429 or too many requests	Wait for the indicated retry period, then ask the assistant to make fewer requests.
Invalid request or date range	Check the booking fields, use valid London dates, and request at most 100 results per page.
An action is missing	It may be disabled by Quiver or your assistant's administrator. Ask which tools the assistant can currently use.
Usage is unavailable or the panel is missing	Look in Settings → Integrations. If usage remains unavailable after refreshing your session, contact us.
A booking times out	Check your bookings before retrying. A timeout does not prove that no booking was created.

Disconnecting

Remove or disable Quiver in your assistant's settings. For an API-key connection, also remove its key configuration. If the key needs to stop working everywhere, contact Quiver to arrange rotation and update affected store integrations.

When Quiver sign-in is available, the assistant's sign-in will last up to an hour and can be renewed for up to 30 days. Removing it in the assistant may not immediately invalidate credentials already issued. If access needs cutting off, email us. Ending the person's Quiver sessions also signs them out of the dashboard; access stops within an hour.

Help

Email [email protected]. Tell us which assistant you use and the error message. Do not send your API key, password or customer details.