silverbullet-mcp

Ahmad-A0/silverbullet-mcp

3.3

If you are the rightful owner of silverbullet-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The SilverBullet MCP Server is a bridge that connects Large Language Models (LLMs) and other MCP-compatible clients to your SilverBullet notes and data.

The SilverBullet MCP Server is designed to facilitate seamless interaction between Large Language Models (LLMs) and your SilverBullet instance. By leveraging the Model Context Protocol (MCP), this server acts as a conduit, allowing external applications to access and manipulate your SilverBullet notes and data securely. The server is intended to be deployed alongside your existing SilverBullet Docker container using Docker Compose, ensuring a streamlined setup process. It manages authentication and provides a standardized interface for MCP-compatible clients to interact with SilverBullet resources. This setup is particularly beneficial for users who wish to integrate AI models with their note-taking and data management workflows, enabling advanced functionalities such as automated data analysis, content generation, and more. The server supports both stdio and HTTP-based MCP clients, offering flexibility in how connections are established and maintained.

Features

  • Secure Authentication: Utilizes token-based authentication to ensure secure access to SilverBullet data.
  • Docker Integration: Easily deployable alongside SilverBullet using Docker Compose.
  • Flexible Client Support: Compatible with both stdio and HTTP-based MCP clients.
  • Standardized Interface: Provides a consistent MCP interface for interacting with SilverBullet resources.
  • Customizable Configuration: Environment variables allow for tailored server settings.

Usages

docker compose with silverbullet

docker-compose up --build

mcp remote with stdio clients

c
{
  "mcpServers": {
    "silverbullet-mcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:4000/mcp", 
        "--transport",
        "http-only",
        "--header",
        "Authorization:Bearer ${MCP_SERVER_TOKEN}"
      ],
      "env": {
        "MCP_SERVER_TOKEN": "your_actual_mcp_token_from_dotenv"
      }
    }
  }
}

direct connection with streamable http clients

http://localhost:4000/mcp?token=YOUR_MCP_TOKEN