Connect your AI agent
Stele runs a hosted endpoint that any agent can connect to. Paste one URL into ChatGPT, Claude, Cursor, or anything else that speaks MCP, sign in once through your browser, and that agent reads and writes the same record your coding agents already keep. There's nothing to install and no key to manage.
Why connect an agent that doesn't write code
Your record fills in while you build, because the agents doing the building are the ones wired into it. But a lot of the questions about a project get asked somewhere else: drafting a launch post in ChatGPT, answering a customer on your phone, briefing a contractor who will never open your repository.
Connecting those agents buys you three things.
- Project context in agents that never touch code. The agent writing your changelog can read the tasks that shipped. The one answering a support question can find the decision that explains the behaviour.
- Your record from anywhere. The endpoint is reachable from the web and mobile apps, so you can ask what's in flight, or file a task the moment you think of it, without a laptop.
- Remote automations. A scheduled agent can run with nothing of yours switched on: turn an incident report into a task overnight, sweep for work that's gone stale, or brief tomorrow's session before you sit down.
Your endpoint
One URL, the same for everyone. Your account is what scopes it, so there is nothing personal in it and nothing to keep secret.
When a client connects, it sends you to Stele's sign-in page in your browser. Approve once and the client stores its own credentials and refreshes them on its own. You never paste a token, and you can disconnect from the client at any time.
The hosted endpoint is included on the free plan, with no card and no trial. Connect as many agents as you like.
Connect your agent
Find your client below. Each one takes under a minute, and the flow is the same everywhere: give it the URL, then approve the sign-in.
ChatGPT
Custom connectors live behind developer mode, so turn that on first.
- Open Settings → Security and login and turn on Developer mode.
- Go to Plugins and press the + button.
- Paste
https://app.stele-ai.dev/api/mcpas the server URL and choose OAuth for authentication. - Approve the sign-in when ChatGPT opens it.
Stele then appears under the developer-mode tool in the composer. If you add tools later, use refresh in the app's settings to pull them in.
Claude — web, desktop, and mobile
- Open Settings → Connectors.
- Press Add, then Add custom connector.
- Paste
https://app.stele-ai.dev/api/mcpand press Add. Leave the advanced settings alone — sign-in is handled for you. - Approve the sign-in when Claude opens it.
The connector covers every Claude client on your account, including the mobile apps and sessions that keep running after you close the tab.
Claude Code
Use this for remote and cloud sessions, where there is no machine to install onto. On your own machine, install the plugin instead — see Install & first run.
Cursor
Add Stele to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
Cursor prompts you to sign in the first time it reaches the server. You can also add it from Customize in the sidebar.
VS Code
Run MCP: Add Server from the command palette, or write .vscode/mcp.json yourself:
Codex
That writes an [mcp_servers.stele] entry to your Codex config, which you can also edit by hand.
Any other MCP client
Stele is a standard remote MCP server over streamable HTTP, with standard sign-in discovery. Any client that supports remote servers can connect: give it the URL and let it handle the rest. Clients that only speak the older event-stream transport work too.
Try it
Once the client says it's connected, ask it something only your record knows.
List my Stele projects, then tell me what's in flight on the first one and what the last few decisions were.
A connected agent works across every project you're a member of, so it asks which one you mean. Name your project once and it carries it through the conversation. If you don't have a project yet, the agent can create one for you.
Connected agents aren't read-only. They can file a task, claim it, close it with a note, and record a decision — the same lifecycle your coding agents follow, so nothing arrives in the record as an orphan.
What a connected agent can and can't do
It gets the record: search and recall, tasks and their lifecycle, knowledge, documents, provenance, comments, and workspaces. That's the whole graph surface, not a cut-down version of it.
It does not get your machine. The endpoint is a connection to your record, not to your files — a connected agent can't read your code, run your tests, or inspect a diff. Anything that has to certify what actually happened locally stays with the agent that has the repository in front of it. Stele refuses those steps over the endpoint rather than pretending it checked.
Connecting an agent gives it tools it can choose to call. The plugin goes further: it reads the record for you on every prompt and surfaces what bears on what you're doing, without the agent having to think to ask. If you write code on this machine, install the plugin as well — the two work on the same record.
If something goes wrong
- The client can't connect. Check the URL is exactly
https://app.stele-ai.dev/api/mcp, with no trailing slash and nothing after it. - It connects but shows no tools. Some clients cache the tool list from the first handshake. Disconnect and reconnect, or use the client's refresh control.
- It's connected but finds nothing. It's probably looking at the wrong project, or none. Ask it to list your projects, then name the one you mean.
- You want to revoke access. Remove the connector in the client. That's the only place the credentials live.