slite

The Slite MCP Server integrates with Slite's API to enable searching your workspace, retrieving note content, and browsing note hierarchies from a single MCP endpoint. After you configure and run the server, you can use the provided tools to interact with Slite data: slite_search lets you query notes across your workspace, slite_get_note retrieves a specific note by its ID in either Markdown or HTML format, and slite_get_note_children fetches child notes under a given parent note. These tools return structured results that you can pass to other MCP tools or use in studies, documentation, or workflows that require Slite content.

Prerequisites:

• Node.js 16+ (and npm)
• A valid Slite API key

1. Clone the repository

• git clone https://github.com/fajarmf/slite-mcp.git
• cd slite-mcp

2. Install dependencies

• npm install

3. Build the project

• npm run build

4. Run the MCP server (example)

• node build/index.js

5. Configure your MCP client

• Add the server entry to your ~/.mcp.json as shown in the Configuration section of the README.

Notes:

• Ensure SLITE_API_KEY is kept secret and not committed to source control.
• The build output is expected at slite-mcp/build/index.js; adjust the path in the mcp_config accordingly.

Tips and potential issues:

• Ensure your Slite API key has the necessary permissions to read workspace content.
• When updating dependencies or rebuilding, re-run npm install and npm run build.
• If you change the build output path, update the mcp_config index.js path accordingly.
• The MCP tools expect the API responses in the formats described in the README; if API changes occur, verify compatibility with the test scripts under tests/.
• For troubleshooting authentication, double-check the API key, its scope, and that it is passed correctly via SLITE_API_KEY env variable.