Local iMessage RAG MCP Server

Created By
willccbba year ago
iMessage RAG MCP Server from Anthropic MCP Hackathon (NYC)
Overview

what is Local iMessage RAG MCP Server?

Local iMessage RAG MCP Server is a project developed during the Anthropic NYC MCP hackathon, designed to facilitate local iMessage communication using a custom server setup.

how to use Local iMessage RAG MCP Server?

To use the server, follow the setup instructions provided in the README files located in the project folders. Note that the project may have bugs and is not actively maintained.

key features of Local iMessage RAG MCP Server?

  • Localized iMessage communication setup
  • Custom server configuration
  • Developed during a hackathon for experimental purposes

use cases of Local iMessage RAG MCP Server?

  1. Setting up a local iMessage server for private communication.
  2. Experimenting with iMessage functionalities in a controlled environment.
  3. Learning about server configurations and local messaging protocols.

FAQ from Local iMessage RAG MCP Server?

  • Is the server stable?

The server is likely to be buggy as it was developed during a hackathon and is not actively maintained.

  • Are there detailed instructions available?

Yes, setup instructions can be found in the README files within the project folders.

  • Is this project open for contributions?

The author has indicated that they are not planning to actively maintain it, but contributions may be welcome.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
willccbb
Star
6
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