MCP Server

Overview

The Storepoint MCP server exposes your locator to AI assistants over the Model Context Protocol, an open standard supported by Claude, ChatGPT, Cursor, and a growing list of clients. Connect once and you can ask your assistant to:

Add, update, and delete locations. Addresses are geocoded automatically.
Create and manage custom fields: buttons, text, phone numbers, and icons
Get your embed code, ready to paste into any website
Answer questions about your location data ("how many stores are tagged flagship?")

Under the hood it calls the same Location Management API documented on this site, so changes appear on your live locator instantly.

Not a developer? The Connect Claude guide in our docs walks through the same setup with screenshots-level detail, no terminal needed.

Connect a client

Every client points at the same endpoint:

MCP endpoint

https://mcp.storepoint.co/mcp

Claude

In Claude, open Settings → Connectors → Add custom connector and paste the endpoint above. Claude opens a Storepoint sign-in page. Log in (or create an account), pick the locator you want to connect if you have more than one, and approve. That's it.

Claude Code

Add the server from your terminal, then run /mcp inside Claude Code to sign in:

terminal

claude mcp add --transport http storepoint https://mcp.storepoint.co/mcp

Prefer to skip the browser round-trip? Pass your private API key directly:

terminal

claude mcp add --transport http storepoint https://mcp.storepoint.co/mcp \
  --header "Authorization: Bearer sk_your_api_key"

ChatGPT

Open Settings → Apps & Connectors → Advanced → Developer mode, then add a connector with the endpoint above. ChatGPT runs the same Storepoint sign-in and approval flow as Claude.

Cursor & other clients

Any MCP client that supports remote servers works. For clients configured with JSON (Cursor, Claude Desktop, and most others):

mcp.json

{
  "mcpServers": {
    "storepoint": {
      "url": "https://mcp.storepoint.co/mcp"
    }
  }
}

Clients that support OAuth prompt you to sign in on first use. Clients that only support headers can send an API key instead, as shown in the Claude Code example.

Authentication

The server accepts two forms of authentication on the same endpoint:

Sign in with Storepoint (OAuth)

The default for Claude and ChatGPT. When you add the connector, your client redirects you to app.storepoint.co where you log in with your normal account, choose a locator, and approve the connection. No keys to copy. The connection is scoped to the single locator you approve.

Direct API key

For CLIs, scripts, and clients without an OAuth flow. Send your private API key as a Bearer token:

Authorization header

Authorization: Bearer sk_your_api_key

Generate a key in the Developer Portal in your Storepoint dashboard. Keys start with sk_. The same page lets you rotate or revoke keys at any time.

Treat the connection like an admin. Either lane grants full management access to the connected locator. Only connect clients you trust, and revoke access from the dashboard if a device or key is ever compromised.

Tools

Ten tools cover locations, custom fields, and your embed code. Your assistant picks the right one from your request, so you rarely reference these by name.

Tool	What it does
`list_locations`	Paginated list of all locations, published and draft.
`get_location`	Full details for one location by id.
`create_location`	Add a location. Plain addresses are geocoded automatically.
`update_location`	Partial update. Send only the fields you want to change.
`delete_location`	Permanently remove a location.
`get_custom_fields`	Your custom field definitions: name, type, label, color, icon.
`create_custom_field`	Add a field: button, text, phone, or icon.
`update_custom_field`	Rename or restyle a field. Location values are kept.
`delete_custom_field`	Remove a field definition.
`get_embed_code`	The widget embed snippet and your public locator token.

Write tools carry MCP destructiveHint annotations, so well-behaved clients ask for confirmation before changing or deleting data.

Permissions & multiple locators

Account owners can connect any of their locators.
Invited team members need the developer or admin role on a locator to approve a connection for it.
Each connection is scoped to one locator. Manage several locators by connecting each one separately, or ask us about consolidating.
If you have more than one locator, the approval screen asks which one to connect.

Disconnecting

Two sides, either works:

In your client: remove the Storepoint connector from its settings. The client discards its access immediately.
In Storepoint: rotate or revoke your private API key from the Developer Portal in your dashboard. Every connection authorized with that key stops working.

Your data stays put. Disconnecting only removes access. Locations, custom fields, and settings are untouched.