Stele
dev.stele-aiPublished by stele-ai.devOfficial publisherv1.0.0Updated Oct 24, 2026
Shared project memory for AI coding agents: decisions, lessons, risks and tasks in one graph.
Overview
Hosted MCP connector that gives AI coding agents shared project memory: decisions, lessons, risks and tasks in one knowledge graph.
- What you can do
- Recall what a project already knows before acting, and trace why a decision was made and what it replaced
- Capture decisions, lessons, risks and gaps as they happen so they outlive the conversation
- Coordinate tasks by creating, claiming and completing them so agents don't duplicate work
- Hand off context cleanly to the next agent, session or teammate
- When to use it
- Useful when several AI agents or people work on the same project and need durable shared context, or when you want decisions and risks recorded rather than lost between sessions. It is a hosted service, so it fits chat and IDE surfaces without local setup.
- Requirements
- A Stele account and at least one project; signing in through the connector creates the account, and no paid plan is required to connect. Connection is to a hosted Streamable HTTP endpoint with OAuth 2.1 and dynamic client registration, so the client registers itself and opens Stele's sign-in page. No environment variables, headers or local runtime are needed.
Installation
In SourceWeft
- Open Stele 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/dev.stele-ai%2Fstele/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": {
"stele": {
"type": "http",
"url": "https://app.stele-ai.dev/api/mcp"
}
}
}README
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
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.
Links
License
MIT — see LICENSE.
Source: README.md at commit 7d6a9f4
Tools
0Version history
1- v1.0.0LatestSep 30, 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