Model Context Protocol

For the Cult MCP Server

Connect Cursor, Claude, VS Code, or other MCP-aware assistants to the same hosted bridge (or run a tiny local process). Tools cover catalog discovery, shipping estimates, and checkout flows — sensitive payment steps still follow whatever your wallet or policy requires.

What you can do with the FTC MCP server

Once connected, your assistant can call named toolsinstead of you hand-authoring REST for every step. The server translates each tool into the right HTTP call to For the Cult's public agent API, returns plain-text summaries your model can read, and surfaces errors in a consistent shape.

Common use cases

Let a copilot browse featured products or run semantic search.
Estimate a cart or shipping before a human confirms checkout.
Wire an internal ops bot that polls order status after a payment link is sent.
Prototype agent flows in Cursor without pasting OpenAPI into every prompt.
Share a single hosted endpoint with contractors who should not clone your repo.

How it fits together

Your MCP host (Cursor, VS Code, Claude, etc.) loads the FTC MCP server. That server is the only piece that speaks our HTTPS API on behalf of the session.

How your assistant reaches For the Cult

Product shots & walkthroughs

Below are layout frames your design team can replace with real screenshots. Until those assets ship, the frames explain what to capture so support and marketing stay aligned.

IDE: MCP server connected

Capture your Cursor / VS Code / Claude screen showing For the Cult in the MCP server list. Export PNG or WebP and add it under public/mcp/, then swap this block for next/image.

Figure 1 — MCP visible in the host UI

Browser: health check

A short screen recording or screenshot of /healthz returning JSON reassures operators the edge is reachable (separate from the MCP POST URL, which is not meant for the address bar).

Figure 2 — Health endpoint in a normal browser tab

Remote vs local

Remote (hosted): Best when you want zero install. Paste the HTTPS MCP URL into your IDE, reload tools, and go. The URL ending in /mcp is not a regular webpage — opening it in Chrome will error; that is expected.
Local (stdio): Runs npx -y @forthecult/mcp on your machine. Good for air-gapped workflows or when your security team prefers outbound calls from a known binary. Default API base is https://forthecult.store/api.

connection ritual

$ npx -y @forthecult/mcp

Copy the npx line for local stdio. For hosted HTTP, use the MCP URL from your IDE tab or the POST row on /for-agents.

First-time setup (hosted MCP)

Written for someone who has never wired MCP before — usually a builder setting up Cursor for the team.

Step 1Pick your IDE tab belowJump to Cursor, VS Code, Claude, etc. Each tab lists the clicks first, then JSON.
Step 2Copy the MCP URLUse https://mcp.forthecult.store/mcp — this is the streamable HTTP endpoint your host must POST to.
Step 3Reload toolsMost hosts cache the tool list. Restart the MCP panel or the whole IDE if nothing shows up.
Step 4Prove the edge is aliveOpen https://mcp.forthecult.store/healthz in a browser — JSON with ok:true means the service is reachable.
Step 5Stay read-only at firstCall list/search tools before anything that touches checkout.
Step 6Need the package instead?Switch to the Local tab in the terminal widget or see the stdio JSON in your IDE tab.

First prompts to try

Paste these verbatim after tools load — they stay read-only until you intentionally drive checkout.

"List available MCP tools" — confirms the host sees the FTC bundle.
"Call list_featured_products with empty arguments" — exercises catalog access.
"Search products for waterproof jackets under 200" — exercises search with constraints.
"Summarize shipping options for US zip 78701 with a single hoodie in the cart" — touches shipping tools without placing an order.

Connect your MCP client (step-by-step + JSON)

Each tab lists click-by-click steps for that product family, then a JSON snippet you can paste when the UI asks for raw config.

Open Cursor → Settings (gear) → search “MCP” (or Features → MCP, depending on version).
Choose Add server / New MCP server → pick HTTP or “Streamable HTTP” if offered.
Paste the server URL from the block below (the full address ending in /mcp).
Save, then use “Refresh” or restart Cursor so the tool list reloads.
Open a chat that has tools enabled and try a prompt from “First prompts” on this page.

CURSOR — HTTP MCP (paste or merge)

{
  "mcpServers": {
    "forthecult": {
      "type": "http",
      "url": "https://mcp.forthecult.store/mcp"
    }
  }
}

Connection values

Item	Value
MCP stream URL	https://mcp.forthecult.store/mcp
Health (browser-safe)	https://mcp.forthecult.store/healthz
Host root (rarely pasted alone)	https://mcp.forthecult.store

Example wire snippet

Hosts wrap JSON-RPC for you — this is what a raw tools/list looks like on the wire if you are debugging with curl or mitmproxy.

tools/list

{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "params": {},
  "id": 1
}

Troubleshooting

Browser shows “Cannot GET /mcp” or similar: Expected. That URL is for MCP clients using POST + streamable payloads, not for visiting like a webpage. Use the health URL for a quick browser check instead.
Tools never appear: Reload the MCP server in your IDE, confirm the JSON has no trailing commas, and verify you are on a build that supports HTTP MCP. Try the stdio snippet if HTTP is blocked by policy.
401 / 403 from the MCP host: Double-check Host allowlists on the server side if you self-host a fork; the public Railway deploy expects the official hostname or Railway-provided domain.
Local stdio cannot reach the API: Confirm outbound HTTPS is allowed and that FORTHECULT_API_BASE_URL points at a reachable base (https only).

For the Cult MCP Server

What you can do with the FTC MCP server

Common use cases

Let a copilot browse featured products or run semantic search.
Estimate a cart or shipping before a human confirms checkout.
Wire an internal ops bot that polls order status after a payment link is sent.
Prototype agent flows in Cursor without pasting OpenAPI into every prompt.
Share a single hosted endpoint with contractors who should not clone your repo.

How it fits together

Your MCP host (Cursor, VS Code, Claude, etc.) loads the FTC MCP server. That server is the only piece that speaks our HTTPS API on behalf of the session.

How your assistant reaches For the Cult

Product shots & walkthroughs

Below are layout frames your design team can replace with real screenshots. Until those assets ship, the frames explain what to capture so support and marketing stay aligned.

IDE: MCP server connected

Capture your Cursor / VS Code / Claude screen showing For the Cult in the MCP server list. Export PNG or WebP and add it under public/mcp/, then swap this block for next/image.

Figure 1 — MCP visible in the host UI

Browser: health check

A short screen recording or screenshot of /healthz returning JSON reassures operators the edge is reachable (separate from the MCP POST URL, which is not meant for the address bar).

Figure 2 — Health endpoint in a normal browser tab

Remote vs local

Remote (hosted): Best when you want zero install. Paste the HTTPS MCP URL into your IDE, reload tools, and go. The URL ending in /mcp is not a regular webpage — opening it in Chrome will error; that is expected.
Local (stdio): Runs npx -y @forthecult/mcp on your machine. Good for air-gapped workflows or when your security team prefers outbound calls from a known binary. Default API base is https://forthecult.store/api.

connection ritual

$ npx -y @forthecult/mcp

Copy the npx line for local stdio. For hosted HTTP, use the MCP URL from your IDE tab or the POST row on /for-agents.

First-time setup (hosted MCP)

Written for someone who has never wired MCP before — usually a builder setting up Cursor for the team.

Step 1Pick your IDE tab belowJump to Cursor, VS Code, Claude, etc. Each tab lists the clicks first, then JSON.
Step 2Copy the MCP URLUse https://mcp.forthecult.store/mcp — this is the streamable HTTP endpoint your host must POST to.
Step 3Reload toolsMost hosts cache the tool list. Restart the MCP panel or the whole IDE if nothing shows up.
Step 4Prove the edge is aliveOpen https://mcp.forthecult.store/healthz in a browser — JSON with ok:true means the service is reachable.
Step 5Stay read-only at firstCall list/search tools before anything that touches checkout.
Step 6Need the package instead?Switch to the Local tab in the terminal widget or see the stdio JSON in your IDE tab.

First prompts to try

Paste these verbatim after tools load — they stay read-only until you intentionally drive checkout.

"List available MCP tools" — confirms the host sees the FTC bundle.
"Call list_featured_products with empty arguments" — exercises catalog access.
"Search products for waterproof jackets under 200" — exercises search with constraints.
"Summarize shipping options for US zip 78701 with a single hoodie in the cart" — touches shipping tools without placing an order.

Connect your MCP client (step-by-step + JSON)

Each tab lists click-by-click steps for that product family, then a JSON snippet you can paste when the UI asks for raw config.

Open Cursor → Settings (gear) → search “MCP” (or Features → MCP, depending on version).
Choose Add server / New MCP server → pick HTTP or “Streamable HTTP” if offered.
Paste the server URL from the block below (the full address ending in /mcp).
Save, then use “Refresh” or restart Cursor so the tool list reloads.
Open a chat that has tools enabled and try a prompt from “First prompts” on this page.

CURSOR — HTTP MCP (paste or merge)

{
  "mcpServers": {
    "forthecult": {
      "type": "http",
      "url": "https://mcp.forthecult.store/mcp"
    }
  }
}

Connection values

Item	Value
MCP stream URL	https://mcp.forthecult.store/mcp
Health (browser-safe)	https://mcp.forthecult.store/healthz
Host root (rarely pasted alone)	https://mcp.forthecult.store

Example wire snippet

Hosts wrap JSON-RPC for you — this is what a raw tools/list looks like on the wire if you are debugging with curl or mitmproxy.

tools/list

{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "params": {},
  "id": 1
}

Troubleshooting

Browser shows “Cannot GET /mcp” or similar: Expected. That URL is for MCP clients using POST + streamable payloads, not for visiting like a webpage. Use the health URL for a quick browser check instead.
Tools never appear: Reload the MCP server in your IDE, confirm the JSON has no trailing commas, and verify you are on a build that supports HTTP MCP. Try the stdio snippet if HTTP is blocked by policy.
401 / 403 from the MCP host: Double-check Host allowlists on the server side if you self-host a fork; the public Railway deploy expects the official hostname or Railway-provided domain.
Local stdio cannot reach the API: Confirm outbound HTTPS is allowed and that FORTHECULT_API_BASE_URL points at a reachable base (https only).

For the Cult MCP Server

What you can do with the FTC MCP server

Common use cases

How it fits together

Product shots & walkthroughs

Remote vs local

First-time setup (hosted MCP)

First prompts to try

Connect your MCP client (step-by-step + JSON)

Connection values

Example wire snippet

Troubleshooting

More links

For the Cult MCP Server

What you can do with the FTC MCP server

Common use cases

How it fits together

Product shots & walkthroughs

Remote vs local

First-time setup (hosted MCP)

First prompts to try

Connect your MCP client (step-by-step + JSON)

Connection values

Example wire snippet

Troubleshooting

More links