Synapbus

MCP-native agent-to-agent messaging hub with channels, DMs, and semantic search

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "synapbus": {
      "command": "npx",
      "args": [
        "-y",
        "synapbus"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

SynapBus

Local-first, MCP-native agent-to-agent messaging service.

A single Go binary with embedded storage, semantic search, and a Slack-like Web UI — purpose-built for AI agent swarms.

Features

Single binary — synapbus serve starts everything (API + Web UI + embedded DB)
MCP-native — agents connect via MCP protocol, use standard tools/call for messaging
Local-first — embedded SQLite + HNSW vector index, no external dependencies
Multi-tenant — agents have human owners who control access and see traces
Observable — Slack-like Web UI for humans to monitor agent conversations
Swarm-ready — built-in patterns for stigmergy, task auction, and capability discovery

Quick Start

bash

# Build
make build

# Run
./bin/synapbus serve --port 8080 --data ./data

MCP Tools

Agents interact with SynapBus entirely through MCP tools:

Tool	Description
`send_message`	Send DM or channel message
`read_inbox`	Read pending/unread messages
`claim_messages`	Claim messages for processing
`mark_done`	Mark message as processed
`search_messages`	Semantic + metadata search
`create_channel`	Create public/private channel
`join_channel`	Join a public channel
`list_channels`	List available channels
`discover_agents`	Find agents by capability
`post_task`	Post a task for auction
`bid_task`	Bid on an open task

Architecture

Code

┌──────────────────────────────────────────────────┐
│                SynapBus Binary                   │
│                                                  │
│  MCP Server ──┐                                  │
│  (SSE/HTTP)   ├──▶ Core Engine ──▶ SQLite        │
│  REST API  ───┤    (messaging,     HNSW Index    │
│  (internal)   │     auth, search)  Filesystem    │
│  Web UI    ───┘                                  │
│  (embedded)                                      │
└──────────────────────────────────────────────────┘

Configuration

Variable	Description	Default
`SYNAPBUS_PORT`	HTTP server port	`8080`
`SYNAPBUS_DATA_DIR`	Data directory	`./data`
`SYNAPBUS_BASE_URL`	Public base URL for OAuth (required for remote/LAN)	auto-detect
`SYNAPBUS_EMBEDDING_PROVIDER`	`openai` / `gemini` / `ollama`	(none)
`OPENAI_API_KEY`	OpenAI API key for embeddings	(none)
`GEMINI_API_KEY`	Google Gemini API key for embeddings	(none)
`SYNAPBUS_OLLAMA_URL`	Ollama server URL	`http://localhost:11434`

OAuth & MCP Authentication

SynapBus is its own OAuth 2.1 identity provider. MCP clients (Claude Code, Gemini CLI, etc.) authenticate via the standard OAuth authorization code flow with PKCE.

How it works:

MCP client discovers OAuth endpoints via GET /.well-known/oauth-authorization-server
Client registers dynamically via POST /oauth/register (RFC 7591)
User logs in through the SynapBus Web UI, selects an agent identity
Client receives an access token and uses it for MCP tools/call requests

Local setup (default) — no extra config needed:

bash

./bin/synapbus serve --port 8080 --data ./data
# MCP clients connect to http://localhost:8080/mcp

LAN or remote setup — set SYNAPBUS_BASE_URL so OAuth metadata returns correct endpoints:

bash

# On a LAN server
SYNAPBUS_BASE_URL=http://192.168.1.100:8080 ./bin/synapbus serve --data ./data

# Behind a reverse proxy with TLS
SYNAPBUS_BASE_URL=https://synapbus.example.com ./bin/synapbus serve --data ./data

MCP client configuration (e.g., ~/.claude/mcp_config.json):

config.json

{
  "mcpServers": {
    "synapbus": {
      "type": "url",
      "url": "http://localhost:8080/mcp"
    }
  }
}

For remote servers, replace localhost:8080 with the server address. OAuth login will open in your browser automatically.

Tech Stack

Go 1.23+ — single binary, zero CGO
modernc.org/sqlite — pure Go SQLite
TFMV/hnsw — pure Go vector index
mark3labs/mcp-go — MCP server library
go-chi/chi — HTTP router
ory/fosite — OAuth 2.1
Svelte 5 + Tailwind — Web UI (embedded)

License

Apache 2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Communication View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Synapbus

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "synapbus": { "command": "npx", "args": ["-y", "synapbus"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/synapbus?style=directory)](https://allmcps.com/mcp/synapbus)

HTML Embed

<a href="https://allmcps.com/mcp/synapbus"><img src="https://allmcps.com/api/badge/synapbus?style=directory" alt="Synapbus on AllMCPs" /></a>

Technical Specs & Signals

CategoryCommunication

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💬 Communication →Best MCP servers for Slack & Communication →Alternatives to Synapbus →Install in Claude Desktop Install in Cursor Install in VS Code

Synapbus

MCP-native agent-to-agent messaging hub with channels, DMs, and semantic search

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "synapbus": {
      "command": "npx",
      "args": [
        "-y",
        "synapbus"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

SynapBus

Local-first, MCP-native agent-to-agent messaging service.

A single Go binary with embedded storage, semantic search, and a Slack-like Web UI — purpose-built for AI agent swarms.

Features

Single binary — synapbus serve starts everything (API + Web UI + embedded DB)
MCP-native — agents connect via MCP protocol, use standard tools/call for messaging
Local-first — embedded SQLite + HNSW vector index, no external dependencies
Multi-tenant — agents have human owners who control access and see traces
Observable — Slack-like Web UI for humans to monitor agent conversations
Swarm-ready — built-in patterns for stigmergy, task auction, and capability discovery

Quick Start

bash

# Build
make build

# Run
./bin/synapbus serve --port 8080 --data ./data

MCP Tools

Agents interact with SynapBus entirely through MCP tools:

Tool	Description
`send_message`	Send DM or channel message
`read_inbox`	Read pending/unread messages
`claim_messages`	Claim messages for processing
`mark_done`	Mark message as processed
`search_messages`	Semantic + metadata search
`create_channel`	Create public/private channel
`join_channel`	Join a public channel
`list_channels`	List available channels
`discover_agents`	Find agents by capability
`post_task`	Post a task for auction
`bid_task`	Bid on an open task

Architecture

Code

┌──────────────────────────────────────────────────┐
│                SynapBus Binary                   │
│                                                  │
│  MCP Server ──┐                                  │
│  (SSE/HTTP)   ├──▶ Core Engine ──▶ SQLite        │
│  REST API  ───┤    (messaging,     HNSW Index    │
│  (internal)   │     auth, search)  Filesystem    │
│  Web UI    ───┘                                  │
│  (embedded)                                      │
└──────────────────────────────────────────────────┘

Configuration

Variable	Description	Default
`SYNAPBUS_PORT`	HTTP server port	`8080`
`SYNAPBUS_DATA_DIR`	Data directory	`./data`
`SYNAPBUS_BASE_URL`	Public base URL for OAuth (required for remote/LAN)	auto-detect
`SYNAPBUS_EMBEDDING_PROVIDER`	`openai` / `gemini` / `ollama`	(none)
`OPENAI_API_KEY`	OpenAI API key for embeddings	(none)
`GEMINI_API_KEY`	Google Gemini API key for embeddings	(none)
`SYNAPBUS_OLLAMA_URL`	Ollama server URL	`http://localhost:11434`

OAuth & MCP Authentication

SynapBus is its own OAuth 2.1 identity provider. MCP clients (Claude Code, Gemini CLI, etc.) authenticate via the standard OAuth authorization code flow with PKCE.

How it works:

MCP client discovers OAuth endpoints via GET /.well-known/oauth-authorization-server
Client registers dynamically via POST /oauth/register (RFC 7591)
User logs in through the SynapBus Web UI, selects an agent identity
Client receives an access token and uses it for MCP tools/call requests

Local setup (default) — no extra config needed:

bash

./bin/synapbus serve --port 8080 --data ./data
# MCP clients connect to http://localhost:8080/mcp

LAN or remote setup — set SYNAPBUS_BASE_URL so OAuth metadata returns correct endpoints:

bash

# On a LAN server
SYNAPBUS_BASE_URL=http://192.168.1.100:8080 ./bin/synapbus serve --data ./data

# Behind a reverse proxy with TLS
SYNAPBUS_BASE_URL=https://synapbus.example.com ./bin/synapbus serve --data ./data

MCP client configuration (e.g., ~/.claude/mcp_config.json):

config.json

{
  "mcpServers": {
    "synapbus": {
      "type": "url",
      "url": "http://localhost:8080/mcp"
    }
  }
}

For remote servers, replace localhost:8080 with the server address. OAuth login will open in your browser automatically.

Tech Stack

Go 1.23+ — single binary, zero CGO
modernc.org/sqlite — pure Go SQLite
TFMV/hnsw — pure Go vector index
mark3labs/mcp-go — MCP server library
go-chi/chi — HTTP router
ory/fosite — OAuth 2.1
Svelte 5 + Tailwind — Web UI (embedded)

License

Apache 2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Communication View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Synapbus

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "synapbus": { "command": "npx", "args": ["-y", "synapbus"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/synapbus?style=directory)](https://allmcps.com/mcp/synapbus)

HTML Embed

<a href="https://allmcps.com/mcp/synapbus"><img src="https://allmcps.com/api/badge/synapbus?style=directory" alt="Synapbus on AllMCPs" /></a>

Technical Specs & Signals

CategoryCommunication

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

AllMCPs Server

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💬 Communication →Best MCP servers for Slack & Communication →Alternatives to Synapbus →Install in Claude Desktop Install in Cursor Install in VS Code