SilverBullet

Exposes SilverBullet data via MCP HTTP/stdio endpoints for external models and tools.

javascript

22

GitHub Stars

javascript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You set up a SilverBullet MCP Server to securely expose your SilverBullet data to any MCP-compatible client, including large language models. This bridge lets you access notes and data through standardized MCP tools and resources, enabling powerful automation and integration while keeping authentication and access under your control.

How to use

Connect your MCP client to the SilverBullet MCP Server to access your space. You can use either an HTTP connection or a local stdio bridge depending on your client’s capabilities. With the HTTP approach, your client talks to the server’s HTTP endpoint to fetch tools and interact with your data. With the stdio bridge, you route requests through a local bridge (mcp-remote) that forwards them to the HTTP server, which is convenient for clients that only support stdio.

Once connected, you can perform actions that read, search, or modify your SilverBullet space through the MCP interface. Use the tokens described in your environment to authenticate your client, and ensure the client sends the token on every request. The server exposes a secure path for external applications to access and manipulate your data.

How to install

Prerequisites you must have before starting:

• Docker • Docker Compose

Create a working directory for your MCP setup and navigate into it.
Prepare environment variables. Create a file named .env with the required secrets and settings. The following variables are used by the MCP server:

SB_AUTH_TOKEN: A secure token for SilverBullet to authenticate with this MCP server and for this MCP server to authenticate with SilverBullet
MCP_TOKEN: A secure token for clients to authenticate with this MCP server
SB_API_BASE_URL: The base URL for the SilverBullet API (optional if running via docker-compose as defined)
PORT: The port the MCP server will listen on (defaults to 4000)

Start the services using Docker Compose. Run the following command in your project directory:

docker-compose up --build

Additional notes

After starting, the SilverBullet instance will be available at http://localhost:3000 and the MCP server at http://localhost:4000 by default.