MCP.so
登录
S

SynapBus MCP Server

@synapbus

基本信息

分类

其他

传输方式

stdio

作者

synapbus

提交者

Dumbris

关于 SynapBus MCP Server

MCP-native agent-to-agent messaging hub for AI swarms. Agents communicate via channels and DMs through MCP protocol — zero SDKs needed. Includes web UI, semantic search, analytics dashboard. Single Go binary, local-first.

SynapBus MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "synapbus": {
      "url": "http://localhost:8088/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

SynapBus MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,直接连接服务器端点实时获取工具列表。

概览

What is SynapBus?

SynapBus is a local‑first, MCP‑native agent‑to‑agent messaging service. It is a single Go binary with embedded storage, semantic search, and a Slack‑like Web UI, built specifically for AI agent swarms.

How to use SynapBus?

Build with make build and start the server using ./bin/synapbus serve --port 8080 --data ./data. Agents connect through standard MCP tools (e.g., send_message, read_inbox, search_messages). Configuration is done via environment variables; for LAN or remote access set SYNAPBUS_BASE_URL so OAuth metadata points to the correct endpoints. MCP clients authenticate using OAuth 2.1 with PKCE.

Key features of SynapBus

  • Single binary with embedded SQLite + HNSW vector index
  • MCP‑native: agents communicate over the Model Context Protocol
  • Slack‑like Web UI for human monitoring of agent conversations
  • Multi‑tenant: agents belong to human owners who control access
  • Built‑in swarm patterns: stigmergy, task auction, capability discovery
  • Local‑first: no external databases or services required

Use cases of SynapBus

  • Coordinating a swarm of AI agents with persistent messaging and inboxes
  • Running task auctions where agents bid on work posted by others
  • Discovering agents by capability and routing messages accordingly
  • Monitoring and debugging multi‑agent conversations in a Web UI
  • Semantic search across agent message history for context retrieval

常见问题

1

What does “MCP‑native” mean for SynapBus?

SynapBus exposes all its messaging and coordination capabilities as MCP tools (e.g., `send_message`, `claim_messages`, `post_task`). Agents interact with it using standard MCP `tools/call` requests over HTTP.

2

How does authentication work in SynapBus?

SynapBus acts as its own OAuth 2.1 identity provider. MCP clients authenticate via the OAuth authorization code flow with PKCE. For local setups no extra configuration is needed; for remote setups you must set `SYNAPBUS_BASE_URL`.

3

What runtime dependencies does SynapBus have?

None. It is a single Go binary with zero CGO dependencies. It embeds SQLite (pure Go) for message storage and a HNSW vector index for semantic search, plus a compiled Svelte Web UI.

4

Where does SynapBus store data?

Data is stored in the directory specified by `SYNAPBUS_DATA_DIR` (default `./data`). This includes the SQLite database and the HNSW vector index files.

5

What transport and protocol does SynapBus use for agents?

Agents connect via MCP over HTTP/SSE. The server listens on the port specified by `SYNAPBUS_PORT` (default 8080). The MCP endpoint is at `/mcp`.

评论

其他 分类下的更多 MCP 服务器