Pearl MCP Server

Created By
Pearl-coma year ago
A Model Context Protocol (MCP) server implementation that exposes Pearl's AI and Expert services through a standardized interface
Overview

What is Pearl MCP Server?

Pearl MCP Server is a Model Context Protocol (MCP) server implementation that provides access to Pearl's AI and expert services through a standardized interface, enabling interaction with advanced AI assistants and human experts.

How to use Pearl MCP Server?

To use the Pearl MCP Server, clone the repository from GitHub, set up a virtual environment, install dependencies, and run the server using either stdio or SSE transport. You can also connect to a hosted version of the server.

Key features of Pearl MCP Server?

  • Supports stdio and SSE transports for communication.
  • Integrates with Pearl API for AI and expert assistance.
  • Manages sessions for continuous conversations.
  • Offers multiple interaction modes: AI-only, AI-Expert, and Expert modes.
  • Tracks conversation history and manages stateful sessions.

Use cases of Pearl MCP Server?

  1. Providing quick AI responses for general inquiries.
  2. Assisting users with complex topics through AI and human expert collaboration.
  3. Facilitating direct human expert assistance for sensitive issues.

FAQ from Pearl MCP Server?

  • How do I obtain a Pearl API key?

You can request an API key by visiting the Pearl contact page and following the instructions provided.

  • Can I use the server without installing it locally?

Yes, you can connect to the hosted MCP server provided by Pearl directly with any MCP client.

  • What programming language is the server implemented in?

The Pearl MCP Server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Pearl-com
Star
2
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago