MCP Connector

BuildYourWolfpack MCP Connector

The BuildYourWolfpack MCP endpoint exposes the Infinite Game and pack platform to AI assistants and connector platforms (including Meta's Muse) via the Model Context Protocol.

Endpoint

  • URL: https://buildyourwolfpack-1.onrender.com/mcp
  • Transport: Streamable HTTP — POST one JSON-RPC 2.0 message per request (protocol version 2025-03-26). Stateless: no session header required.
  • Methods: initialize, tools/list, tools/call, ping

Authentication

Every request requires a per-account API key:

Authorization: Bearer wmk_<your-key>

Keys are tied to your BuildYourWolfpack game account and can be revoked on request. An OAuth 2.1 upgrade path is planned. Requests are rate-limited per key (60/min).

Reviewers: to request a test account with representative data (mid-tier player, missions in progress), email dominiqueharris@picdigroup.com with subject "MCP reviewer access". Credentials are issued via secure channel only — never posted publicly.

Tools

Missions

  • list_missions — list the 40 mission steps; optional filters: sector (BUILD/MEASURE/LEARN), status (HUNT/CHASE/FEAST).
  • get_mission — full detail for one step (1–40): objective, deliverables, acceptance criteria, pace and approach options, base IVP.
  • start_mission — commits to a step (HUNT→CHASE). Declares its credit cost and requires an explicit confirmation token before any credit is spent — no spend without approval.
  • submit_mission_result — submit a deliverable for validation against the step's acceptance criteria (CHASE→FEAST, awards IVP). Steps that require real-world action return awaiting_human_confirmation and are never auto-completed by an agent.

Player

  • get_player_status — wolf name, IVP, level, tier (Lone Wolf → Pack Member → Hunter → Alpha), Pack Points, credit balance, tiles completed n/40.
  • get_referral_info — your referral code, redemptions, Pack Points earned from referrals.

Pack

  • get_my_pack — your pack. On first call, your pack is provisioned with the starter trio (idempotent — repeat calls never duplicate).
  • get_pack_board — your pack's board: members, mission, and progress.

Pack Hubs

  • list_pack_hubs — pilot café list (optional city filter). Every response includes "pilot": true; Pack Hub presence is in pilot — confirm directly with the café.

Safety & privacy

  • Every call resolves to exactly one account — your API key is your identity; no cross-account reads are possible.
  • Agents never self-attest real-world mission steps; physical actions require your own confirmation.
  • The connector never stores platform credentials or payment instruments. Coffee checkout stays on native Shopify rails.

Connect from Kimi Code

Kimi Code users can add the connector directly — no listing or review needed:

kimi mcp add --transport http buildyourwolfpack https://buildyourwolfpack-1.onrender.com/mcp --header "Authorization: Bearer <your-api-key>"

or via config file (~/.kimi-code/mcp.json):

{
  "mcpServers": {
    "buildyourwolfpack": {
      "url": "https://buildyourwolfpack-1.onrender.com/mcp",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Any MCP client that supports Streamable HTTP + custom headers works the same way: point it at the endpoint URL with the Authorization header.