Sutra

io.github.shivnathtathePublished by GitHub account shivnathtathev1.0.1Updated Oct 24, 2026

Private, portable memory and reusable skills for AI agents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Hosted Sutra service giving AI agents private, portable memory and reusable skills through 10 typed MCP tools.

What you can do
  • Read shared identity context, search memories by keyword, and list or load named project clusters
  • Save durable preferences, decisions, corrections and facts as observations
  • Export all stored memories for data portability
  • Discover user-enabled skills, load a skill and its resource index, and read individual skill resources
  • Upload a new immutable skill version after explicit authorization
When to use it
Useful when you want context to carry across chat sessions and across different AI clients, or when you maintain reusable skills that several agents should load. Suited to users who want a vendor-neutral, exportable memory store rather than per-client history.
Requirements
A remote Streamable HTTP endpoint; no local package. A Sutra account is required. Authentication is OAuth 2.1 (browser consent) or a dedicated revocable API key sent in an Authorization header, depending on the client. Network access to the hosted service.
Before you install
The service stores what agents write, so review what gets saved; write, upload and export operations are meant to require deliberate user intent. Keep API keys and OAuth tokens out of checked-in configuration files and use the client's secret mechanism. Export produces a full copy of stored memories. Read the security, privacy and terms documents before connecting sensitive workflows.

Installation

In SourceWeft

  1. Open Sutra 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.shivnathtathe%2Fsutra/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": {
    "sutra": {
      "type": "http",
      "url": "https://sutra-c3or.onrender.com/mcp"
    }
  }
}

README

[Sutra - one private memory layer for every AI agent]

Open MCP integration files for the hosted Sutra service.
Connect private, portable context to the AI agents you already use.

Website  ·  All integrations  ·  Smithery  ·  Glama  ·  Support

[MCP Streamable HTTP] [OAuth 2.1] [Ten typed tools] [MIT licensed integrations]

Connect Sutra

text
https://sutra-c3or.onrender.com/mcp
ConnectionUse whenWhat happens
OAuth 2.1Your client supports remote MCP authorization.The client opens Sutra in your browser, requests consent, and stores its grant.
API keyYour client expects an Authorization header.You create a dedicated, revocable key in Sutra and store it with the client's secret mechanism.
  1. Create a Sutra account.
  2. Choose a client configuration below.
  3. Complete OAuth or enter a dedicated API key when prompted.
  4. Confirm the client discovers 10 tools.
  5. Try: Use Sutra to list my project clusters. Ask before saving anything.

[!IMPORTANT] Never put a real Sutra API key, OAuth token, memory export, or password in a checked-in configuration file.

Choose Your Client

ClientAuthenticationConfiguration
CursorOAuthclients/cursor-mcp.json
OpenCodeOAuth with DCR and PKCEclients/opencode.json
VS Code / GitHub CopilotRevocable API keyclients/vscode-mcp.json
Claude CodeRevocable API keyGuided CLI setup
Cursor   OAuth

Install this repository as an Agent Plugin, or add the following to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "sutra": {      "url": "https://sutra-c3or.onrender.com/mcp"    }  }}

Connect the server and complete Sutra's browser authorization flow.

OpenCode   OAuth + DCR + PKCE

Merge clients/opencode.json into your global or project opencode.json:

json
{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "sutra": {      "type": "remote",      "url": "https://sutra-c3or.onrender.com/mcp",      "oauth": {}    }  }}

Authorize and inspect the connection:

sh
opencode mcp auth sutraopencode mcp list
VS Code and GitHub Copilot   API key

Copy clients/vscode-mcp.json to .vscode/mcp.json, or merge it into your user MCP configuration:

json
{  "inputs": [    {      "id": "sutra-api-key",      "type": "promptString",      "description": "Sutra API key",      "password": true    }  ],  "servers": {    "sutra": {      "type": "http",      "url": "https://sutra-c3or.onrender.com/mcp",      "headers": {        "Authorization": "Bearer ${input:sutra-api-key}"      }    }  }}

Start Sutra from the MCP configuration editor. VS Code requests the key through a masked input instead of storing it in the file.

Claude Code   API key

Use the Sutra CLI for guided setup:

sh
npm install -g @shivnathtathe/sutra-clisutra connect claude-code

The CLI requests a dedicated key and safely writes the supported local configuration. It does not send your key to this repository.

Need another agent? Sutra publishes current instructions for all 22 tested integrations.

Confirmed Compatibility

[The 22 AI clients independently tested with Sutra]

11 web agents use OAuth. 11 CLI and desktop agents use dedicated API keys. Product names and marks belong to their respective owners.

Tool Surface

Sutra exposes 10 typed tools. Read operations retrieve only the context needed for the current request. Write, upload, and export operations require deliberate user intent.

Context and memoryAccessPurpose
read_contextReadLoad the user's shared identity context.
search_memoryReadFind targeted memories by keyword.
list_clustersReadDiscover available project clusters.
get_clusterReadLoad one known project cluster.
write_observationWriteSave one durable preference, decision, correction, or fact.
export_allExportExport all user memories for data portability.
Reusable skillsAccessPurpose
list_skillsReadDiscover skills explicitly enabled by the user.
get_skillReadLoad an enabled skill and its resource index.
get_skill_resourceReadRead one resource referenced by an enabled skill.
upload_skillWriteUpload a new immutable skill version after explicit authorization.

Data Boundaries

Sutra doesSutra does not
Stores observations deliberately saved by a user or authorized agent.Copy every conversation from a connected client.
Isolates unrelated context in named project clusters.Share one cluster with every request automatically.
Shows the source agent, tags, and activity for stored memories.Hide writes inside an opaque client profile.
Supports revocable OAuth grants and per-client API keys.Require one permanent credential across all agents.
Provides an explicit full export for portability.Lock user memory to one AI vendor.

Read Security and data boundaries, the Privacy Policy, and the Terms of Service before connecting sensitive workflows.

Repository Contents

text
.|-- plugin.json             # Agent Plugins 1.0 manifest|-- mcp.json                # Portable Streamable HTTP connection|-- server.json             # Official MCP Registry metadata|-- clients/|   |-- cursor-mcp.json|   |-- opencode.json|   `-- vscode-mcp.json|-- docs/|   |-- client-support.md|   `-- security-and-data.md`-- assets/    |-- integration-grid.svg    |-- readme-hero.png       # Pixel-tested GitHub banner    |-- readme-hero.svg       # Editable banner source    `-- sutra-logo.png

Open Integration Layer

This repository contains the open-source manifests, examples, documentation, and artwork needed to connect clients to Sutra. Corrections for changing client formats are welcome; see CONTRIBUTING.md and SECURITY.md.

The files in this repository are licensed under the MIT License. The hosted Sutra backend, dashboard, APIs, infrastructure, datasets, service implementation, and trademarks remain proprietary and are not included. The Sutra logo and third-party product names and marks are excluded from the MIT grant; see NOTICE.

Context should outlast the chat window.
Create your private workspace

Source: README.md at commit f706b30

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

1
  1. v1.0.1LatestSep 16, 2026

Score

85% 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
  • License10 pts