Pearl

io.github.Pearl-PassportPublished by GitHub account Pearl-Passportv0.12.3Updated Oct 24, 2026

Pearl places, table availability, and confirmed visit, save and trip actions for reviewed hosts.

The publisher's own server: Pearl Api Mcp Server

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Pearl connects an assistant to a remote MCP endpoint for restaurant discovery, table availability, and confirmed visit, saved-place and trip actions for…

What you can do
  • Look up places, venue details, booking opening times, similar and nearby places, Pearl events and bookable venues in a Tables city
  • Check table availability for reviewed hosts
  • Record and manage visits, saved places and private trips through confirmed actions
  • Import existing records such as flights, recorded seats, reservations and visit items, without provider actions
  • Show presentation-only cards for venues, saved places, visits, place matches, profile, trips, reservations and previews
When to use it
For eligible Pearl Reserve or Elite members who want an assistant to help find places, check table availability, and keep track of visits, saved places and trips. Useful when the workflow is discovery and record-keeping rather than booking.
Requirements
A remote Streamable HTTP endpoint with OAuth sign-in; no local package or runtime. An eligible Pearl Reserve or Elite membership is required, and available tools depend on the connection's permissions and host. Reconnecting is needed to approve newly requested permissions.
Before you install
Requires OAuth authorization to a Pearl member account and access to member profile and trip data. Confirmed-action tools write visits, saved places and trips, and record imports add existing reservations and flights. This release cannot book, hold, change, cancel or pay for reservations. Never place credentials or member data in the package.

Installation

In SourceWeft

  1. Open Pearl in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Pearl-Passport%2Fpearl-agent-plugin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pearl": {
      "type": "http",
      "url": "https://agent.joinpearl.co/mcp"
    }
  }
}

README

Pearl agent integration package

New to Pearl? Start with the Quick Start & Tester Guide.

Eligible Pearl Reserve and Elite members can connect. Available actions depend on the connection's permissions and live tool inventory.

Pearl's installable package gives Codex, Claude, Cursor, and Cursor's Grok Bot a thin host integration for one authenticated Streamable HTTP MCP endpoint:

https://agent.joinpearl.co/mcp

The package contains host manifests, the Pearl Concierge skill, public setup documentation, brand assets, presentation-only MCP Apps resources, and validation code. It contains no application, database, OAuth server, MCP executor, deployment configuration, access token or client secret.

Current release

Package 0.13.0 keeps the common 13 reads for every authenticated connection. Reviewed Codex, Claude and Cursor clients also get table availability, six discovery reads (venue details, when bookings open, similar and nearby places, Pearl events, and the bookable venues of a Tables city) and ten confirmed-action tools for visits, saved places and private trips: 20 tools with the seven reads, 30 with all ten scopes. The discovery reads need no new permission; reconnect to approve newly requested permissions. ChatGPT retains its submitted 18-tool visit/availability contract. The CLI defaults to 13 reads; unknown clients remain read-only. Selected Codex, Claude, Cursor and CLI registrations can also receive four confirmed record-import pairs after rollout and relevant consent. These record flights, recorded seats, existing reservations and visit items, without provider actions. CLI publication is separate.

Current Codex presents the shared OpenAI-hosted CIMD client ID (older releases used per-install identities); Pearl accepts only that strictly validated official family. The same gateway and executor serve every host. Cards are presentation-only and cover venues, saved places, visits, place matches, your profile, trips, reservations, venue details, availability, flights where available, and visit/save/trip previews and receipts.

See the capability snapshot for the exact host matrix and honest unavailable-workflow labels. No host can book, hold, change, cancel, or pay for a reservation in this release. The package does not claim that a host has approved or listed Pearl.

For practical logging/editing prompts, matching and confirmation rules, and reservation boundaries, see Visits and reservations.

Included artifacts

  • .codex-plugin/plugin.json: Codex metadata and starter prompts.
  • .claude-plugin/plugin.json: Claude Code and Cowork metadata.
  • cursor/.cursor-plugin/plugin.json: the isolated Cursor source plus the host-specific pearl-cursor identifier and secretless public OAuth configuration.
  • .mcp.json: the single shared URL-only Codex and Claude connection; Cursor's isolated thin wrapper uses the same endpoint with its required static public client.
  • server.json: the MCP Registry preview entry for the same remote URL; it contains no headers, credentials, package runtime, or tool inventory.
  • skills/pearl-concierge/: the canonical discovery-first workflow skill for Codex and Claude; Cursor ships a byte-for-byte validated mirror under its isolated source subtree.
  • docs/: member setup, host registration and review, OAuth, and release instructions.
  • assets/: approved Pearl marketplace artwork; see assets/README.md. Cursor's isolated source contains a hash-validated logo mirror.
  • mcp-apps/: the dependency-free, versioned inline UI resource and integration helpers. It adds no tools, auth, network endpoint, or business logic; see mcp-apps/README.md.
  • scripts/ and test/: zero-dependency validation.

Validate

From the repository root:

bash
npm --prefix plugins/pearl testnpm --prefix plugins/pearl run validatenpm --prefix plugins/pearl run validate:livenpm --prefix plugins/pearl run validate:registrynpm --prefix plugins/pearl run validate:registry:schemanpm --prefix plugins/pearl run validate:registry:liveclaude plugin validate plugins/pearl --strictclaude plugin validate . --strict

Live validation performs only public discovery and unauthenticated challenge checks. It does not use credentials or invoke member tools.

Pearl maintainers who have Codex's bundled plugin-creator and skill-creator skills installed should additionally run those skills' validators against plugins/pearl and both packaged Pearl Concierge skill directories. These are maintainer checks, not public package dependencies.

Before a marketplace release, also run the safe static-host registration probes documented in docs/submission.md. Those probes use an intentionally invalid MCP resource and never create an authorization request or invoke a member tool.

The official MCP Registry is in preview. Keeping server.json in the package does not publish it or imply Registry, Anthropic, Cursor, or OpenAI approval. Registry publication is a separate protected release action documented in docs/releasing.md.

Security and support

Never add credentials, environment files, authorization headers, private implementation details, or member data to this package. Report vulnerabilities privately to [email protected] with [Security] in the subject line.

Source: plugins/pearl/README.md at commit 31bc38e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.12.3LatestSep 23, 2026
  2. v0.12.0Sep 23, 2026
  3. v0.11.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Pearl integrations