Condens Remote MCP Server
Pull UX research, insights, and repository context from Condens into your agent while exploring product direction.
Overview
Condens Remote MCP Server is an MCP server for the Idea phase that connects your AI assistant to your Condens UX research repository.
What is this MCP server?
- Streamable HTTP remote MCP with tenant-specific base URL
- Connects to your Condens UX repository from the agent
- Admin MCP URL in Condens Settings > API & MCP-Server
- US or EU API host choice (api.condens.io / api-us.condens.io)
- Registry v1.0.1 with setup docs on condens.io help center
- MCP registry version 1.0.1
- Two regional API base URL choices documented
What problem does it solve?
Builders doing UX discovery still manually export or paste research from Condens instead of letting the agent query the live repository.
Who is it for?
Solo builders with a Condens workspace who want agent-driven synthesis of existing usability and interview research.
Skip if: Teams without Condens, or pure code-only repos with no UX research practice.
What do I get? / Deliverables
After configuring your tenant MCP URL, your agent can ground answers in Condens UX data while you research problems and audiences.
- Agent-grounded answers from Condens research content
- Faster synthesis of UX insights during discovery
Recommended MCP Servers
Journey fit
Condens is a UX repository; connecting it over MCP supports early journey research before you commit to build specs. Research is the right shelf when the server’s job is to query and synthesize existing user-research artifacts rather than ship code.
How it compares
UX repository MCP bridge, not a Figma codegen skill or generic GitHub MCP.
Common Questions / FAQ
Who is io.condens/remote-mcp-server for?
It is for Condens customers—especially indie PM-designers—who want MCP access to their UX repository from coding agents.
When should I use io.condens/remote-mcp-server?
Use it during idea validation and research synthesis when answers should cite Condens insights, tags, or study structure.
How do I add io.condens/remote-mcp-server to my agent?
Copy your workspace MCP URL from Condens settings, set baseUrl to api.condens.io or api-us.condens.io as directed, and add the streamable HTTP remote in your MCP config.