Skip to content

MCP server

Connect Claude, ChatGPT, Grok, Muse or any MCP client to a FirearmCart store — sign in with OAuth or use an API token, the store and theme tools, permissions, how changes are confirmed, and limits

Updated View as Markdown

FirearmCart runs one Model Context Protocol server for AI assistants and agents. It works with a store the way a staff member would — products, orders, customers, sales, discount codes, Reload subscriptions and FFL dealers — and builds and edits the storefront’s themes, pages, blogs and policies.

POST https://api.firearmcart.com/mcp

The server advertises itself as FirearmCart and has 84 tools (47 for the store, 37 for themes), 3 resources and 2 prompts. A connection only sees the tools its permissions allow.

Property Value
Endpoint https://api.firearmcart.com/mcp
Method POST only
Transport Streamable HTTP (JSON-RPC 2.0)
Auth OAuth sign-in, or Authorization: Bearer <token> with a store API token — the same server and tools either way
Rate limit 240 requests/minute per store (see Rate limits)
Protocol versions 2025-11-25 (default), 2025-06-18, 2026-07-28

It sits beside the v1 REST API, not inside it: same host and same API tokens, different protocol.


Two ways to connect

Both reach the same server and the same tools. They differ in who holds the credential.

Sign in with OAuth API token
For AI apps with connectors: Claude, ChatGPT, Grok, Grok Bot, Muse, Claude Code Clients that send a fixed header: Claude Code, Cursor, the Grok CLI, the xAI API’s remote MCP tools, scripts
Set up by Adding the URL in the app and signing in Creating a token at Profile → API Tokens
Permissions Every view permission, plus the changes ticked on the sign-in page; changes can be edited later under Connected apps The token’s abilities
Stops working when It is disconnected, the person who connected it is no longer a store owner or admin, or it goes unused for 30 days The token is deleted

Either way, only a store owner or admin can set it up, the store’s plan must include API access, and nothing on this server can charge cards, refund or move money. Each connection or token acts on one store; for several stores, connect each one.

Connecting an AI app

AI apps that support MCP connectors sign in with your FirearmCart account. You never paste a token into them: the app opens a FirearmCart sign-in page, you choose the store and what the app may do, and the app gets its own access, which you can change or remove at any time.

App Where to add it
Claude (claude.ai, Desktop) Customize → Connectors → Add → Add custom connector with https://api.firearmcart.com/mcp. Keep Sign in now and choose Register automatically under OAuth client: the server supports dynamic client registration, not Claude’s published identity (Client ID Metadata Documents). Then Add and Connect. On Team and Enterprise, an Owner adds it under Organization settings → Connectors and each member clicks Connect.
ChatGPT (chatgpt.com) Plugins → + → Add custom MCP server, with https://api.firearmcart.com/mcp as the Server URL and OAuth authentication. Accept the risk warning, select Create as a plugin, then install the plugin and pick it with @ in a chat. On personal ChatGPT plans such as Pro, FirearmCart can only look things up; to let it make changes, you need a ChatGPT Business, Enterprise or Edu plan.
Grok (grok.com) Connectors → New Connector → Custom, then paste https://api.firearmcart.com/mcp. On Grok Business and Enterprise, a workspace admin adds the connector first.
Grok Bot Ask the bot to “add a custom MCP server named FirearmCart at https://api.firearmcart.com/mcp”, then use the connect card it shows.
Muse (Meta: web, iOS and Android) In a chat, ask Muse to “create a custom connector named FirearmCart for the remote MCP server at https://api.firearmcart.com/mcp, using Streamable HTTP with OAuth sign-in”, then use the connect card it shows.
Claude Code claude mcp add --transport http firearmcart https://api.firearmcart.com/mcp, then run /mcp to sign in.

After you sign in, FirearmCart shows a consent page with:

  • Which app is asking. The app is named by the address it sends you back to (claude.ai, chatgpt.com, grok.com and so on), so a look-alike app can’t pass itself off as one you know. Apps running on your own computer, such as Claude Code, get an extra warning.
  • The store. Pick one. You can only choose a store you own or are an admin of, whose plan includes API access.
  • What the app may do. View access to the store is always included. Each kind of change is off until you tick it under Optional actions. See Permissions.

Every connected app is listed under Profile → API Tokens → Connected apps for the current store, with who connected it, whether it can change data, and when it was last used. From there you can change which changes it may make, or disconnect it. View access always stays on. A removed permission applies on the client’s next request. Tools for an added one appear the next time the client calls tools/list, since FirearmCart doesn’t send notifications/tools/list_changed. Everyone on the store’s team is notified when an app is connected, in the dashboard and by email; this alert can’t be turned off.

Using an API token

A store owner or admin creates the token at Profile → API Tokens (/user/api-tokens) on https://app.firearmcart.com, after switching to the store the token should act on, and ticks the abilities for the tools it needs (see Permissions). The client then sends it as a bearer token:

claude mcp add --transport http firearmcart https://api.firearmcart.com/mcp \
  --header "Authorization: Bearer $FIREARMCART_TOKEN"

Most desktop and IDE clients keep a JSON list of servers and accept a remote HTTP server in roughly this shape:

{
  "mcpServers": {
    "firearmcart": {
      "type": "http",
      "url": "https://api.firearmcart.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Note: The exact key names differ between clients — some spell the transport "transport" rather than "type", some nest headers differently, and some need a local bridge for remote servers. Check your client’s documentation; the only values that come from FirearmCart are the URL and the Authorization header.

A token that holds payments:charge, payments:tokenize, orders:upsell or * is refused (403), because the client stores the token and it also works on the REST API. Create a separate token for AI clients. See Authentication for the token model and format.

Verify with curl

The handshake is plain JSON-RPC, so you can prove a token works before touching a client config:

curl -sS https://api.firearmcart.com/mcp \
  -H "Authorization: Bearer $FIREARMCART_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-25",
      "capabilities": {},
      "clientInfo": { "name": "curl", "version": "1.0" }
    }
  }'

A working token returns a result whose serverInfo.name is FirearmCart and whose instructions field carries the server’s brief. Swap the method for tools/list to see the tools this token can reach.


Permissions

Every tool needs one ability. On a token they are the token’s abilities. An OAuth connection always holds every view ability (the :read ones), including any added after it connected, plus the change abilities ticked on the sign-in page. A connection needs at least one ability to connect, and only sees the tools it may use — the rest are left out of tools/list and cannot be called.

Ability Lets the connection Tools
products:read Look up products, prices, stock and collections, the store’s distributors’ catalogs, and the tax plugin’s tax codes search-products, search-distributor-catalog, list-collections, search-tax-codes
products:write Add products, import them from the store’s distributors at a markup, edit them — prices, markups, publish status, descriptions, specifications, SEO, images, the store’s own shipping weights and tax codes — and collections, including their covers create-product, import-distributor-products, update-product, set-product-markup, update-product-content, update-product-images, update-product-weight, set-product-tax-code, create-collection, update-collection
inventory:write Change the stock the store holds itself adjust-inventory
orders:read Look up orders, fulfillment and tracking search-orders
orders:write Record tracking, send orders to their suppliers, change who ships a line, add to order notes and change the receiving FFL fulfill-order, process-order, change-order-supplier, update-order-note, change-order-ffl
customers:read Look up customers search-customers
analytics:read Read sales and traffic summaries get-sales-summary, get-traffic-summary
discounts:read / discounts:write Read / create and update discount codes list-discounts / create-discount, update-discount
subscriptions:read / subscriptions:write Read / pause, resume, skip and cancel Reload subscriptions list-subscriptions / update-subscription, cancel-subscription
ffl:read Search the FFL dealer directory search-ffl-dealers
settings:read Read the store’s settings, payment gateways (read-only, with Test connection), domains (and why one won’t connect), setup progress, shipping and tax zones, and the plugin marketplace get-store-settings, check-gateways, check-domain, get-setup-progress, list-shipping-zones, list-tax-zones, list-marketplace-plugins
settings:write Change the store’s business details, social links, FFL visibility and branding, set the store’s FFL from a license copy, connect custom domains, and save shipping and tax zones update-store-settings, set-store-ffl, connect-domain, save-shipping-zone, save-tax-zone
themes:read View themes and storefront content The 18 theme read tools
themes:write Edit and publish themes and storefront content The 19 theme write tools, plus the 18 read tools — edit includes view

get-store-overview and search-docs work for any connection. Images serve both the catalog and the storefront, so upload-media and create-upload-link work with products:write or themes:write, and list-media with any product or theme ability. Tools re-check their ability on every call, so a permission removed under Connected apps takes effect on the next request.


Tools

Store tools

Tool What it does Ability
get-store-overview The store, its timezone and today’s date, what this connection may do, catalog counts, plugins and collections. Called first. Any
search-docs Search these docs for how FirearmCart works, returning the best-matching sections with links. Any
search-products Find products by name, SKU, barcode, manufacturer or brand; filter by status, stock, collection, type, sale, provider, missing shipping weight or missing tax code. One product in full: variants, stock source, shipping weight, tax code, cost basis, MAP, FFL and shipping class, plus its description, specs and SEO fields. products:read
search-distributor-catalog Search the catalogs of the store’s distributors for items to import, with each item’s cost to the store, MAP, stock and the store product it already is. Only while a distributor is switched on. products:read
list-collections The store’s collections with product counts and URLs, how many products are in none, and the collection types it can still add. products:read
search-orders Find orders by number (ours, GunBroker or Guns.com), customer, payment or fulfillment status and date range, or the orders that need the merchant. One order in full: items with who ships each, FFL flags, totals, the FFL dealer, fulfillments, tracking and the order note. orders:read
search-customers Find customers by name, email or phone, with paid orders and total spent. One customer with addresses and recent orders. customers:read
get-sales-summary Orders, gross revenue, average order value, discounts and units for a period, the change against the previous period, and the top products, collections and codes — counted as the Sales report counts them. analytics:read
get-traffic-summary Visits, unique visitors, pages viewed, time on site, orders and conversion rate for a period, the change against the previous period, and the top sources, landing pages and locations — counted as the Traffic report counts them. analytics:read
list-subscriptions Reload subscriptions by status or customer, with items and history. Only for stores using Reload. subscriptions:read
list-discounts Discount codes with their value, targets, usage, dates and status. discounts:read
search-ffl-dealers FFL dealers by name, license number or near a ZIP code. ffl:read
get-store-settings The store’s business details, branding, social links, storefront, own FFL, payment gateways (never credentials) and domains. settings:read
check-gateways Whether each payment gateway can take payments: its recent payments and failures with the gateway’s message, and Test connection. settings:read
check-domain Why a custom domain isn’t connecting — nameservers not changed, wrong or still propagating, DNSSEC, a CNAME missing or pointing elsewhere — with the fix, or which way to connect a new one. settings:read
get-setup-progress What is done and left before launch, step by step, with dashboard and docs links. settings:read
list-shipping-zones Shipping zones with their states and rates, the carriers quoting live rates, and states no zone covers. settings:read
list-tax-zones Manual tax zones with their rates and states, and the tax plugin when one calculates tax. settings:read
list-marketplace-plugins The plugin marketplace this store can see: what each plugin does, whether it’s on, its help page, and the store’s distributor slots, marketplace feeds and tax plugin. settings:read
search-tax-codes The tax plugin’s tax codes, by code or by words in their description. Only while Avalara or TaxJar is active. products:read
create-product Add one product, as a draft unless asked to publish it, with its price, cost, stock, weight, collection, description, specs, SEO, options and variants, and up to 5 images. Reports whether it needs an FFL and its shipping class. products:write
update-product Change one product’s or variant’s price or compare-at price, or publish / unpublish a product. products:write
update-product-content Change one product’s description, specifications, or SEO title and description, distributor products included. products:write
update-product-images Add, remove and reorder one product’s images, choose the featured one, set alt text, and choose which image each variant shows. products:write
update-product-weight Set the shipping weight of one product, or of a variant with its own, distributor products included. products:write
set-product-tax-code Set or remove the tax code of one product, or of many at once by IDs, product type or collection, previewed first. Only while Avalara or TaxJar is active. products:write
set-product-markup Price up to 500 products at a markup on their cost, never under MAP, by IDs or by provider, product type and collection, previewed first. products:write
import-distributor-products Import up to 500 items from one of the store’s distributors at a markup on cost, by SKU or every match of a search, previewed first. They arrive as drafts unless asked to publish them; more than 5 run as a background import. Only while a distributor is switched on. products:write
adjust-inventory Set or adjust the stock the store itself holds for one product or variant. inventory:write
fulfill-order Record tracking for a parcel the merchant shipped, emailing the customer once. orders:write
process-order Send an order’s waiting lines to their suppliers, placing real purchase orders: previewed first, then sent as approved. orders:write
change-order-supplier Change who ships one order line before it is sent: own stock, an outside source or a distributor. orders:write
update-order-note Add to an order’s internal note, or replace it. orders:write
change-order-ffl Change the FFL dealer an order’s firearms ship to, while none has gone out. orders:write
update-store-settings Change the store’s business details, social links, FFL visibility, logo, favicon or checkout logo. settings:write
set-store-ffl Set the store’s own FFL from a copy of its license, previewed first. settings:write
connect-domain Connect a custom domain, or re-check and retry one: with FirearmCart-managed DNS (the nameservers to set) or the merchant’s own DNS (its CNAME record). settings:write
save-shipping-zone Create a shipping zone, or change its name, states, on switch and rates. settings:write
save-tax-zone Create a tax zone, or change its name, rate, states or on switch. settings:write
upload-media Add an image to the media library from a public https URL, a file attached in ChatGPT, or an upload-link upload, and get its media_id. products:write or themes:write
create-upload-link Get a 15-minute link an agent that can run commands sends files to with curl. Not offered to the in-app AI assistant. products:write or themes:write
create-collection Add a collection from the platform’s collection types. products:write
update-collection Move up to 50 products into or out of a collection, change its type (which renames it and changes its URL), or set or remove its cover image. products:write
update-subscription Pause, resume or skip the next charge of one subscription. subscriptions:write
cancel-subscription Cancel one subscription. subscriptions:write
create-discount Create a discount code for the whole store, products, collections or customers. discounts:write
update-discount Turn a code on or off, or change its dates, usage limit, minimum purchase or name. discounts:write

All money is in dollars and all dates are in the store’s timezone, which is the store owner’s timezone.

Theme tools

The 18 read tools list and read themes and their files, search them, describe section schemas and theme settings, list pages, policies, blogs, articles, menus, media, fonts, plugins, collection filters and file versions, and screenshot a theme. The 19 write tools create, update and delete theme files, restore versions, create and update pages, policies, blogs and articles, create, update and delete navigation menus, generate a menu from the catalog with AI, set collection filters, add a theme from the theme store, duplicate a theme and publish one.

The server also ships three resources — liquid-guidelines, theme-json-shapes and plugin-liquid — and two prompts for recreating a page from a mockup and building a section. See Resources & prompts.

Every tool’s arguments, results and guardrails are on Tools.


Images and uploads

MCP has no way to send a file, so an image reaches the store’s media library (the Files page) one of four ways:

The image is How Who can use it
At a public https address upload-media with url. The server downloads it. Every app
Attached in a ChatGPT conversation upload-media with file. ChatGPT passes its download link. ChatGPT
A file on the agent’s own machine create-upload-link, then curl -F "file=@photo.jpg" "<link>" once per file, then upload-media with the upload_id from each reply. Agents that can run commands: Claude Code, Grok Bot, Cursor
On the merchant’s computer, in a chat-only app The merchant uploads it on the Files page, and the assistant finds it with list-media and since. Every app

upload-media returns a media_id and a CDN url. Images can be JPG, PNG, GIF or WebP up to 10 MB and 40 megapixels. SVG, HEIC, AVIF and animated WebP are refused. The type is read from the file itself, never its name, and location data is removed from photos. The same image uploaded twice returns the same media_id.

A copy of the store’s FFL reaches set-store-ffl the same ways, as a url, a ChatGPT file or an upload link made with purpose: "license" (one PDF, JPG or PNG; it needs settings:write).

Downloads only reach public internet addresses: a link to a private network, or one that redirects there, is refused. An upload link takes up to 10 files, expires after 15 minutes, and is the only credential the upload needs, so treat it like a password. Each file it receives is held privately for one hour and becomes media only when upload-media uses it; each upload can be used once.


How changes work

Store changes

Every store change is narrow and checked:

  • One record per call, after the assistant has read it. The assistant is told to describe the change (record, field, current → new) and get a clear yes first, and most apps also ask you to approve each change. Tax codes, markups and distributor imports can change many products in one call: the assistant previews it, tells you how many products it covers, and the change is refused if that number has changed by the time it’s applied.
  • It must quote what it read. Price, status and stock changes carry the value the assistant last saw, and content changes carry the version of the description, specs and SEO fields it read. If the record changed since, nothing is saved and the assistant has to read it again.
  • Prices below MAP are refused. A price below cost, or a move past double or under half the current price, is refused unless the assistant passes an explicit flag after you confirm that exact number.
  • Only stock you own can change. Distributor stock, and stock synced from Lightspeed, FastBound or Orchid eBound, updates from its source and is refused. A pack variant sells the product’s units, so the product is adjusted instead. A product’s name, type, cost and SKU are set when create-product adds it and are never changed through the server afterwards.
  • Descriptions are cleaned and compliance specs kept. A description keeps the product editor’s kinds of markup; scripts, styles, images and iframes are removed, and its only Liquid can be a plain product field such as {{ product.specifications }}. A magazine capacity or action type spec decides state shipping restrictions and FFL transfers, so one a product already has is changed only on the product page.
  • Collections stay one per type. A collection is created from the platform’s collection types, and a product sits in at most one, so moving a product takes it out of its old collection. Changing a collection’s type moves it to a new URL, so the assistant must quote the name it read and pass a flag after you agree that old links stop working. Collections are deleted only on the Collections page.
  • Images are copied in. An image from the media library is copied onto the product or collection, so deleting it from the library never breaks the product. Image changes quote the images_version or cover the assistant read, the old collection cover stays until the new one is saved, and a product page that is open refreshes its images.
  • New products start as drafts. create-product adds one product per call and refuses an SKU the store already uses, a product type FirearmCart doesn’t know (suggesting the closest), and a second product with the same name within 10 minutes, which is how a retried call shows up. The store’s plan limit on products applies. The product type decides FFL requirements and shipping class (a Hazmat specification can make powder or primers hazmat too), so the result reports both. Products imported from a distributor also arrive as drafts, priced at their cost plus the markup you chose and never under MAP, unless you ask for them to go live.
  • Purchase orders go out only as approved. process-order previews first: each shipment, who sends it, where it goes, its cost and anything blocking it, with a version. The send must name that version, so it does exactly what the merchant saw, and each line goes out once even if the order page sends it at the same moment. Test orders, local pickups and unpaid or refunded orders are never sent.
  • Order changes follow the order page’s rules. Tracking is recorded only for a parcel already shipped (a distributor line that was never sent is refused, since the distributor would ship it too), who ships a line changes only while it waits, and the receiving FFL only while no firearm line has gone out. Expired or delisted licenses are refused, and an NFA item going to a dealer not on file as SOT needs an explicit flag. Notes are added to, signed with who added them.
  • Settings quote the version they read. update-store-settings saves only when settings_version still matches, and its changes reach the storefront and checkout at once. Payment gateways are read-only, credentials never leave FirearmCart, and the lock screen and custom scripts stay in the dashboard. Shipping rates follow the zone editor’s range rules, a state sits in one active tax zone at most, and deleting zones stays in the dashboard.
  • Previews (dry_run) check a change without saving it.

Prices and content are saved the way the product page saves them, including the markup and cost basis that distributor syncs rely on, and the storefront’s cached pages refresh within a minute. Distributor syncs only update stock, cost and pricing, so description, spec and SEO changes on a distributor product stay. Every change an assistant attempts — made, refused, or already done — is recorded with the connection and the exact change.

Theme changes

The initialize response ships a long instructions block with the theme rules, which your agent receives automatically. In short:

  1. list-themes, then never build against the live theme. Use an inactive library copy, or duplicate-theme to make one. File-write tools refuse the live theme unless the merchant asked to edit it (allow_active: true).
  2. Read the liquid-guidelines resource before writing any Liquid. It is the platform rulebook, and the failures it covers are silent ones.
  3. Inventory before authoring. list-theme-files and get-section-schema first — configuring an existing section through templates/*.json beats writing a new one.
  4. Save, then look. Change part of an existing file with update-theme-file edits (find-and-replace pairs) instead of sending the whole file again. Saves are validated (Liquid, JSON and schema) and versioned; screenshot-theme on desktop, then tablet and mobile.
  5. Revert cheaply. list-file-versions and restore-file-version when a change made things worse.
  6. Publish last. publish-theme when the merchant is ready; the previously live theme is deactivated automatically.

Menus, policies, pages and plugin sections are store data with their own tools, not theme files. Collection filters are a theme setting, trimmed with list-collection-filters and set-collection-filters rather than by editing the facets snippets.


Store scoping

The authenticated principal is a store, not a person — see Authentication. Every tool resolves the store from the token or connection and limits its query to that store before doing anything else. No tool takes a store argument, and a record that belongs to another store is reported exactly like one that does not exist.


Transport

The endpoint speaks Streamable HTTP: every client message is an HTTP POST carrying a JSON-RPC envelope.

  • POST is the only usable method. GET and DELETE answer 405 with Allow: POST. There is no server-initiated SSE channel, so a client that insists on opening a GET stream first cannot connect.
  • Those 405s are unauthenticated. Auth, permission and throttle checks run on POST only, so a probe that expects a 401 from a GET reads the wrong signal.
  • Responses are application/json, switching to text/event-stream only when a tool streams. Send Accept: application/json, text/event-stream as the MCP spec requires.

The server is stateless: it issues no session id, and every request carries its own credentials.


Rate limits

Limit Keyed by
Requests 240/minute Store
Unauthenticated requests 10/minute Client IP
Sales summaries 30/minute Store
Upload links 20/hour Store
Files sent to an upload link 30/minute per link and 60/minute per address Link, client IP

The request budget is separate from the /v1 budget of 60/minute: exhausting one leaves the other untouched. The unit is requests, not tool calls — a client that batches several JSON-RPC messages into one POST spends one slot. Changes have no separate cap: your AI app runs on your own AI account. See Rate limits.


Errors

Tool-level problems — a record that doesn’t exist, a refused change — come back as MCP error results, which your client shows. The rejections below happen before the MCP server runs, so they arrive as plain HTTP, which most clients surface as a bare connection failure:

Status Body Cause
401 {"message": "Unauthenticated."} Missing, mistyped or deleted token; a disconnected app; a connection whose user is no longer a store owner or admin; or an expired sign-in. Carries WWW-Authenticate: Bearer realm="mcp", resource_metadata="https://api.firearmcart.com/.well-known/oauth-protected-resource/mcp", which OAuth apps follow to sign in again.
403 {"error": "forbidden", "message": "API access is not enabled for this team."} The store’s plan has no API access and it holds no add-on.
403 {"error": "subscription_expired", …} The store’s subscription is suspended or past its cancellation date.
403 "This API token can charge cards…" A token holding a payment or upsell ability, or *.
403 {"message": "Invalid ability provided."} The connection holds none of the abilities above.
405 (empty, with Allow: POST) The request used GET or DELETE.
429 Standard throttle response, with Retry-After 240 requests/minute exceeded.

If a client reports “server disconnected” or “failed to initialize” with no detail, replay the handshake with the curl command — the HTTP status tells you which row you are in.


For developers: OAuth details

AI apps discover everything themselves; this is for anyone building or debugging a client.

Protected resource metadata https://api.firearmcart.com/.well-known/oauth-protected-resource/mcp
Authorization server metadata https://api.firearmcart.com/.well-known/oauth-authorization-server
Issuer https://api.firearmcart.com
Authorization endpoint https://app.firearmcart.com/oauth/authorize
Token endpoint https://api.firearmcart.com/oauth/token
Dynamic client registration POST https://api.firearmcart.com/oauth/register
Grant Authorization code with PKCE (S256 only), refresh tokens
Client authentication none (public clients)
Scope mcp:use
Access token lifetime 1 hour; refresh tokens last 30 days and rotate on use

A client that registers again to reconnect gets a new client_id. When the merchant approves it for a store, it replaces the connection the same app (same client name and redirect host) already had to that store, and the consent screen starts from that connection’s permissions.

Registration accepts redirect URIs on claude.ai, claude.com, chatgpt.com, grok.com, cursor.com, www.cursor.com and Muse’s hosts (agent.meta.ai, muse.ai and platform.muse.ai), loopback addresses (http://localhost or http://127.0.0.1, any port) for local apps, and Cursor’s cursor:// scheme, which Grok Bot registers alongside its other callbacks.


The older /mcp/themes endpoint

https://api.firearmcart.com/mcp/themes is the original, theme-only endpoint. It serves the same 37 theme tools, upload-media and create-upload-link, resources and prompts under the name FirearmCart Theme Dev, accepts the same tokens and sign-in, and needs themes:read or themes:write. Existing setups keep working; point new ones at https://api.firearmcart.com/mcp.


  • Tools — every tool’s arguments, results and guardrails
  • Resources & prompts — the reference material the server hands your agent
  • AI Assistants — the merchant guide to connecting and managing assistants
  • Authentication — store API tokens, their abilities, and the API access gate
  • Rate limits — how the MCP budget sits alongside the /v1 budgets
  • Themes — the merchant-facing theme editor the theme tools write into
Navigation

Type to search…

↑↓ navigate↵ selectEsc close