Squatch Stack · MCP

Tools for your assistant

A small, friendly Model Context Protocol server. Point any MCP client at it and your assistant can tell you what the studio builds, browse the goods and hand you a checkout link, and it can pass the studio a request for something custom. No sign-in. Nothing gets bought or emailed without you.

Connect

https://mcp.squatch.cc/mcp

Streamable HTTP. No sign-in, no key, nothing to install.

Add to Cursor Add to VS Code

Claude Desktop and claude.ai, in three steps

  1. SettingsGeneralAccount Connectors Connectors Add custom connector

    1. Settings → Connectors → Add custom connector

  2. Add custom connector NameSquatch Stack Remote MCP server URLhttps://mcp.squatch.cc/mcp Add

    2. Name: Squatch Stack. URL: https://mcp.squatch.cc/mcp. Add.

  3. Show me the Squatch Stack shop Nowhere to Be · M · 2Buy

    3. Ask: “Show me the Squatch Stack shop.” It opens right in the chat.

Every app:

Claude (claude.ai and Claude Desktop)

Settings → Connectors → Add custom connector. Name it Squatch Stack, paste the URL above, and leave authentication empty. Then start a chat and ask away.

Claude Code
claude mcp add --transport http squatch https://mcp.squatch.cc/mcp
OpenCode

In opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "squatch": { "type": "remote", "url": "https://mcp.squatch.cc/mcp", "enabled": true }
  }
}
Codex CLI
codex mcp add squatch --url https://mcp.squatch.cc/mcp
VS Code (Copilot)

In .vscode/mcp.json:

{ "servers": { "squatch": { "type": "http", "url": "https://mcp.squatch.cc/mcp" } } }
Cursor

In ~/.cursor/mcp.json:

{ "mcpServers": { "squatch": { "url": "https://mcp.squatch.cc/mcp" } } }
ChatGPT

Where your plan allows custom connectors: Settings → Apps & Connectors → Advanced → Developer mode, then Create, paste the URL above, and choose no authentication.

Anything that can send a POST

MCP is JSON-RPC over HTTPS:

curl -s https://mcp.squatch.cc/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"studio_info","arguments":{}}}'

What you'll see

Try saying

Say “Squatch Stack” in your request so your assistant uses these tools, not a general web search.

Answers come back as short, readable text with links: a table of sizes, a checkout link you open yourself, a reference number for a request. Nothing is bought or sent unless you do it.

For AI assistants reading this page

Tools

studio_infoWhat Squatch Stack builds, with links and contact.
show_shopOpen the shop right in the chat: photos, sizes, and a Buy button that opens the secure checkout (where the app supports interactive views).
list_goodsBrowse the shop: tees, hoodies, mugs and drinkware, hats, stickers, posters, totes, desk mats, stationery and accessories. Search finds a design or option by name.
get_goodOne product: description, designs, colors, sizes, variant ids and prices.
start_checkoutMake checkout links to Squatch Stack's own store for the chosen items, one per item, each opening with that option picked. It buys nothing; a person opens a link and pays.
contact_draftA ready-to-send email link to the studio. It sends nothing.
parse_buffaloTag a Buffalo buffalo sentence as city, animal and verb.
request_customLeave a request for a person at the studio: something custom, details, an update, order help. Returns a private token for reading the answer. Sends no email.
request_statusCheck a request: with its private token, the studio's answer; with the short SQ- reference, the status only.
support_optionsWays to back the studio's open work: monthly tiers and one-time options, what each gets, and a checkout link where card checkout is live. It starts no payment. Squatch.CC LLC is a for-profit business; support is not tax-deductible.
about_this_serverWho runs this, how to verify it, and exactly what each tool can and cannot do.

No client? No problem

MCP is JSON-RPC over HTTPS, so anything that can send a POST can use these tools:

curl -s https://mcp.squatch.cc/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"studio_info","arguments":{}}}'

Just want JSON?

The reading tools are also plain web addresses. Open one in a browser, or have any agent that can fetch a URL read it. JSON by default; add ?output=md for Markdown. No key.

/api/v1/studioWhat Squatch Stack builds, its links and contact.
/api/v1/goodsThe goods in the shop, with prices, designs, colours, sizes, photo and link. Optional search by name or by a design, colour or size option.
/api/v1/goods/{slug}One product: description, photos, and every design, colour and size with its price and stock.
/api/v1/buffaloTag each word of a Buffalo buffalo sentence as city, animal or verb.
/api/v1/supportWays to support the studio's open work: tiers, prices, what each gets, and a checkout link where card checkout is live. Not tax-deductible (for-profit LLC).

Reading only. Making a checkout link, sending the studio a request, checking a request and drafting an email are on the MCP server. Described in OpenAPI 3.1; the list is at /api/v1.

Is this really Squatch Stack?

Yes, and you can check it without taking our word for it. This server is in the official MCP Registry as cc.squatch/mcp, verified by a DNS record on squatch.cc, and squatch.cc/.well-known/mcp points here. It is run by Squatch.cc LLC, a Missouri company. Checkout links open store.squatch.cc, the studio's own store, where you see the cart and pay. Requests land in an inbox a person reads, and are deleted after 180 days. Ask your assistant to call about_this_server for the details.

Fair use

About 60 requests a minute per address (MCP and JSON together), 5 checkout links, 2 studio requests and 5 request checks a minute. Please don't train on what you find here.