home / mcp / limitless mcp server

Limitless MCP Server

Provides an MCP server that connects Limitless Pendant data to AI tools via the Limitless API, enabling structured lifelog access and actionable workflows.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "boyleryan-mcp-limitless-server": {
      "command": "node",
      "args": [
        "<FULL_FILE_PATH_TO_DIST_SERVER.js>"
      ],
      "env": {
        "LIMITLESS_API_KEY": "<YOUR_LIMITLESS_API_KEY_HERE>"
      }
    }
  }
}

You can extend AI chat interfaces to access and act on your Limitless Pendant data through a dedicated MCP server. This server connects your pendant lifelog recordings to AI tools via the Limitless API, enabling structured, programmable interactions and workflows between your data and AI assistants.

How to use

You will run this MCP server alongside your chosen MCP client (for example Claude, Windsurf, Cursor, ChatWise, or ChatGPT when available). Configure the client to spawn the server as a stdio process, then provide your Limitless API key. Once connected, you can retrieve lifelog entries by ID, by date or date range, list recent lifelog entries, and perform text searches on recent lifelogs. These actions enable practical workflows like pulling action items from your lifelog and sending them to other apps such as Notion or task managers.

How to install

Prerequisites and initial setup ensure you can run and connect the MCP server from your client.

# 1) Clone or download the project
# 2) Navigate to the directory
cd mcp-limitless-server
# 3) Install dependencies
npm install
# 4) Build the code
npm run build

Configuration and usage notes

Configure your MCP client to launch the server as a stdio process using the example provided. You will supply the Limitless API key via an environment variable.

{
  "mcpServers": {
    "limitless": {
      "command": "node",
      "args": ["<FULL_FILE_PATH_TO_DIST_SERVER.js>"],
      "env": {
        "LIMITLESS_API_KEY": "<YOUR_LIMITLESS_API_KEY_HERE>"
      }
    }
  }
}

Notes & limitations

- Pendant required: The server relies on data generated by the Limitless Pendant. Ensure your Pendant is connected and recording.

- API beta status: The Limitless API is in beta and may be unstable or subject to changes. Large data requests can timeout; the server enforces a 120-second timeout per API call.

- Search scope: The search endpoint scans only recent lifelogs (default is 20 results, max 100). It does not search your full history.

- Transport: The server uses stdio and is started by your MCP client.

Available tools

The MCP server exposes the following functions to interact with your lifelog data.

Security and maintenance

Keep your Limitless API key secure. Update the server when new features are released to stay aligned with the official API changes.

Troubleshooting

If you encounter timeouts for large requests, retry with smaller batches or date ranges. Verify your Pendant connection and that data is actively recording.

Available tools

limitless_get_lifelog_by_id

Retrieve a single Pendant recording by its specific ID.

limitless_list_lifelogs_by_date

List Pendant recordings for a specific date.

limitless_list_lifelogs_by_range

List Pendant recordings within a date/time range.

limitless_list_recent_lifelogs

List the most recent Pendant recordings.

limitless_search_lifelogs

Search the titles or content of recent Pendant recordings (limited scope).