Leash
io.github.open-leashPublished by GitHub account open-leashv1.0.2Updated Nov 3, 2026
Hosted remote MCP for protected account access, permissions, activity history and supported undo.
Overview
Leash's hosted MCP server (secure.lea.sh); OAuth sign-in required; Streamable HTTP.
No AI overview yet: these facts come from the registry entry and the server itself.
- Endpoint
- secure.lea.sh
- Last checked
Installation
In SourceWeft
- Open Leash in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.open-leash%2Fleash/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"leash": {
"type": "http",
"url": "https://secure.lea.sh/mcp"
}
}
}README
Leash
A little peace of mind for your AI. Free.
Leash connects your AI to your accounts through configurable protections. Review activity, control each AI's access, and undo supported reversible actions when undo is enabled. Only activity routed through Leash is covered.
Install
Install Leash from your AI's plugin directory when its listing is available, or install this package from GitHub in clients that support repository plugins. Enable the Leash connection and sign in at openleash.com when prompted. Each installation receives a separate, revocable connection. Some hosts share one connection across multiple bots; Leash cannot distinguish bots that use the same credentials. Use separate connections where your host supports them. The shared endpoint is https://secure.openleash.com/mcp. Never append another person's token or put a personal link in a public package.
For Gemini CLI: gemini extensions install https://github.com/open-leash/leash-plugin. Run /mcp auth leash if sign-in is requested. For OpenClaw, use openclaw plugins install git:github.com/open-leash/[email protected], then inspect the enabled leash bundle. Its compatibility format is Cursor; no native code runs. For other clients, use their remote HTTP server option with the shared endpoint and OAuth. A public directory submission is not the same as an approved listing. Check the release notes for current availability.
Run the Leash setup skill or ask: "Check Leash is connected without accessing my personal accounts." Success must come from the check_connection tool, not merely from listing available tools. Then connect the accounts you want at https://openleash.com/personal.
Instructions and privacy
This package includes a setup skill and a personal-account skill. Cursor loads a packaged rule and Gemini CLI loads GEMINI.md while the extension is enabled. A plugin cannot guarantee that all AI activity uses Leash. For a permanent preference in other clients, add the credential-free rule from GEMINI.md to the client's supported personal instructions. ChatGPT web uses Settings → Personalization → Custom instructions; Claude app uses Settings → General → Instructions for Claude; Cursor uses User Rules. A chat reply confirming the connection does not confirm that these settings were saved. Preserve your other instructions. Never add credentials to memory or shared files.
This integration uses personal Leash connections. The personal-connection retention terms apply to it; workspace and desktop-client retention terms describe the separate business service. Protection checks may process relevant request and response content with TypeSafe JEV. Audit history is retained for 90 days. When undo is enabled, supported recovery details are encrypted and retained for up to 7 days. Turning undo off stops new recovery capture. Read https://openleash.com/privacy for the full policy.
Remove
Disable or uninstall the plugin in your AI, remove any Leash-specific saved preference you added, then remove its connection in Your AIs at https://openleash.com/personal. Removing that connection revokes access immediately without disconnecting other AIs.
Support
https://openleash.com/contact · [email protected]
Privacy: https://openleash.com/privacy · Terms: https://openleash.com/terms
This repository contains only public integration metadata, instructions and brand assets. Leash's gateway and protection engine remain private.
Source: README.md at commit 840b523
Tools
0Version history
2- v1.0.2LatestNov 3, 2026
- v1.0.1Oct 20, 2026
Score
75% 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
Declare a license in the repository or the registry entry.