Introduction
Slaunt is a hosted MCP server that gives coding agents a memory shared across your whole team. An agent can look up what was decided or shipped before it starts, record what it did when it finishes, and show up live in Quaero, where people can see what every agent is doing and stop it.
| Endpoint | https://central-mcp-ccr-production.up.railway.app/mcp |
| Transport | Streamable HTTP, protocol 2025-11-25 |
| Auth | OAuth 2.1 + PKCE S256, dynamic registration, scope mcp:tools |
| Rate limit | 240 requests/min |
| Body limit | 1 MiB |
How it fits together
Each chat is a thread and each task inside it is a run. Runs are what Quaero displays, so the lifecycle calls (run_begin, run_step, run_end) are what make an agent visible and stoppable. Inside a run, the agent reads and writes Slaunt Context (short events like "deployed X" or "decided Y"), Tasks, Room files and GitHub.
For Claude Code and Codex, the installer adds hooks that make the lifecycle calls automatically. Other clients have to make them from the model.
Where to go next
- Quickstart: Claude Code and Codex in one command.
- Transport: sessions, auth and the lifecycle over raw HTTP, for building a client.
- Tools overview: every tool's parameters and responses.
- Errors: what each failure means and how to fix it.