Mallory MCP Server

Created By
malloryaia year ago
MCP Server for mallory.ai intelligence
Overview

what is Mallory Mcp Server?

Mallory Mcp Server is a server designed for the MCP (Mallory Control Protocol) API, which facilitates communication and data exchange for mallory.ai applications.

how to use Mallory Mcp Server?

To use the Mallory Mcp Server, set up the server environment by following the installation instructions in the GitHub repository, and then connect your application to the server using the provided API endpoints.

key features of Mallory Mcp Server?

  • Supports the Mallory Control Protocol for seamless integration with mallory.ai applications.
  • Provides a robust API for data exchange and communication.
  • Built with Python, ensuring flexibility and ease of use.

use cases of Mallory Mcp Server?

  1. Integrating mallory.ai services into existing applications.
  2. Facilitating real-time data exchange between different components of a system.
  3. Enabling developers to build custom applications using the MCP API.

FAQ from Mallory Mcp Server?

  • What programming language is Mallory Mcp Server built with?

Mallory Mcp Server is built with Python.

  • Is there any documentation available?

Yes! Documentation is available in the GitHub repository.

  • How can I contribute to the project?

Contributions are welcome! Please refer to the contribution guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
malloryai
Star
1
Language
Python
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