Docs

Quickstart

Laterbase is an MCP server. Connect your agent once, and it pins out-of-scope work and whatever you put off, checks for known issues when it starts a task, and picks pins up when you're ready.

1. Connect your agent

Many clients sign in with your account, so there's nothing to copy; the rest take an API key you create on the dashboard's Connections page.

See every client Laterbase works with.

2. Work as usual

The agent pins whatever gets left for later, whether it spotted something out of scope or you said refunds can wait, and says so in its reply. Each pin is written for whoever picks it up: what's wrong or wanted, where, how it came up and how to go about it.

3. Pick it up later

Ask what's worth picking up? and the agent lists pins by priority: the payoff for the effort, the risk of waiting, and what each one unblocks. It claims a pin before starting, links the PR when it opens one and resolves the pin once it merges. Everyone in the workspace sees the same backlog, on the dashboard and through their own agents.

What your agent is told

The server sends these instructions when an agent connects, so you don't have to explain any of it:

Laterbase is your team's shared backlog of out-of-scope and deferred work from coding sessions. When work gets left for later, because you notice something out of scope worth doing or the user puts something off ("let's do that later"), pin it with create_pin straight away, without asking, and mention it in your next reply. Never leave it as a note in chat. When you start a task, call pins_near on the files it involves to see known issues there. When asked what to work on, use search_pins: by default it lists open pins by priority. Before starting a pin, read it in full with get_pin and claim it; link your PR to it as fixed_in as soon as the PR is open, and resolve the pin once the PR merges. If you stop partway, release it with a note saying where you left off. When you mention a pin to a person, link its key to the pin's url, e.g. [ACME-42](url).

The tool reference has every tool's description, parameters and response, generated from the server itself.