Sirro

io.github.JonathanmbergPublished by GitHub account Jonathanmbergv0.1.1Updated Oct 25, 2026

Shared memory for AI coding agents. Save once, reuse from Cursor, Claude Code, Codex.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Sirro is a remote MCP server providing shared memory for AI coding agents, so context saved once can be reused across Cursor, Claude Code and Codex.

What you can do
Save shared memory once and reuse it from multiple AI coding agents such as Cursor, Claude Code and Codex. The manifest lists no individual tools, so the exact operations are not documented in the supplied material.
When to use it
Useful when you work with several AI coding agents and want context or notes stored once to carry over between them instead of being re-entered in each tool.
Requirements
A remote MCP endpoint at sirro.dev, connected over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Sign-in is through OAuth, so the server receives an authenticated account connection. The material does not describe what memory is stored, where it is kept, or who can read it, so treat saved coding context as shared data before relying on it.

Installation

In SourceWeft

  1. Open Sirro in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Jonathanmberg%2Fsirro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sirro": {
      "type": "http",
      "url": "https://www.sirro.dev/beta/mcp/sirro-public-beta"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.1LatestSep 24, 2026
  2. v0.1.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.