Perigon MCP Server

Created By
goperigona year ago
Official MCP server for the Perigon API
Overview

what is Perigon MCP Server?

Perigon MCP Server is the official server for the Perigon API, designed to facilitate seamless integration and interaction with the Perigon platform.

how to use Perigon MCP Server?

To use the Perigon MCP Server, developers can connect to the server via the provided API endpoints to access various functionalities and data provided by the Perigon API.

key features of Perigon MCP Server?

  • Official support for the Perigon API
  • Easy integration with existing applications
  • Comprehensive documentation for developers

use cases of Perigon MCP Server?

  1. Building applications that require data from the Perigon API.
  2. Integrating Perigon services into existing software solutions.
  3. Developing new features that leverage the capabilities of the Perigon API.

FAQ from Perigon MCP Server?

  • What is the Perigon API used for?

The Perigon API is used for accessing various data and services provided by the Perigon platform.

  • Is there any cost associated with using the Perigon MCP Server?

The Perigon MCP Server is free to use, but check the API documentation for any usage limits.

  • Where can I find the documentation for the Perigon API?

Documentation can be found on the official GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
goperigon
Star
3
Language
TypeScript
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