Sign Customiser now runs an MCP server. The Model Context Protocol is the standard way an AI assistant connects to software it does not own, and connecting one to your store takes a single URL: https://web.signcustomiser.com/mcp. There is no API key to create, copy or store.
Paste that URL into Claude, ChatGPT, Cursor or Codex and you are sent to a Sign Customiser consent screen. Choose the store the assistant acts for, then approve permissions written in plain language, such as View customisers and Manage pricing. A connection only ever holds the permissions you ticked, and it is bound to that one store for its whole life.
From there the assistant has 39 tools, or 44 once you approve the advanced catalogue. It can start a customiser from a sign prototype, add and reorder colours, fonts, sizes and materials, read and rewrite a pricing document, record products and orders, and pull up quotes, orders and your revenue summary.
What’s changed
- One URL to connect - No API key anywhere in the flow, on any client that supports remote MCP servers
- Permissions you approve - Named in plain language on the consent screen and checked on every call, not just at connection time
- Safe by default on writes - Every write that supports it can run as a dry run first, and deletions, order creation and product creation need an explicit confirmation
- A record you can read - Tools & Settings > MCP server lists every connected assistant, what each tool has been called for, and every change written to your store
- Revoke in one click - Immediate, and it does not need the assistant’s cooperation
Read what an assistant can do with your store, or go straight to the setup steps for each client.
