Condens Remote MCP Server
Remote MCP server for connecting to your Condens UX repository.
Install
$ agentstack add mcp-condens-remote-mcp-server ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v1.0.1 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v1.0.1. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/mcp-condens-remote-mcp-server) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 [hello@condens.io](mailto:hello@condens.io)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: condens
- Source: condens/remote-mcp-server
- License: MIT
- Homepage: https://condens.io/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v1.0.1 Imported from the upstream source.