Set up with a coding agent
Give a coding agent the Site's install prompt and point it at these docs. The agent should inspect your application and propose the smallest framework-appropriate change; you review it before deployment.
Copy the install prompt
- Open the dashboard, select the Site and go to Settings › Channels.
- Choose Review installation prompt.
- Copy the prompt, or use Open in Cursor, Open in Claude Code or Open in Codex.
- Review the agent's identity source, consent behaviour, Content Security Policy changes and test results before you merge.
The prompt is generated from the Site's public configuration: the Telltale server's address, the publishable key and the Site's website addresses. It follows your answer to "Does your site show a cookie or consent banner?" on the same page. The default answer, no banner, keeps the hosted tag's default of recording on page load; until you save an answer, the prompt also asks the agent to hold the tag if it finds a consent manager after all. With a banner, it holds collection with data-telltale-wait-for-consent (or waitForConsent: true) and wires optIn() and optOut(). EU and UK sites usually need a consent banner and should hold. It always asks the agent to tell Telltale who is signed in from your server (identify({sessionToken, userId, accountId}) with the server adapter after sign-in). It never contains a server key. The Open in links put the whole prompt, including the publishable key, in a link handled by that third-party application; choose Copy when you want to review or control what is passed on. A link is omitted when the prompt exceeds the vendor's documented length limit.
Pick a documentation source
| Task | Source |
|---|---|
| Install the browser SDK | https://app.trytelltale.dev/docs/sdk.md |
| Connect a consent manager | https://app.trytelltale.dev/docs/consent.md |
| Handle errors and retries | https://app.trytelltale.dev/docs/errors.md |
| Record agent tool calls through your MCP server | https://app.trytelltale.dev/docs/mcp.md |
| Record agent calls to your own API | https://app.trytelltale.dev/docs/api-channel.md |
| Generate or inspect HTTP clients | https://app.trytelltale.dev/openapi.json |
| Find relevant pages | https://app.trytelltale.dev/llms.txt |
| Read everything at once | https://app.trytelltale.dev/llms-full.txt |
| Retrieve selected pages on demand | Docs MCP server at https://app.trytelltale.dev/mcp |
Every guide is also served as Markdown when the request sends Accept: text/markdown, and at the same path with a .md suffix.
Add the docs MCP server
The docs MCP server is read-only, needs no key and returns public documentation only. It offers two tools: list-pages and get-page. get-page takes a slug or the exact path from list-pages (slug or path "/" returns the grouped index) and returns the Markdown as both markdown and content. It speaks Streamable HTTP with JSON responses and supports MCP protocol versions 2026-07-28, 2025-11-25 and 2025-06-18.
Claude Code:
claude mcp add --transport http telltale-docs https://app.trytelltale.dev/mcpCursor: Install in Cursor. VS Code: Install in VS Code. Claude Code: Install in Claude Code (shows the command above).
Each install page links to the IDE's own install handler, which asks before it saves the server. Discovery metadata is published at https://app.trytelltale.dev/.well-known/mcp/server-card.json and the API catalog at https://app.trytelltale.dev/.well-known/api-catalog.
/mcpNo key neededAsk for consent-controlled collection
Tell the agent which consent manager you use, the exact category, group, purpose or vendor that covers Telltale, and which code owns authentication. Ask it to:
- install the SDK held (data-telltale-wait-for-consent on the hosted tag, or waitForConsent: true in init(); the tag records on page load without it) before any other installer can start it;
- add one page-owned consent bridge (Consent bridge guide) and the matching CMP recipe, applying the saved decision on every full page load and continuing updates afterwards: approval calls optIn(), refusal or withdrawal calls optOut(), and an unknown initial choice stays held;
- reconnect identity through the existing auth owner with connectIdentity, so reapproval reads current authentication instead of replaying a cached identity;
- follow the React and Next.js or Vue and Nuxt placement guide rather than adding a framework package, keep browser globals out of server rendering, and clean up component subscriptions;
- keep a single installation owner: remove a managed Zaraz installation before adding direct CMP control, and in Google Tag Manager use the template's Let my CMP control collection mode.
Ask it to verify the held start, grant, withdrawal during pending work, reapproval with current identity, logout and account switch, reload and SPA navigation, and token submission to the backend, and to report what it could not test.