Connect an AI agent to Nick with MCP
How Cursor, Claude, and other agents reach Nick over Streamable HTTP: the tools, the store API token, and what the connection will not do.
Nick exposes a Model Context Protocol server so an agent can search domains and, with a token, read orders. The endpoint is POST /api/mcp. It speaks stateless Streamable HTTP, protocol 2025-06-18, and it does not keep a session.
What the agent can call
- search_domains checks a label or a full name against the extensions Nick sells and returns availability plus the one-year price in Taka. No token is required. Each address is limited to thirty searches in ten minutes.
- connection_status says whether the call included a valid store API token. It returns no secrets and no customer records.
- list_orders and get_order need the store API token, sent as Authorization: Bearer or x-api-key. They return the same order fields the store API already shares. Passwords and payment secrets are left out.
How to connect
Create the store API token in Reseller admin, under Integrations. The same token is used for n8n. Then point the agent at the MCP URL. On the live store that is https://nick.bd/api/mcp. A desktop client may omit the Origin header. A browser Origin has to match the site, or the call is refused.
A Cursor config looks like a small JSON object: mcpServers.nick.url is the endpoint, and mcpServers.nick.headers.Authorization is Bearer followed by the token. Admin → Integrations can copy that snippet and run a handshake test.
What this connection will not do
The server never registers a domain and never takes payment. Confirming a search does not add the name to a cart. Order tools fail closed when the token is missing or wrong. If you need a registration, the customer still searches on the site, checks out, and pays.