A chat connector (MCP server) connects one of your own tool accounts to RShift Sites, in the project chat and in Chats. Once connected, RShift Sites can look things up in that tool while it works for you: your Notion docs, your Linear tickets, your Miro boards. You describe what you want, and RShift Sites grounds the result in your real content instead of guessing.
Chat connections are personal. You sign in with your own account, only you can use the connection, and it does not become part of the app you publish. Chat connectors are built on MCP (Model Context Protocol), an open standard that connects AI systems like RShift Sites to external tools. You don’t need to know anything about MCP to use them.
RShift Sites includes prebuilt chat connectors for popular tools and supports custom MCP servers on all plans. The RShift Sites static IPs connection option for custom MCP servers is the one Enterprise-only exception. Workspaces can also add MCP registries, browsable directories of MCP servers that members connect as chat connectors without entering URLs.
Why use chat connectors
Chat connectors unlock two key capabilities:
- Bring your existing context into RShift Sites.
RShift Sites can read your team’s documentation, tickets, and design files to build prototypes and flows aligned with your standards. - Connect your work in RShift Sites back to your workflows.
RShift Sites can take follow-up actions in your connected tools, such as updating ticket statuses, adding prototype links as comments, or creating new items when supported.
RShift Sites becomes more powerful when it understands your team’s world, eliminating guesswork and speeding up iteration.
Here is what that looks like in practice:
| Scenario | Example prompt | Example outcome |
|---|---|---|
| A product manager connects Linear or Jira | Generate a prototype based on tickets in the current sprint. | RShift Sites reads issue descriptions and acceptance criteria to build aligned, testable UI. |
| A marketer connects Notion or Confluence | Turn our Q4 campaign brief into a landing page. | RShift Sites uses the document as context to generate an on-brand, editable page. |
| A designer connects Miro | Prototype the signup flow from our whiteboard. | RShift Sites reads flow diagrams to scaffold UI navigation and turns them into an interactive prototype your team can test. |
| An engineer connects n8n or an internal MCP server | Build a workflow UI that lists users and allows deleting them. | RShift Sites builds an app that uses live data and workflows. |
How chat connectors relate to RShift Sites’ other MCP features
RShift Sites uses MCP in three different ways, each connecting a different system for a different purpose. Chat connectors bring external tools into RShift Sites as context while you build.
| Feature | Direction | What it does |
|---|---|---|
| Chat connectors (this page) | RShift Sites uses external tools | RShift Sites pulls context from services such as Notion or Linear while you build |
| RShift Sites MCP server | AI tools build in RShift Sites | External AI tools create, edit, and manage your RShift Sites projects |
| Agent integrations | AI assistants use your app | Your users’ assistants call the actions you expose in your published app |
These uses also combine: a published RShift Sites app with an agent integration becomes a chat connector in its own workspace, listed under RShift Sites apps on the Connectors page. See Use your app in your chats.
How chat connections work
Chat connections behave differently from the other connection types in a few important ways:
- Personal to you. You connect with your own account, and only you can use or manage the connection. Teammates who want the same tool connect their own accounts.
- Chat only. RShift Sites uses the connection in the project chat and in Chats. It is not included in your published app, and your app’s visitors cannot reach the connected tool through it. If your published app itself needs the tool, use an app + chat connector.
- Read first, act when supported. RShift Sites can read structured content such as docs, issues, and diagrams. Where the tool supports it, RShift Sites can also take limited actions, such as creating or updating items.
- Available on all plans, everywhere you work with RShift Sites. Once connected, the tool is available as context across your projects and in Chats. Workspace admins can manage which chat connectors are available, described under Managing chat connectors.
Prebuilt chat connectors
RShift Sites includes prebuilt chat connectors for these tools. Expand one to see what connecting it unlocks:
Amplitude: product analytics and feedback
Turn user behavior into better product decisions.
Bring product insights, user funnels, and feedback into RShift Sites so you can iterate on flows, optimize layouts, and run experiments with a simple prompt. See the Amplitude MCP docs.
Atlassian: Jira issues and Confluence pages
Turn product documentation into working prototypes.
RShift Sites can read product documentation and linked Jira epics (PRDs, specs, architecture docs) to generate prototypes that match your team’s standards. Embed generated prototypes back into Confluence for feedback. See the Atlassian MCP docs.
Canva: designs, brand assets, and templates
Create and export visuals without leaving the chat.
RShift Sites can create and edit Canva designs, search your brand assets and templates, and export finished designs as PDF, PNG, or other formats. Some features, such as brand kits, need a Canva plan that includes them. See the Canva MCP docs.
Confidence: feature flags and experiment data
Build and iterate with real experimentation context.
RShift Sites can evaluate feature flags, read experiment results, and incorporate rollout logic into your apps, helping you ship features that are informed by real user experiments. See the Confidence MCP docs.
Granola: meeting notes, decisions, and action items
Turn meeting context into specs and tickets.
RShift Sites can search across past meetings, pull out decisions and action items, and use what was agreed to generate PRDs, user stories, or follow-up tasks, without digging through notes. See the Granola MCP docs.
Hex: notebooks and workspace data
Build apps powered by real analysis and data workflows.
RShift Sites can query Hex notebooks, explore datasets, and use results as context to generate data-driven apps, dashboards, and workflows aligned with your existing analyses. See the Hex MCP docs.
HeyGen: AI avatars, voices, and video generation
Generate AI avatars and videos directly from your RShift Sites apps.
RShift Sites can use HeyGen to create AI-generated avatar videos, voiceovers, and personalized video content as part of your apps and workflows. See the HeyGen MCP docs.
Linear: issues and project data
Prototype from real issues and tickets.
RShift Sites can read Linear issues, including descriptions and acceptance criteria, to generate functional prototypes. Attach resulting apps back to Linear for review. See the Linear MCP docs.
Miro: boards and diagrams
Bring your boards to life.
RShift Sites can convert user flows, wireframes, or information architecture from your boards into interactive prototypes you can test and export back for feedback. See the Miro MCP docs.
Notion: pages and databases
Build directly from your team’s Notion workspace.
RShift Sites can read PRDs, design specs, or marketing briefs and turn them into working apps, landing pages, or prototypes. Embed generated RShift Sites apps back into Notion for seamless collaboration. Need your published app to read or write Notion while people use it? Use the Notion app + chat connector instead. See the Notion MCP docs.
n8n: automation workflows
Build workflow-rich apps with live data.
Connect your n8n automations to RShift Sites to pull data from tools like HubSpot, Google Sheets, or Slack, and build user-facing apps powered by existing automations. See the n8n MCP docs.
Polar: billing, products, customers, and subscriptions
Build subscription-enabled apps with real billing context.
RShift Sites can use your Polar setup as context when scaffolding SaaS apps, checkout flows, pricing pages, subscription management, and customer billing experiences. See the Polar MCP docs.
PostHog: product analytics data
Turn product analytics into better features.
RShift Sites can query user behavior, analyze funnels and events, and use real usage insights to generate flows, features, and improvements grounded in how users actually interact with your product. See the PostHog MCP docs.
Sanity: CMS content and schemas
Build content-driven apps with your CMS data.
RShift Sites can read your Sanity documents, schemas, and structured content to generate apps, landing pages, and content management interfaces aligned with your content model. See the Sanity MCP docs.
Sentry: issues, errors, and project insights
Debug and monitor your apps with real error data.
RShift Sites can read Sentry issues, exceptions, and performance data to help you identify and fix problems faster. See the Sentry MCP docs.
Wispr Flow: meeting notes, summaries, and transcripts
Build from the decisions your team makes in meetings.
Wispr Flow Notetaker records your meetings and creates notes, summaries, and transcripts from them. RShift Sites can read that content and use it as context while you build. You need Notetaker and Cloud Sync enabled in your Wispr Flow account. See the Wispr Flow MCP docs.
How to add a prebuilt chat connector
To connect a prebuilt chat connector:
Select the connector
Open Connectors and select a chat connector, for example Notion or Linear. See Where to find connectors for every place you can open the catalog.
Add a connection
Click Add connection. If the connector supports more than one connection type, choose Chat connector.
Authorize
Sign in and grant RShift Sites access to your account.
Additional setup for specific chat connectors
In addition to these steps, you need to do the following in n8n:
- Go to Settings → MCP access and toggle Enable MCP access (requires instance owner or admin permissions)
- For each workflow you want to expose, go to Settings in the workflow editor and toggle Available in MCP.
If you plan to analyze your RShift Sites-built app, make sure it is already sending data to Amplitude before using the connector. See the Amplitude Quickstart guide for setup instructions.
Hex requires you to provide a custom server URL when connecting. For most users, the default URL is https://app.hex.tech/mcp. If you are on a single-tenant, EU multi-tenant, or HIPAA multi-tenant instance, replace app.hex.tech with your custom Hex domain (for example, https://your-company.hex.tech/mcp or https://eu.hex.tech/mcp).
Custom MCP servers
If a tool isn’t in the catalog but offers an MCP server, you can still connect it. Custom MCP servers bring internal or third-party systems into RShift Sites as chat connectors, which is perfect for private APIs, internal CRMs, or custom data sources. See Connect a custom MCP server for setup steps, authentication options, and admin controls.
Managing chat connectors in your workspace
Chat connections are personal, so you review or revoke your own connections anytime in Connectors, which you can also reach from inside a project, as described in Where to find connectors.
Chat connectors, including custom MCP servers, are enabled by default on all plans, including Enterprise. The RShift Sites static IPs connection option for custom MCP servers is the exception: it requires an Enterprise plan.
On Business and Enterprise plans, workspace admins and owners can turn chat connectors off for the whole workspace or disable individual ones. See Chat connector controls for the settings and where to find them.
FAQ
Can my teammates use my chat connection?
No. Chat connections are personal, so only you can use and manage yours. Teammates who want the same tool connect it themselves with their own accounts.
Is a chat connection part of my published app?
No. Chat connections only give RShift Sites context in the project chat and in Chats. Your published app and its visitors cannot reach the connected tool through them. If your app itself needs the tool, use an app + chat connector.
What’s the difference between a chat connector and an app + chat connector?
A chat connector (MCP server) uses your own account, is personal to you, and works only in the project chat and in Chats. An app + chat connector runs on one shared account and also works in your published app. The decision table on the overview shows when to pick each one.
Why can’t I connect a chat connector?
A workspace admin may have disabled the connector, custom MCP servers, or all chat connectors for the workspace. See Chat connector controls for the settings and ask an admin to check them.