English Français العربية

Stele

Official registry Developer tools

Shared project memory for AI coding agents: decisions, lessons, risks and tasks in one graph.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http stele 'https://app.stele-ai.dev/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "stele": {
            "type": "http",
            "url": "https://app.stele-ai.dev/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Stele — MCP connector plugin
  2. What's in here
  3. What the connector does
  4. Working locally
  5. Requirements
  6. Authentication
  7. Tool safety
  8. Links
  9. License

Stele — MCP connector plugin

Stele is shared project memory and work tracking for AI agents and the people who work with them. It keeps decisions, lessons, risks, documents, components, and tasks in one durable knowledge graph, so work can continue across agent clients without losing the project's history.

This repository is the plugin that connects an agent client to Stele. It follows the Agent Plugins open standard and contains configuration and documentation only.

What's in here

plugin.json          Agent Plugins manifest
mcp.json             Stele's hosted MCP server, over Streamable HTTP
skills/stele/        Guidance on when and how an agent should use Stele

There is no build step, no bundled binary, and no executable code. Stele itself runs as a hosted service; this plugin only points at it.

What the connector does

Once connected, an agent can:

  • Recall what a project already knows before it acts, instead of starting cold.
  • Trace why a decision was made, what caused it, and what it replaced.
  • Capture decisions, lessons, risks, and gaps as they happen, so they survive the conversation that produced them.
  • Coordinate tasks — create, claim, and complete them — so two agents don't duplicate each other's work.
  • Hand off cleanly to the next agent, session, or teammate.

The bundled skill tells the agent when reaching for these tools is appropriate and when it isn't, which matters on a surface where the agent chooses for itself.

Working locally

This connector is the whole product on a chat or IDE surface. If you also work in a local repository, Stele's command-line tool adds automatic recall — relevant prior decisions, risks, and open work surface as you go, rather than only when someone thinks to ask. See the documentation.

The tool is optional. Nothing in this plugin requires it, downloads it, or runs it for you.

Requirements

A Stele account and at least one project. Signing in through the connector creates the account if you don't already have one, and no paid plan is required to connect.

Authentication

OAuth 2.1 with dynamic client registration (RFC 7591). Your client registers itself on first connection and opens Stele's sign-in page. Access is limited to the projects you own or belong to.

No credentials, tokens, or secrets are stored in this repository, and none are needed to install it.

Tool safety

Stele's tools are split so a client can tell safe operations from unsafe ones. Read-only tools are annotated as such and never modify data. Write tools are separate. Every consequential operation — cancelling, force-claiming, unlinking, retiring, merging — lives in a single destructive tool that always prompts before acting. No tool mixes these tiers.

License

MIT — see LICENSE.

Frequently asked questions

What is Stele?

Shared project memory for AI coding agents: decisions, lessons, risks and tasks in one graph.

How do I install Stele?

It runs as a remote server. In Claude Code: claude mcp add --transport http stele 'https://app.stele-ai.dev/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Stele need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Stele open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Stele?

It is published by Stele-Dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.