@datadisco/mcp

One command to connect DataDisco's MCP server to your AI coding tools.

DataDisco's MCP lets your AI client read your personas, prototypes, and feedback, talk to personas in character, and generate new ones. This package writes the right configuration into each of your tools and gets out of the way — sign-in happens automatically in your browser on first use (OAuth, no API key to copy).

Quick start

npx @datadisco/mcp

Pick your tools from the list and you're done. Restart the tool, and on first use your browser opens to sign in to DataDisco.

What it supports

| Tool | How it connects | | ----------------- | ---------------------------- | | Claude Code | native remote (HTTP + OAuth) | | Claude Desktop | mcp-remote bridge | | Cursor | native remote (HTTP + OAuth) | | VS Code (Copilot) | native remote (HTTP + OAuth) | | OpenAI Codex | native remote (HTTP + OAuth) | | Windsurf | native remote (HTTP + OAuth) | | Zed | native remote (HTTP + OAuth) |

Every tool except Claude Desktop is pointed straight at https://www.datadisco.com/mcp and runs the OAuth flow natively. Claude Desktop's config file accepts stdio servers only, so it uses mcp-remote, a small stdio↔HTTP bridge that runs the OAuth flow on its behalf.

Commands

npx @datadisco/mcp                 # interactive wizard
npx @datadisco/mcp install --all   # configure every known tool
npx @datadisco/mcp install --client claude-code --client cursor
npx @datadisco/mcp list            # show what's installed and configured
npx @datadisco/mcp remove --all    # remove the datadisco entry everywhere

Options

• --client <id> — target a specific tool (repeatable). Ids: claude-code, claude-desktop, cursor, vscode, codex, windsurf, zed.
• --all — every known tool.
• --project — write project-scoped config in the current directory (Claude Code, Cursor, VS Code, Zed).
• --url <url> — point at a different DataDisco environment (default https://www.datadisco.com/mcp).
• --dry-run — show what would change without writing.

Manual configuration

Prefer to wire it up yourself? Add one of the following.

HTTP transport with an explicit type (Claude Code, VS Code):

{ "type": "http", "url": "https://www.datadisco.com/mcp" }

URL only (Cursor, Zed):

{ "url": "https://www.datadisco.com/mcp" }

Windsurf uses serverUrl:

{ "serverUrl": "https://www.datadisco.com/mcp" }

Codex (TOML, in ~/.codex/config.toml):

[mcp_servers.datadisco]
url = "https://www.datadisco.com/mcp"

Claude Desktop's config accepts stdio servers only, so use the mcp-remote bridge:

{ "command": "npx", "args": ["-y", "mcp-remote", "https://www.datadisco.com/mcp"] }

Each tool nests this differently (mcpServers, servers, context_servers, [mcp_servers.*]); the installer handles those details for you.

Notes

• The installer only writes config — it never sees your credentials. Sign-in uses DataDisco's OAuth flow in your browser.
• Existing config is merged, not overwritten. Before changing a file that already exists, a backup is written beside it (e.g. ~/.claude.json.datadisco.bak); brand-new files have nothing to back up. A config file that isn't valid JSON/TOML is left untouched and reported as failed.
• Native remote MCP support in some tools is still evolving; if a tool fails to connect, please open an issue.
• For scripting/CI, use install --all or install --client <id> — the bare wizard needs a terminal. Commands exit non-zero if a selected tool can't be configured.

License

MIT