Limitless MCP Server (v0.1.0)

Created By
ipvr9a year ago
This is an MCP (Model Context Protocol) server that connects your Limitless Pendant data to AI tools like Claude, Windsurf, and others via the Limitless API. It lets AI apps and agents interact with your Lifelog in a structured, programmable way.
Overview

What is Limitless MCP Server?

The Limitless MCP Server is a Model Context Protocol (MCP) server that connects data from the Limitless Pendant to various AI tools like Claude and Windsurf through the Limitless API, enabling structured interactions with your Lifelog data.

How to use Limitless MCP Server?

To use the server, you need to have a Limitless Pendant connected and recording data. Clone the project, install dependencies, build the code, and configure your MCP client to launch the server with the required API key.

Key features of Limitless MCP Server?

  • Retrieve Pendant recordings by ID, date, or date range.
  • Perform text searches within recent Pendant recordings.
  • Integrate with AI applications to pull action items from your Lifelog.

Use cases of Limitless MCP Server?

  1. Automating task management by sending action items from Lifelog to Notion.
  2. Analyzing personal data recorded by the Limitless Pendant for insights.
  3. Enhancing AI interactions with context-rich data from the Lifelog.

FAQ from Limitless MCP Server?

  • What is required to use the server?

You need a Limitless Pendant, a Limitless account, and an API key.

  • Is the Limitless API stable?

The API is currently in beta and may experience occasional instability.

  • Can I search my entire Lifelog history?

No, the search feature is limited to recent logs only.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ipvr9
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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