SilverBullet MCP Server

The server is designed to be run via Docker Compose alongside your existing SilverBullet Docker container. It handles authentication and provides a secure way for external applications to access and manipulate your SilverBullet space.

Asking Claude to create a retirement projection, based on my notes.

git clone <repository-url> cd <repository-name>

Create an environment file:Copy the contents of.env.exampleto a new file named.env.

Update the.envfile with your specific values:

- 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 (e.g., your AI model) to authenticate with this MCP server.
- SB_API_BASE_URL: (Optional if running via docker-compose as defined) The base URL for the SilverBullet API. Defaults tohttp://silverbullet:3000in thedocker-compose.yml.
- PORT: (Optional if running via docker-compose as defined) The port the MCP server will listen on. Defaults to4000.

Build and run the services using Docker Compose:

- Build the Docker image for thesilverbullet-mcp-serverif it doesn't exist or ifDockerfileor related files have changed.
- Pull the latestsilverbulletmd/silverbulletimage.
- Start both the SilverBullet instance and the MCP server.

The SilverBullet instance will be accessible athttp://localhost:3000. The MCP server will be accessible athttp://localhost:4000.

This MCP server runs as part of a Docker Compose setup and will be accessible athttp://localhost:4000by default.

You can connect to this server using an MCP client. The method of connection and authentication depends on the client's capabilities.

Usingmcp-remote(for stdio-only clients)

If your MCP client only supportsstdioconnections (e.g., older versions of Claude Desktop, Cursor, Windsurf), you can usemcp-remoteto bridge the connection to this HTTP-based MCP server.

mcp-remoteacts as a local stdio MCP server that proxies requests to a remote HTTP MCP server, handling authentication in the process.

Client Configuration with Authentication:

This MCP server requires token-based authentication. Configure your MCP client (e.g., inclaude_desktop_config.json,~/.cursor/mcp.json, or~/.codeium/windsurf/mcp_config.json) to usemcp-remoteand pass theMCP_TOKENvia a custom header:

Direct Connection (for Streamable HTTP clients)

If your MCP client supports Streamable HTTP transport and can send custom headers, you can connect to it directly.

The server supports two methods for token-based authentication:

- Header Name:Authorization
- Header Value:Bearer YOUR_MCP_TOKEN

- Append?token=YOUR_MCP_TOKENto the server URL.
- Example:http://localhost:4000/mcp?token=YOUR_MCP_TOKEN

ReplaceYOUR_MCP_TOKENwith the actual value of theMCP_TOKENenvironment variable set in your.envfile.

Endpoint:http://localhost:4000/mcp(or as configured byPORTif not using Docker Compose defaults).

Consult your MCP client's documentation on how to configure connections to remote HTTP MCP servers, including how to send custom headers or append query parameters.

Create notes, search, & think with your Fabric AI workspace

Interact with your Anytype data through its API, enabling AI assistants to access your information.

MCP server for Apple Notes with semantic search and CRUD operations. Claude searches, reads, creates, updates, and manages your Apple Notes through natural language.

Personal Knowledge Base MCP — 22 tools for AI agents to access your curated reading intelligence.

Integrates Model Context Protocol (MCP) with Obsidian, allowing AI assistants to interact with your notes and vault.

The visual deal tracker for AI agents to search pipelines, log notes, qualify leads, and export live reports.

Create notes in Flomo through AI chat interactions in Cursor or Claude desktop.

Manage and share personal knowledge, daily notes, and reusable prompts using GitHub Gists.

Historis keeps track of what happened — so you and your AI are never out of sync. Everything lands in one shared timeline, linked to the right people. Ask for the brief: what happened, what you should know, what needs handling.