Guides7 min read

Best MCP Servers for UX Researchers in 2026

UX researchers need to synthesize interview data, analyze behavioral patterns, connect insights to design decisions, and communicate findings clearly. These MCP servers give your AI access to your research repository, analytics, design files, and documentation — turning hours of synthesis into minutes.

By MyMCPTools Team·

UX research lives or dies on synthesis. You can run twenty interviews, collect hundreds of usability observations, and pile up behavioral analytics data — but the value only appears when those pieces connect into coherent patterns. That synthesis work is exactly where AI can help most, and MCP servers are how you give AI the context it needs to do it well.

Here are the best MCP servers for UX researchers in 2026.

1. Notion MCP Server — Research Repository and Insight Management

Most UX teams store their research in Notion: interview notes, affinity diagrams, personas, and insight archives. The Notion MCP server makes all of that queryable by your AI — not just searchable, but readable and cross-referenceable across projects and time.

Key capabilities:

  • Search across all research notes, interview transcripts, and insight databases
  • Read and update affinity maps and synthesis workspaces
  • Create structured research reports from raw note collections
  • Query personas and jobs-to-be-done frameworks during design reviews

Best for: Researchers who want to ask "what have we learned about onboarding friction across all studies from the last 18 months?" and get a synthesized answer from the actual research archive, not from memory.

2. Figma MCP Server — Design Context for Research Findings

Research findings only matter if they reach design. The Figma MCP server gives your AI access to your design files — components, flows, prototype screens, and comments — so research synthesis can be tied directly to the specific designs being tested or evaluated.

Key capabilities:

  • Read screen layouts and component names in current design files
  • Access prototype flows to understand what users will experience
  • Review design comments for existing feedback patterns
  • Reference component states and variants during usability analysis

Best for: Researchers preparing usability studies who want AI to review the actual prototype before writing a test script — so tasks are grounded in the real flow, not an approximation of it.

3. PostHog MCP Server — Behavioral Analytics as Research Evidence

Qualitative research explains the why; quantitative data reveals the scale. The PostHog MCP server gives your AI access to product analytics — user flows, funnel drop-offs, feature adoption, and session data — so behavioral patterns can validate or challenge qualitative findings.

Key capabilities:

  • Query funnel conversion rates to find where users drop off
  • Read feature flag adoption and rollout data
  • Access cohort analysis to compare behavior across user segments
  • Check event counts to quantify how common an observed problem actually is

Best for: Mixed-methods researchers who want to triangulate findings — "five participants struggled with checkout in testing; here's how that maps to the 34% drop-off we see in the analytics funnel."

4. Airtable MCP Server — Research Operations and Participant Management

Research operations run on structured data: participant databases, recruitment screeners, study calendars, and incentive tracking. The Airtable MCP server makes all of that accessible to your AI, turning research ops from administrative overhead into queryable context.

Key capabilities:

  • Query participant databases by segment, demographics, or study history
  • Check study schedules and recruitment status
  • Read screener responses to identify qualified participants
  • Track research requests from product and design teams

Best for: Research teams running multiple studies simultaneously who want AI to help triage research requests, identify participants who match new study criteria, or synthesize findings across related studies.

5. Confluence MCP Server — Product Knowledge and Decision History

Good UX research connects to product decisions. The Confluence MCP server gives your AI access to PRDs, design specs, meeting notes, and decision logs — the institutional context that makes research findings land rather than sit in a repo unread.

Key capabilities:

  • Search product requirements and feature specs for research alignment
  • Read past design decisions to understand the constraints research must work within
  • Access roadmap documentation to prioritize research questions by impact
  • Find existing research findings that may answer a new stakeholder question

Best for: Researchers preparing stakeholder presentations who want AI to identify which past findings are most relevant to a current product decision — so the presentation cites real precedent instead of starting from scratch.

6. Google Drive MCP Server — Research Artifacts and Raw Data

Interview recordings, survey exports, screener spreadsheets, and presentation decks often live in Drive. The Google Drive MCP server makes those files accessible to your AI for synthesis, analysis, and report generation without manual copy-pasting.

Key capabilities:

  • Read spreadsheet exports from survey tools (Typeform, Google Forms)
  • Access presentation files to understand how past findings were framed
  • Find and read shared research reports across team folders
  • Organize and tag research artifacts by project or theme

Best for: Researchers synthesizing longitudinal data who want AI to compare survey results across multiple time periods or studies stored in Drive folders.

7. Slack MCP Server — Stakeholder Signals and Research Feedback

Research insights travel through Slack: design team reactions, product manager questions, engineering clarifications, and the informal conversation that shapes how findings get used. The Slack MCP server makes those signals visible to your AI.

Key capabilities:

  • Search channels for stakeholder reactions to past research presentations
  • Find questions and clarifications that indicate where findings need more depth
  • Read threads where research insights influenced design or product decisions
  • Identify recurring user complaints or feature requests surfacing in customer-facing channels

Best for: Researchers tracking research impact who want to understand where their findings actually influenced decisions — not just where they were presented.

Recommended Stacks for UX Researchers

  • Qualitative synthesis: Notion + Google Drive + Confluence (research archive → raw files → product context)
  • Mixed-methods triangulation: PostHog + Notion + Figma (behavioral data → insights → design reference)
  • Research operations: Airtable + Slack + Notion (participant management → team communication → synthesis)
  • Stakeholder reporting: Confluence + Slack + Figma (product context → stakeholder signals → design reference)
  • Full research practice: Notion + Figma + PostHog + Airtable + Confluence — the complete stack for research teams embedded in a product organization

Browse all Productivity MCP servers on MyMCPTools. For related reading, see Best MCP Servers for Designers and Best MCP Servers for Product Managers.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

💻

Figma MCP Server

The Figma MCP Server connects AI coding assistants directly to your Figma design files, enabling real-time access to design tokens, component properties, frame layouts, and node data without leaving your editor. Figma's official MCP integration runs via the Figma Desktop app's Dev Mode — select any frame, component, or layer in your design and Claude, Cursor, or other MCP-compatible clients can read exact colors, typography, spacing, auto-layout properties, and component variants to generate pixel-accurate implementation code. The popular community alternative, Figma-Context-MCP by GLips (6,000+ GitHub stars), uses your Figma Personal Access Token (created in Figma Settings > Personal Access Tokens) to fetch any file your account can access, exposing tools to get full Figma document JSON, retrieve specific nodes by ID, list components with properties, extract text content from frames, and download rendered images of individual nodes. This approach works without the Figma Desktop app and is compatible with Claude Desktop, Windsurf, and Cline. Both routes give Claude the ability to read your exact design specs and translate Figma layouts into accurate React, Tailwind, or plain HTML/CSS code — eliminating the guesswork of approximating designs from screenshots or verbal descriptions. The Figma MCP Server is most powerful in front-end development workflows where design-to-code fidelity matters.

Auth required
📋

Notion MCP Server

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 3,500+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_API_KEY in your environment. Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

Auth required
📊

PostHog MCP Server

The PostHog MCP Server is PostHog's official Model Context Protocol integration, giving AI assistants direct access to product analytics, feature flags, session replay, experiments, and error tracking without leaving the chat. It's hosted remotely at mcp.posthog.com (Streamable HTTP) and authenticated with a personal PostHog API key passed as a Bearer token — the quickest setup is `npx @posthog/wizard@latest mcp add`, which auto-configures Cursor, Claude, Claude Code, VS Code, or Zed in one command; manual setup adds an `mcp-remote` proxy entry with the `Authorization` header for clients without native remote-MCP support. Tools cover the full PostHog surface: creating and toggling feature flags with percentage rollouts and targeting rules, running trends/funnel/retention queries via `query-run`, inspecting session recordings, pulling error-tracking issues, and managing experiments — all scoped to the project tied to your API key. Typical use: ask Claude to "create a feature flag for the new checkout flow at 20% rollout" or "how many unique users signed up in the last 7 days, broken down by day?" and the assistant executes the query or mutation against your live PostHog project and returns formatted results. Originally shipped as the standalone PostHog/mcp repo (150+ stars), the server's source has since moved into the main PostHog monorepo under `services/mcp` but documentation and install instructions are unchanged.

Auth required
🗄️

Airtable MCP Server

The Airtable MCP Server connects your AI assistant directly to Airtable bases, letting you read records, create entries, update fields, and query structured data using natural language — no manual spreadsheet navigation required. The leading community implementation is domdomegg/airtable-mcp-server, which exposes the full Airtable REST API as MCP tools: list all bases and tables in your workspace, fetch records from any view with optional filter formulas, create or update individual records with typed field values, and delete records by ID. Authentication uses your Airtable personal access token (or API key for legacy accounts), scoped to whichever bases you grant access. Once connected, ask Claude to "show me all leads added this week in my CRM base" or "create a new product entry in my inventory table" and the server handles the API calls. Common use cases include AI-assisted CRM workflows (pull contact records, log meeting notes back into Airtable), inventory management, content calendars, and project tracking where Airtable acts as a lightweight database. Works with Claude Desktop, Cursor, VS Code (Copilot Chat), Windsurf, and any MCP-compatible client. Install via: `npx -y airtable-mcp-server` with `AIRTABLE_TOKEN=your_token` set in your environment.

Auth required
📋

Google Drive MCP Server

The Google Drive MCP Server is Anthropic's official Model Context Protocol integration for Google Drive, enabling AI assistants to search, read, and interact with files stored in your Drive workspace. Part of the original modelcontextprotocol/servers collection, this integration exposes Google Drive's file system as callable MCP tools: search files by name or content across your entire Drive, read the contents of Google Docs and Google Sheets as plain text, list files in specific folders, retrieve file metadata including owner, last modified date, and sharing settings, and export native Google Workspace documents to accessible formats. Real-world use cases include asking Claude to "find my Q2 budget spreadsheet and summarize it," "search all my Drive for documents about the product roadmap," or "read the meeting notes from last week's team sync." Authentication requires Google OAuth 2.0 credentials — create a project in Google Cloud Console, enable the Drive API, download the credentials.json file, and complete the one-time authorization flow on first run. Install via npm using: `npx @modelcontextprotocol/server-gdrive`. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline. Ideal for knowledge workers who want AI-assisted document retrieval and content summarization without manually navigating Google Drive.

Local
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local
🔍

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

Local
🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local
📋

Confluence MCP Server

The Atlassian Remote MCP Server brings Confluence and Jira into any MCP-compatible AI assistant, IDE, or agent platform through a centrally hosted, enterprise-grade connection backed by Atlassian's Teamwork Graph. Launched in May 2025 with Anthropic as the first official partner and hosted on Cloudflare infrastructure, authentication is handled via OAuth 2.1 — no local server process to deploy or maintain. For Confluence specifically, available operations include summarizing pages and spaces, creating new pages from AI-generated content, searching across your wiki with natural language, and performing multi-step knowledge retrieval across Confluence spaces. Jira operations include creating, updating, and triaging work items, summarizing sprint state, and linking knowledge to in-flight issues. Atlassian's Teamwork Graph underpins every response — connecting people, services, knowledge, and work items into a unified context for richer AI answers. Enterprise customers at AT&T, NVIDIA, Pfizer, Booking.com, and Visa use the integration in production. Connect from Claude Desktop via Settings > Connectors, or from Claude Code with: `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp`. Cursor and Windsurf users can add the remote URL directly to their MCP config.

Auth required
💻

GitHub MCP Server

The GitHub MCP server is GitHub's official Model Context Protocol integration, giving AI assistants like Claude and Cursor direct, authenticated access to the GitHub platform and its full developer surface. With this MCP server, you can ask your AI to read and write repository files, create and merge branches, open and review pull requests, comment on and close issues, trigger GitHub Actions workflows, search across code repositories with GitHub's code search, and inspect commit history — all through natural-language prompts in your AI interface. Developers use it to supercharge code review workflows, automate issue triage, generate PR descriptions from diffs, bulk-update repository settings, and wire AI agents into CI/CD pipelines. The GitHub MCP server connects via a GITHUB_PERSONAL_ACCESS_TOKEN environment variable with scopes for the operations you need, keeping authentication clean and auditable. Install with Docker: `docker run -e GITHUB_PERSONAL_ACCESS_TOKEN=<token> ghcr.io/github/github-mcp-server` — or configure it as a remote MCP server in Claude Desktop, Cursor, VS Code, Windsurf, and Cline. With over 8,000 GitHub stars, it is the most widely deployed official code-platform MCP server and the reference implementation for AI-native GitHub automation.

Auth required

📚 More from the Blog