vTilt
By roleFoundersKnow what to fix firstMarketersSee what happens after the clickCMOsSee what your budget really buys
By businessSaaSTurn signups into active usersEcommerceSee why shoppers abandon cartsAgenciesProve your work to clientsEnterpriseOne customer record for every team
MeasureWeb AnalyticsFind where buyers leaveSession ReplaySee why they left, not just that they didAdsKnow what paid visitors do nextIntegrationsOne snippet feeds your stack
ThinkPeopleOne profile per customerCustomer MemoryvTilt remembers every visitorSite KnowledgeAnswers and audits from your own pages
ActAsk AIAnswers from real behaviorAI ChatChat that knows the visitorEmail CampaignsEmail from real visits
PricingWhy vTiltDocs
Docs / Website chat MCP servers
Getting Started
OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes
Guides
Event forwardingReverse proxyRealtime dashboardSite knowledgeStudioWebsite chat MCP
Frontend frameworks
Next.jsNuxt.jsVue.jsReactReact RouterRemixGatsbySvelte / SvelteKitAstroAngularTanStack StartDocusaurus
Backend frameworks
NestJSHonoCloudflare WorkersDjangoFlaskLaravelPhoenixRuby on Rails
Backend languages
PythonPHPRubyElixirGoJava.NET / C#Rust
Stack guides
Vue + PHP
API Reference
Browser SDK
Script bundlesAutocaptureWeb VitalsSession recordingChat widgetOutbound messagesCookie consentFeature readinessRemote configurationDebug logging
Node SDK
Install & setupCapture, identify & aliasContext & shutdownGlobal properties & opt-outError tracking
MCP server
Guides
OverviewAuthenticationOAuthAgent skills (prompts)AI intelligenceSite knowledgeGoogle AdsMeta Ads
Client setup
CursorClaude DesktopVS CodeChatGPTCodex

Getting Started

OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes

Guides

Event forwardingReverse proxyRealtime dashboardSite knowledgeStudioWebsite chat MCP

API Reference

MCP server

On this page

On this page

  • Prerequisites
  • Add a server
  • Auth modes
  • OAuth
  • Current page context
  • Security notes
  • Related
DocsGuidesWebsite chat MCP

Website chat MCP servers

Last updated October 13, 2026

Connect remote custom MCP servers so the visitor chat widget can answer page-specific questions.

Website chat MCP servers

Project admins can attach remote MCP servers to Channels → Website chat → MCP servers. The visitor AI assistant calls those tools when answering questions (for example, “tell me more about this property” on a listing page).

Important: This is separate from vTilt MCP. Website chat never exposes your analytics, persons, or ads tools to visitors. Only connect MCP servers that are safe for public visitors.

#Prerequisites

  • Website chat enabled for the project
  • AI assistant enabled
  • An HTTPS remote MCP endpoint (Streamable HTTP; SSE is used as a fallback)

#Add a server

  1. Open Channels → Website chat → MCP servers.
  2. Click Add server.
  3. Enter a name and the MCP URL (must be https://).
  4. Choose an auth mode (see below).
  5. Save, then Test (and Connect for OAuth).
  6. Enable the server (at most two enabled servers per project).

#Auth modes

ModeWhen to use
NonePublic MCP with no authentication
Bearer tokenServer expects Authorization: Bearer …
Custom headersNon-Bearer auth (API keys in headers, etc.) as a JSON object
OAuthMCP Authorization (browser Connect). Tokens are stored encrypted on the project

#OAuth

  1. Set auth to OAuth and save.
  2. Optionally paste a static client ID / secret if the authorization server does not support Client ID Metadata or Dynamic Client Registration.
  3. Click Connect — complete consent in the browser.
  4. When status shows connected, click Test to refresh the tool list.

If refresh fails later, the server shows Reconnect. Chat still answers from your system prompt and Site Knowledge while that server’s tools are skipped.

#Current page context

The chat widget sends the visitor’s current page URL and title with every message. The AI sees the full URL (including query string) so tools can resolve “this property” / “this listing” from the page the visitor is on.

#Security notes

  • Credentials never appear in the install snippet or /decide.
  • Prefer read-oriented MCP tools. Anything the model can call may run for any visitor who chats.
  • Private / localhost MCP URLs are rejected (SSRF protection).
  • Tool results are redacted for obvious secrets before the model sees them; visitors never see raw tool JSON.

#Related

  • Chat widget API
  • vTilt MCP overview (for Cursor / Claude — not for the visitor widget)
PreviousStudioGuidesNextNext.jsIntegration guides