# Encore MCP

Encore is an agent-native studio for gathering context:
projects, flows with their welcome and ending, the instruments (Questions,
Moodboards, Comparisons), sessions with every answer whole, and visual
verification. Pages are retired; existing pages stay readable through get_page.
Briefs are retired (5.0.0): every answer comes back whole through
read_session_results, and list_activity says what came back across the studio
since a moment (5.1.0). get_project returns each flow as the studio's project
page shows it: its steps in order, live or draft, and how many finished (5.2.0).

Canonical MCP resource: https://mcp.encorehq.co/mcp
Authentication: OAuth 2.1 authorization code + PKCE S256. CIMD is preferred;
Dynamic Client Registration remains supported for compatibility.

Connect to the canonical resource above — that is the whole consumer story. The
connection serves a curated 48-tool core (discovery, projects, pieces, flows, client, vision, plus the
always-present studio identity and link-domain reads), and the ENTIRE 93-tool
surface stays reachable at runtime: list_encore_tools searches the registry with schemas on
demand, and run_encore_tool validates and executes any returned tool through its existing
handler. Scopes, tenancy, entitlement, audit, teaching errors, and confirmation-token
contracts are identical through the gateway. If a goal is still out of reach, file
report_agent_blocker — reports drive promotion into the core.

Deterministic pinning (CI, gates, scripted agents): a path-form resource such as
https://mcp.encorehq.co/mcp/ts/pages,library replaces the core with discovery plus exactly the
selected toolsets, and the URL is itself the OAuth resource. The legacy ?toolsets= query form
(and its ?features= alias) remains accepted. Unknown selections fail loudly with a teaching
400; empty or omitted selections serve the core. Pinning is an operator tool, not a consumer
step — humans connecting Encore should never need to compose a URL.

## Toolsets

- discovery: Find Encore capabilities and choose the toolsets needed for the work. (5 tools)
- projects: Manage the complete lifecycle of projects, including Trash and restore. (7 tools)
- pieces: Manage the instruments: Questions, Moodboards and Comparisons. Existing pages are listed read-only. (5 tools)
- flows: Build ordered flows; set pacing and the fixed welcome and ending; check readiness and previews; publish and unpublish (update_flow status). (10 tools)
- client: Run the loop with the people you ask: links, sessions, answers, exports, and what came back since. (13 tools)
- vision: Visually verify instruments and flows (including the flow welcome and ending) at mobile or desktop size. (2 tools)
- pages: Read existing page documents (read-only; pages are retired and cannot be created or changed). (1 tools)
- questions: Discover question grammars, manage questions, and read bounded response summaries. (10 tools)
- canvas: Read or atomically replace a versioned flow canvas. (2 tools)
- library: Manage project images, image sets, templates, stock search, and context: add or remove sources, draft, edit and approve the business context, turn its gaps into flow questions or dismiss them. (26 tools)
- settings: Read studio, domain, team, and workspace settings; update safe studio defaults, the studio profile (about, services, voice, colours, past work), and your own email switches. (11 tools)
- studio: Search work across the connected studio. (1 tools)

Machine changelog: https://mcp.encorehq.co/.well-known/mcp-changelog.json
Human reference: https://encorehq.co