Set up your agent

The simplest setup is to paste set up https://crowdlisten.com/SKILL.md into your agent. To install manually, use the instructions for your client below. Requires Node.js 22+.

Codex
Claude Code
Cursor
OpenClaw
Other assistants

codex mcp add crowdlisten -- npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness
npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness login --no-setup

Complete browser sign-in, then start a new Codex session. If a crowdlisten entry already exists, inspect it before replacing it.

claude mcp add --transport stdio --scope user crowdlisten -- npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness
npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness login --no-setup

Complete browser sign-in, restart Claude Code, then use /mcp to inspect the server. Preserve existing MCP connections.

Add this server to ~/.cursor/mcp.json, merging it with existing mcpServers entries:

{
  "mcpServers": {
    "crowdlisten": {
      "command": "npx",
      "args": ["-y", "-p", "@crowdlisten/harness@2.3.2", "crowdlisten-harness"]
    }
  }
}

Then sign in:

npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness login --no-setup

Enable CrowdListen in Cursor’s MCP settings and start a new chat.

Find the existing workspace for the agent you are using. For the default agent:

openclaw config get agents.defaults.workspace

Replace the placeholder below with that existing absolute path. Do not create a new workspace just for setup.

npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness setup openclaw "/ABSOLUTE/PATH/TO/WORKSPACE"
npx -y -p @crowdlisten/harness@2.3.2 crowdlisten-harness login --no-setup

Start a new OpenClaw session and read its installed crowdlisten skill. It includes the pinned mcporter bridge and connection checks. Login alone does not install that bridge. See the OpenClaw reference.

Paste this into Muse, Grok Bot, Instinct, or another assistant:

set up https://crowdlisten.com/SKILL.md

The assistant must check which integrations it supports. If it cannot register an MCP server, use CrowdListen in the browser. A working browser session is not a persistent MCP connection.The remote MCP endpoint requires an authenticated account session header. It does not currently offer OAuth or anonymous URL-only installation. Do not paste session tokens into an assistant conversation.

Check from the connected client

Confirm that recall, analyze, and ingest are available, then run:

recall({ mode: "connection" })
recall({ mode: "workspaces" })

These reads do not start a model, collect sources, or spend credits. Choose an authorized workspace before reading private expertise.

Troubleshooting

No tools after setup: restart the client, inspect its MCP settings, and confirm Node.js 22+ is on its path.
Another account appears: run the browser login command again and select the intended CrowdListen account.
Existing configuration conflict: inspect the entry and preserve unrelated servers. The targeted harness installer, crowdlisten-harness setup --agent codex (or claude-code or cursor), reports conflicts instead of silently replacing custom settings.
A method or task is unavailable: verify workspace membership and ownership. Signing in does not grant access to someone else’s private methods.

Get started

Work with experts

Build

Updates

Check from the connected client

Troubleshooting

​Check from the connected client

​Troubleshooting

Check from the connected client

Troubleshooting