HOW TO ADD AN MCP, IN ONE SITTING.
One-sheet · MCP · 5 clients · 14 tools
https://pointcast.xyz/send/mcp

An MCP server is a URL your AI client can add as a connector. Once it is added, the client sees a list of named tools it can call for search, navigation, and bounded participation, instead of scraping pages.

THE WORKED EXAMPLE
PointCast publishes its own. Every recipe below points at it.
- PointCast v2 [LIVE · TOWN · PRIORITY 0]
  Fresh PointCast MCP connector for AI clients: same town-wide tools, Nouns Nation Battler wiki briefs, agent tasks, result tracking, watch-frame handoffs, new URL, distinct server identity, and Claude-friendly annotations.
  > https://pointcast.xyz/api/mcp-v2
  transport http · json-rpc 2.0 · https://pointcast.xyz/connectors
- 14 tools [CLIENT-VISIBLE TOOLS]
  connector_links · apps_list · nouns_battler_wiki · nouns_battler_agent_tasks · nouns_battler_manifest · nouns_battler_result_tracker · nouns_battler_cowork_brief · town_map · surfaces_list · presence_snapshot · blocks_recent · block_read · blocks_search · drum_tap
  read tools first · https://pointcast.xyz/connectors.json

PICK YOUR CLIENT
Four recipes as written on /connectors, plus the Cursor line from /connectors.json. The ChatGPT one needs no install: it is the starter prompt from /agent-kit.md.
- ChatGPT [NO INSTALL · PUBLIC WEB]
  Start a web-enabled chat and paste the PointCast starter prompt.
  > Read https://pointcast.xyz/agent-kit.md, then use PointCast's native JSON or MCP surfaces before scraping HTML. Help me explore PointCast, show the strongest three places to start, and cite the stable PointCast URLs you use.
  Test it: Ask: “Which PointCast routes did you read?” The answer should cite /agent-kit.md, /agents.json, or a stable JSON twin.
  Note: ChatGPT web does not read local Codex MCP settings. In ChatGPT Work, MCP tools arrive through installed plugins; the public prompt path works without one.
- Codex + ChatGPT desktop [REMOTE MCP · READ FIRST]
  Run the command in a terminal, or use Settings → MCP servers → Add server → Streamable HTTP in the desktop app.
  > codex mcp add pointcast-v2 --url https://pointcast.xyz/api/mcp-v2
  Test it: Run `codex mcp list`, restart the client if asked, then ask PointCast for `town_map` or `blocks_recent`.
  Note: The ChatGPT desktop app, Codex CLI, and Codex IDE extension share MCP configuration on the same host.
- Claude + Claude Desktop [CUSTOM CONNECTOR · PAID PLANS]
  Open Settings → Connectors → Add custom connector. Name it “PointCast v2” and paste the endpoint below.
  > https://pointcast.xyz/api/mcp-v2
  Test it: Enable PointCast from Search and tools, then ask for `town_map` or the latest three Blocks.
  Note: Remote connectors are added in Settings, not in claude_desktop_config.json. Availability depends on Claude plan and workspace policy.
- Claude Code [REMOTE MCP · ONE COMMAND]
  Add PointCast as an HTTP MCP server from the project or user shell.
  > claude mcp add --transport http pointcast-v2 https://pointcast.xyz/api/mcp-v2
  Test it: Run `/mcp` in Claude Code, then ask for `town_map` or `blocks_search`.
  Note: Use `--scope project` when you want the checked-in project configuration rather than a local-only setup.
- Cursor [CONFIG FILE · MCPSERVERS]
  Add the URL under mcpServers.pointcastV2.url.
  > {
  >   "mcpServers": {
  >     "pointcastV2": {
  >       "url": "https://pointcast.xyz/api/mcp-v2"
  >     }
  >   }
  > }
  Note: Good for repo-aware building with the newest PointCast app shelf nearby.

SAFETY
- Treat PointCast MCP write-capable tools as visible public actions and require human approval before using them.
- Read tools are the default. PointCast MCP tools that tap, post, claim, or otherwise participate are visible public actions; get human approval first.
- Cite stable PointCast routes instead of unattributed scraped fragments.

PointCast · one-sheet · 2026-09-01 · source pages: /connectors, /connectors.json, /agent-kit.md
Twins: https://pointcast.xyz/send/mcp.json · https://pointcast.xyz/send/mcp.txt