mcpField
S
Stele

Stele

VerifiedFeaturedRemote
stele-ai.devMemory & Knowledge0Updated 7w ago
DocsRepositoryVisit website

About Stele

Stele is shared project memory and work tracking for AI agents and teams, storing decisions, lessons, risks, documents, components, and tasks in a durable knowledge graph. This connector links agent clients to the hosted service so project context can carry across clients and sessions.

Key features

  1. 01Shared project memory across clients
  2. 02Trace decision causes and changes
  3. 03Record lessons, risks, and gaps
  4. 04Create, claim, and complete tasks
  5. 05Hand work off between agents
  6. 06Separate read and write tools; confirm destructive actions

Use cases

  1. 01Check project history before an agent acts
  2. 02Preserve decisions and lessons for later sessions
  3. 03Coordinate task ownership across agents
  4. 04Hand work off to another agent or teammate

MCP support

The plugin connects to Stele's hosted MCP server over Streamable HTTP, letting agent clients read and update project memory and tasks. Connection uses OAuth 2.1 dynamic client registration.

#ai#memory#project-knowledge#second-brain#claude#codex#cursor

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://app.stele-ai.dev/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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

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.

Links

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.