limitless

The Limitless MCP server exposes a single GET tool named getLifelogs that retrieves lifelogs from the Limitless Developer API. The server is designed to be run locally and can be controlled via the included client and interactive modes. To use the server, start it in server mode and then connect a client to invoke the getLifelogs tool. The tool accepts optional query parameters as part of the HTTP GET request, such as filters or pagination, depending on the Limitless API capabilities. The client and interactive modes demonstrate how to call the tool with JSON-formatted parameters, and the merged implementation passes environment variables (including your API key) to the spawned server process for authentication.

Typical usage flows:

• Server Mode: Run the MCP server so it listens for tool calls.
• Client Mode: Spawn the server and call the getLifelogs tool directly from the client.
• Interactive Mode: Use an interactive client to call tools with JSON parameters, enabling experimentation and testing without code changes.

Prerequisites

• Node.js v20 or higher
• npm
• A valid Limitless API key (set as an environment variable for the server: LIMITLESS_API_KEY)

Install and build

1. Clone the repository and navigate into it
2. Install dependencies

git clone <repo-url> && cd limitless
npm ci

3. Build the TypeScript project

npm run build

4. Set up your API key (example for Unix-like shells)

export LIMITLESS_API_KEY=your_api_key_here

5. Run the server (see the usage section for invocation examples)

Notes and tips:

• The server reads LIMITLESS_API_KEY from the environment to authenticate requests with the Limitless API.
• If you encounter issues with the API key, ensure it has the correct permissions and is exported in the environment where the MCP server runs.
• In some environments, you may need to restart the server after updating environment variables.
• The mcp_config block maps a logical server name (limitless) to the Node.js entry point that implements the MCP server logic. You can adjust the path if your build artifacts are in a different location.
• If you later publish this as an npm package, you could replace the local node execution with an npm run script or switch to a packaged distribution.