Pearl Agent Plugin MCP Server

Pearl Agent Plugin

Pearl's installable package connects Codex, Claude, Cursor, and Grok Bot to Pearl's authenticated remote MCP server at https://agent.joinpearl.co/mcp.

Pearl Agent access currently requires active Pearl Elite membership. The server enforces eligibility and OAuth scopes; installing this package cannot widen access.

Package 0.8.7 is read-only. Runtime MCP tools/list is authoritative. The public package contains thin host manifests, current workflow guidance, public documentation, approved brand assets, a presentation-only MCP Apps resource, and zero-dependency validation. The resource is deployed and source-wired to five reviewed read tools, but final real-host rendering verification is still pending, so the package does not claim that any host renders it successfully. The package contains no application, OAuth server, database, executor, environment, deployment configuration, or credential.

Repository availability does not mean Anthropic, Cursor, or OpenAI has approved, endorsed, or listed Pearl.

Install

Codex Desktop and CLI

git clone --branch v0.8.7 --depth 1 https://github.com/Pearl-Passport/pearl-agent-plugin.git
cd pearl-agent-plugin
codex plugin marketplace add .
codex plugin add pearl@pearl-integrations
codex mcp login pearl

Claude Code

git clone --branch v0.8.7 --depth 1 https://github.com/Pearl-Passport/pearl-agent-plugin.git
cd pearl-agent-plugin
claude plugin marketplace add .
claude plugin install pearl@pearl-integrations
claude mcp login plugin:pearl:pearl

For Claude web/desktop Chat, add https://agent.joinpearl.co/mcp as a custom connector, enter public client ID pearl-claude-hosted, and leave the secret empty.

Cursor IDE, Cloud Agents, and Grok Bot

git clone --branch v0.8.7 --depth 1 https://github.com/Pearl-Passport/pearl-agent-plugin.git
cd pearl-agent-plugin
mkdir -p ~/.cursor/plugins/local
test ! -e ~/.cursor/plugins/local/pearl-cursor
cp -R plugins/pearl/cursor ~/.cursor/plugins/local/pearl-cursor

Reload Cursor and enable Pearl Cursor in Customize. The plugin and server use the collision-resistant identifier pearl-cursor, public client ID pearl-cursor, no secret, seven read scopes, and the official hosted and desktop callbacks documented in OAuth setup.

Validate

npm --prefix plugins/pearl test
npm --prefix plugins/pearl run validate
npm --prefix plugins/pearl/mcp-apps test
npm --prefix plugins/pearl/mcp-apps run validate
npm --prefix plugins/pearl run validate:live
npm --prefix plugins/pearl run validate:registry
npm --prefix plugins/pearl run validate:registry:schema
npm --prefix plugins/pearl run validate:registry:live
npm --prefix cli/pearl run check
npm --prefix cli/pearl test
npm --prefix cli/pearl run validate

Pearl CLI release candidate

The same repository contains Pearl's standalone read-only CLI in cli/pearl. After Pearl verifies ownership of the @joinpearl npm scope and publishes through the protected Trusted Publishing workflow:

npm install --global @joinpearl/cli
pearl doctor --json
pearl login
pearl tools --json

Until that npm release exists, use the repository development instructions in the CLI README. Do not install an unverified package with a similar name.

MCP Registry release candidate

server.json is Pearl's remote-only metadata for the preview MCP Registry. It declares io.github.Pearl-Passport/pearl-agent-plugin, matching the case-sensitive public GitHub owner, and the same one Streamable HTTP endpoint used by every host wrapper. It contains no header, token, client secret, package runtime, or tool allowlist.

Registry publication is intentionally separate from source availability. It requires a validated v0.8.7 release from protected main, a protected mcp-registry-publish GitHub environment restricted to v* release tags, and secretless GitHub OIDC. This small-team repository does not require a second human approver; required CI, signed commits, linear history, admin enforcement, secret scanning, push protection, and the tag-only publication boundary remain enforced. Until that protected workflow completes and the exact version is verified in the Registry, do not describe Pearl as listed there. The Registry is itself in preview.

See cross-host setup, the capability snapshot, and source provenance.

Marketplace publication remains a separate host-review step. See submission paths for new applications and future release updates.

Security, policies, and brand

• Support and security: hello@joinpearl.co (use [Security] in the subject line for vulnerability reports)
• Support: https://joinpearl.co/support
• Privacy: https://joinpearl.co/privacy
• Terms: https://joinpearl.co/terms
• Software license: MIT
• Pearl trademarks and artwork: TRADEMARKS.md