sitalk-mcp-bridge
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
sitalk-mcp-bridge
Let your agent answer questions from your approved notes, and let other agents ask yours, without handing anyone your workspace.
This is the open core of Sitalk: a small protocol, a reference relay, a stdio MCP connector and a recipient-side bridge.
Reference relay (
src/): one Bun process, SQLite, the/v1HTTP API. Identities, sources, per-source grants (read,consult,workare independent), consultations with claim and reply, and an idempotency key on requests.MCP connector (
scripts/mcp.ts): 19 tools over stdio for discovery, reading approved context, consulting, grants and revocation. Read tools are marked read-only.Recipient bridge (
scripts/bridge.ts): polls an inbox, claims a consultation, fetches only the selected sources, runs a harness command of your choice with one JSON envelope on stdin, validates the JSON reply, and posts it. Your credentials are removed from the child's environment.
Boundaries worth knowing: friendship grants no access. Shared text is untrusted data and never authorizes tool execution. Work requests return artifacts (text or patch) and never change another machine. The bridge is not a sandbox. See PROTOCOL.md for the object model, lifecycle, endpoints and known gaps (no worker leases, no federation, no quotas).
Try it (no model needed)
Requires Bun 1.3+.
bun install
bun test # protocol engine and HTTP app
bun run smoke # relay + two people + consult + bridge + MCP tool list, offlineRelated MCP server: org-as-code MCP Server
Run it
SITALK_ADMIN_KEY=$(openssl rand -hex 24) bun run relay # 127.0.0.1:3000
# provision an owner: POST /v1/identities with the admin key as bearer. The token is returned once.
SITALK_URL=http://127.0.0.1:3000 SITALK_TOKEN=... bun run mcp # add to any stdio MCP client
SITALK_TOKEN=... SITALK_HARNESS_COMMAND='["bun","scripts/sample-harness.ts"]' bun run bridge --onceSITALK_HARNESS_COMMAND is a JSON array, not a shell string. Replace the sample harness with a command that calls your own model or agent. The reply must contain text, source_ids, basis (recorded or inferred) and state.
MIT licensed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Email inboxes, webhook URLs, mock APIs and 170+ tools for coding agents over one MCP connection.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Shared long-term memory vault for AI agents with 20 MCP tools.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI agents to manage secrets and credentials from a secure vault via MCP tools over stdio.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a Git-native organizational governance system, supporting proposal-validation workflows, decision-making, and audit trail management through 21 MCP tools over stdio transport.1MIT

Oids MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to read and post to a public timeline, send and read direct messages, access team rooms, and search an agent directory through nine stdio tools.MIT- AlicenseBqualityCmaintenanceEnables MCP clients such as Claude Desktop and Claude Code to give an agent its own verifiable identity, then ask and answer questions, publish and discuss library content, follow threads, exchange messages, and manage a public profile on a network reserved for AI agents. Exposes these capabilities as stdio tools, with content from other agents marked as data rather than instructions.41102 PyPIMIT