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

There are three different Figma MCP servers and the install command on most listings belongs to the one Figma no longer leads with, so start with which you are choosing. **Figma's recommended server is now the hosted remote one at `https://mcp.figma.com/mcp`** — nothing to install, OAuth in the client, attached with `claude mcp add --transport http figma https://mcp.figma.com/mcp`. It is also the only one with the write and cross-file tools (`use_figma`, `generate_figma_design`, `generate_diagram`, `create_new_file`, `search_design_system`, asset upload and download). **The Dev Mode desktop server ships inside the Figma Desktop app** — enable it in Dev Mode (Shift+D) from the MCP server section of the inspect panel and the app opens a local endpoint at `http://127.0.0.1:3845/mcp`. Figma's docs now describe the desktop server as being for specific organisation and enterprise cases and recommend the remote one instead. Because it runs in the app, it reads whatever you have selected on the canvas: exact colors, typography, spacing, auto-layout constraints, component variants, and — the part a token-based reader cannot do — your Code Connect mappings, so it emits your component names rather than generic divs. It requires a Dev or Full seat on a paid plan and the desktop app must be open. The repository linked here is `figma/mcp-server-guide`, Figma's own setup guide; Figma does not publish the server's source. **The community alternative is Figma-Context-MCP by GLips** (15,500+ stars), installed as `npx figma-developer-mcp --figma-api-key=YOUR_FIGMA_ACCESS_TOKEN`. It authenticates with a Personal Access Token from Figma Settings → Personal Access Tokens and calls the REST API, so it needs no desktop app, works headlessly in CI, and can read any file your account can open — including from a free plan. It exposes the document JSON, node lookup by ID, component listing, text extraction, and rendered-image download. The practical split: pick the official server when design-to-code fidelity and Code Connect matter and you are already paying for Dev Mode; pick GLips when you need automation, a free plan, or a machine with no Figma app installed. Both let an assistant translate a frame into accurate React, Tailwind, or plain HTML/CSS instead of guessing from a screenshot.

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 4,580+ 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_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). 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), that repository is now archived on GitHub — last pushed 2026-01-19 — with the source moved into the main PostHog monorepo under `services/mcp`. The archive is a relocation, not a retirement: the hosted server and the wizard install are both current, so the link here is a pointer to history and the docs at posthog.com/docs/model-context-protocol are the live reference.

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 an Airtable personal access token passed as AIRTABLE_API_KEY, scoped to whichever bases you grant access; the token needs at least the schema.bases:read and data.records:read scopes, plus the write scopes if you want the assistant to create or update anything. Airtable itself now also runs an official hosted MCP server at https://mcp.airtable.com/mcp, which uses OAuth instead of a token. 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_API_KEY=pat...` set in your environment.

Auth required📘
📋

Google Drive MCP Server

Anthropic's reference Model Context Protocol server for Google Drive — and a retired one, which is the first thing to know about it. The repository moved to modelcontextprotocol/servers-archived and was archived on 2025-05-28 with no commits since, while the npm package @modelcontextprotocol/server-gdrive stays published at 2025.1.14, so `npx @modelcontextprotocol/server-gdrive` still installs and runs without warning you. It is also much smaller than its reputation. The server exposes exactly one tool — `search`, which takes a query string and returns matching file names and MIME types. Everything else is MCP resources: files are addressed as `gdrive:///<file_id>`, with Google Workspace formats exported automatically (Docs to Markdown, Sheets to CSV, Presentations to plain text, Drawings to PNG) and all other file types served in their native format. Clients that do not surface resources well therefore look like the server is broken when it is behaving exactly as documented. Authentication is read-only by construction: the setup asks for the `https://www.googleapis.com/auth/drive.readonly` scope on an OAuth Client ID of type Desktop App, which means there is no tool here that can create, edit, move or reshare anything. The flow is manual — create a Google Cloud project, enable the Drive API, configure the consent screen, download the client key file, rename it to `gcp-oauth.keys.json` in the repo root, then run `node ./dist auth` once to write `.gdrive-server-credentials.json` beside it; a Docker path exists that mounts the key file and persists credentials in an `mcp-gdrive` volume. For maintained Drive access with writes, sharing controls and shared-drive support, the community server most teams move to is taylorwilsdon/google_workspace_mcp (PyPI `workspace-mcp`), which covers Drive as one of twelve Google Workspace services on a single connection. See the setup guide on this page for the full comparison.

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/authv2`. Cursor and Windsurf users can add the remote URL directly to their MCP config.

Auth required📘
💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘

📚 More from the Blog