Pica MCP Server

Created By
picahqa year ago
A Model Context Protocol Server for Pica, built in TypeScript
Overview

what is Pica MCP Server?

Pica MCP Server is a Model Context Protocol Server designed for Pica, built using TypeScript, which facilitates communication between various applications and services.

how to use Pica MCP Server?

To use the Pica MCP Server, install the necessary dependencies, build the server, and configure it with your Pica API key. You can then connect it with Claude Desktop and start using it with various platforms.

key features of Pica MCP Server?

  • Built with TypeScript for robust development.
  • Supports integration with multiple platforms through the Model Context Protocol.
  • Provides debugging tools via the MCP Inspector.

use cases of Pica MCP Server?

  1. Integrating with email services to send messages.
  2. Automating tasks in Google Sheets.
  3. Managing calendar events and user data from databases.

FAQ from Pica MCP Server?

  • What is required to run the Pica MCP Server?

You need a Pica API key and the server must be configured correctly in Claude Desktop.

  • How can I debug the server?

Use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

  • Is there a license for this project?

Yes, the project is licensed under the GPL-3.0 license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
picahq
Star
3
Language
JavaScript
License
GPL-3.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