Skip to main content
The Parlay MCP server exposes 63 tools, organized into 10 domains. Tools that incur AI cost or take noticeable time are flagged.
Cost notation: $0 = read or static, ¢ = under one cent per call, $$ = a few cents. Latency notation: fast = under 1s, medium = 1–10s, slow = 10–90s, very slow = up to 5 min.

Reference data (6 tools)

Cheap reads, no AI cost. Use these to validate slugs before passing them to other tools.

Orgs (4 tools)

Reps (5 tools)

Analyses (5 tools)

Rep intelligence (8 tools)

The assign_* and generate_* calls are async with internal polling. Default timeout: 3 min for analysis_ids path, 10 min for recording_urls path.

Scout chat (3 tools)

Multi-turn coaching chat scoped to a single completed analysis. History is persisted server-side per analysis.

Playbooks (5 tools)

Playbook source materials + AI drafting (4 tools)

Custom prompts (5 tools)

Org-level prompts injected into every analysis. Distinct from playbooks: prompts are many short focused criteria, each scored separately.

Dispositions (4 tools)

Tag the outcome (sold / lost / canceled / undispositioned) of an analysis. Lets org insights correlate scoring patterns to deal outcomes.

Org insights + leaderboard (4 tools)

Org-level rollups across every rep + every analysis. The async generate_org_insights runs a Gemini meta-analysis; get_leaderboard is pure SQL with no AI cost.

Webhooks (6 tools)

Connectivity diagnostic (1 tool)

Documentation lookup (3 tools)

These let the LLM answer “how does X work” questions by pulling content directly from docs.goparlay.io. Cached in memory per session — no separate Mintlify MCP needed.

What’s not in the catalog

Intentionally excluded — these stay REST-only:
  • Admin (/v1/admin/*) — creating partners, minting keys, suspending partners
  • Internal infra (/v1/internal/recover) — crash recovery scanner
  • Health / status / version endpoints
  • Webhook delivery log + replay (debug-focused; access via REST)
  • Raw chat history (the tool responses already carry state)
  • API key management (key creation/revocation is per-partner lifecycle, sensitive)

Tool-naming conventions

  • create_* — strict create (errors if duplicate)
  • create_or_update_* — upsert (used for orgs, reps that have stable partner-supplied ids)
  • get_* — fetch one by id
  • list_* — paginated collection
  • update_* — partial update (PATCH semantics)
  • archive_* — soft delete
  • assign_* — async AI classification
  • generate_* — async AI authoring
  • set_*_manually — manual override of an AI assignment
  • tag_* — apply a label / status
  • ask_* / get_*_questions / clear_* — Scout chat verbs
The LLM is good at picking the right tool from these prefixes alone. If you see it pick the wrong one, file an issue — usually the description needs a better hint.