Skip to main content
Any client that speaks MCP over Streamable HTTP can connect to storekit. If yours is not covered by a dedicated guide — Windsurf, Zed, Gemini CLI, an agent framework, your own code — this page has what you need.

​
What to Enter

Clients that support SSE only, or stdio only, cannot connect directly. Most of them can go through a small bridge such as mcp-remote; check your client’s documentation for “remote MCP servers”.

​
Sign In With OAuth

1

Add the server by URL

Enter the URL above wherever your client lists MCP servers. Do not enter a client ID or secret; storekit supports dynamic client registration, so the client registers itself.
2

Follow the sign-in

When your client first calls the server it receives a 401 with a WWW-Authenticate header pointing at storekit’s OAuth metadata, and starts the sign-in flow.Your browser opens the storekit dashboard. Sign in with your usual storekit email and password if you are not already signed in. You briefly see Connecting your MCP client, please wait… and are then sent back to your assistant.
The assistant is connected to the account of the user who signed in. If you belong to more than one storekit account, it uses your first account. There is no account picker during sign-in.

​
Ask Your First Question

Ask your assistant:
The assistant lists your stores by name, with their timezone and currency. If it does, you are connected. Try a second question — “How many orders did we take yesterday?” — then head to What You Can Ask.
If the assistant says it cannot reach storekit or asks you to sign in again, see Troubleshooting.

​
Check the Server From a Terminal

This is useful when a client refuses to connect and you want to rule storekit out:
A healthy server answers 401 Unauthorized with a WWW-Authenticate header that points at its OAuth metadata — that is exactly what a client sees before it signs in. Anything else (a timeout, a 5xx) is a storekit problem: email mcp@storekit.com. Developers can find the full protocol details under Merchant MCP.