Condens Remote MCP Server
io.condensPublished by condens.iov1.0.1Updated Oct 24, 2026
Remote MCP server for connecting to your Condens UX repository.
The publisher's own server: Registry Mcp
Overview
Remote MCP server that connects AI assistants to a Condens UX research repository so they can search and read published research artifacts.
- What you can do
- List workspaces and published artifacts accessible to the authorized user, optionally filtered by workspace or artifact IDs, and retrieve artifact content as Markdown, including insights, reports and usability issues. Search published artifacts in natural language and get back matching artifact IDs. Access is read-only and scoped to the user's existing Condens permissions.
- When to use it
- Use it when you want an AI assistant or agent to ground its output in your team's validated customer research, for example drafting documents or designs backed by real insights, or answering questions from published Condens reports.
- Requirements
- A remote Streamable HTTP endpoint at the Condens MCP URL for your region (EU or US). A Condens account on a trial, Business or Enterprise plan, with an admin creating and configuring the MCP client. Each user authorizes via OAuth 2.0 with dynamic client registration and PKCE; no client IDs or secrets are copied. Some MCP clients need their own paid plan.
Installation
In SourceWeft
- Open Condens Remote MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Follow the launch instructions in the repository.
README
Condens MCP Server
Overview
The Condens MCP Server lets you connect MCP-compatible AI assistants, IDEs, and agent platforms to your Condens research repository. Once connected, you can search across your validated customer insights in natural language directly from the LLMs you already use, or let agents and workflows pull from research findings so whatever they produce is grounded in real customer knowledge.
Features
- Published Research Access - Search and retrieve published Condens Artifacts, including insights, reports, usability issues, and other research outputs
- Permission-Aware - Users only see data they already have access to in Condens
- Client Access Control - Admins control which MCP clients are available and can scope access by role, user group, or individual user
- OAuth 2.0 Authentication - Uses OAuth 2.0 authorization with support for dynamic client registration and PKCE
- Streamable HTTP Transport - Exposes the MCP server over Streamable HTTP at
/mcp
Available Tools
The server currently provides these read-only MCP tools:
- List Workspaces - Lists Condens Workspaces accessible to the authorized user
- List Published Artifacts - Lists accessible published Artifacts, optionally filtered by Workspace ID or Artifact IDs
- Get Artifacts - Retrieves Markdown content of Artifacts by ID
- Search Condens - Searches published Artifacts for content relevant to a user query and returns matching Artifact IDs
Getting Started
1. Set up the MCP client in Condens
Admins create and configure the MCP client in Condens under Settings > Account > API & MCP Server, including which users, roles, or groups are allowed to use it.
2. Add Condens MCP to your tool
In your MCP-compatible tool, add the Condens MCP server URL. Your URL depends on your Condens server region:
https://api.condens.io/mcpfor EUhttps://api-us.condens.io/mcpfor US
If you're unsure about your Condens server region, Admins can find the designated MCP URL in the API & MCP Server page.
Condens includes preconfigured MCP clients for Claude and ChatGPT. See the client-specific guides below for step-by-step instructions.
3. Authorize the connection on user-level
Each user authorizes the connection for their own Condens account via OAuth. Authorized non-admin users can find setup instructions in: Settings > Integrations > MCP Client > Show setup instructions.
Authentication uses OAuth 2.0 with Dynamic Client Registration. Compatible MCP clients register themselves during the authorization flow, so Condens does not provide manually generated client IDs or client secrets to copy into your MCP client.
Condens MCP currently supports remote MCP over Streamable HTTP. It does not support local stdio servers or SSE.
For full setup instructions, view our step-by-step setup guide.
Client-specific guides:
Availability
Condens MCP is available during the free 15-day trial and on Business and Enterprise plans.
Business plans can connect Condens to preconfigured AI assistants such as Claude and ChatGPT.
Enterprise plans can additionally connect Condens to custom MCP clients, including custom or company LLMs, automation agents, design assistants, knowledge assistants, and coding assistants.
Some MCP clients may require their own paid plan, such as Claude Pro or higher, or ChatGPT Plus or higher.
Security & Access Control
Condens Admins control which MCP clients are available for their organization. For each MCP client, Admins can configure who is allowed to use it by selecting roles, user groups, or individual users.
Only authorized users see the MCP client in their Integrations settings and can complete the OAuth authorization flow. Each user authorizes the MCP client for their own Condens account, so access remains scoped to that user's existing Condens permissions.
Admins can remove or deactivate an MCP client at any time. They can also change which users, roles, or groups have access; those changes limit who can continue using the MCP connection.
Support
For questions about Condens MCP setup, contact Condens via [email protected]
Source: README.md at commit 3a9eaaa
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Remote-Mcp integrations
Registry Mcp
com.remote-mcpOfficial publisher
Remote MCP server that lets an assistant search the official MCP registry and look up details on individual MCP servers.
Starmux — All-in-One Self-Hosted Remote MCP Server & Gateway
Published by GitHub account cookyecat
Self-hosted daemon that exposes filesystem, terminal, process and Git tools to AI clients over Streamable HTTP, and multiplexes other local MCP servers.
Remote MCP Server
Published by GitHub account CaSO44444
A remote MCP server hosted at a bare IP address, with no documented tools, description, or authentication details.
Sdp Remote Mcp
com.opentext
Official OpenText server embedded in Software Delivery Platform products, giving AI clients read and write access to backlogs, work items and delivery data.
ChromaDB Remote MCP Server
Published by GitHub account meloncafe
Self-hosted remote ChromaDB vector database server over streamable HTTP, letting assistants manage collections and documents and run semantic search.