Integrations overview

You've learned how to research, publish, collaborate in teams, and participate in the community. Integrations are for when you want Parallect inside the tools you already use—IDEs, desktop assistants, automation, or your own backends.

This section is power-user territory: API keys, config files, and protocols. Take it step by step; each guide below stands alone.

What's available

Parallect supports:

• Cursor — MCP setup from the Integrations page with copy-paste config.
• Claude Code — One-command MCP setup via CLI, with API key or zero-config OAuth.
• Claude Desktop — MCP with platform-specific config file locations.
• OpenClaw — Download a SKILL.md to teach compatible setups how to use Parallect.
• REST API — Programmatic access for custom workflows; uses API keys like the MCP integrations.

The Integrations page in the app surfaces cards for Cursor, Claude Code, OpenClaw, and Claude Desktop with setup dialogs—start there when you want guided steps.

MCP in plain terms

MCP (Model Context Protocol) is a way for AI agents—like the assistant in your IDE—to call tools on your behalf. When you connect Parallect via MCP, those agents can use Parallect as a tool: kicking off research, pulling context, or whatever the server exposes, depending on version and permissions.

You don't need to memorize the protocol. Practically: install config + API key → your client talks to Parallect's MCP server.

MCP server URL: https://parallect.ai/api/mcp/mcp

REST API for custom integrations

For scripts, backends, or products that aren't MCP-native, use the REST API. You'll create API keys in Parallect, send them on requests, and integrate with the endpoints documented in the API reference. Keys are sensitive—treat them like passwords.

Choose your path

For protocol-level detail, the MCP integration and REST API references go deeper than this user guide.