Segue

Segue is a neutral context-relay service built on the Model Context Protocol (MCP) that lets AI assistants hand off working state to one another. Instead of rebuilding context every time you switch tools, you save a brief or plan in one assistant, receive a short three-syllable handle (like brelavo), and load it in any other MCP-connected assistant. The service launched with support for Claude, ChatGPT, Cursor, Windsurf, Codex, and any other MCP-compliant client.

What It Is

Segue is an MCP server that acts as a shared context store across AI assistants. It solves the "silo problem" — the fact that each AI tool holds your working state independently and cannot brief a competing tool. Segue sits between your assistants as a neutral relay: it belongs to no vendor, stores context as plain Markdown, and requires explicit human action at every transfer step. MCP itself is described on the site as an open standard stewarded by the Linux Foundation.

How the Three-Step Workflow Works

The core loop is deliberately simple:

• Save: An AI calls save_context with your brief, notes, or plan and receives a short handle.
• Pass: You carry that handle — say it aloud, type it on a phone, write it on a sticky note — to the next assistant.
• Load: The next AI calls load_context with the handle and picks up exactly where you left off.

Handles are three pronounceable syllables, case-insensitive, and unique within your account. They are meaningless outside your account by construction, so a leaked or guessed handle cannot be resolved by anyone else.

Design Principles

Segue is built around six stated commitments:

• Explicit transfers — nothing syncs behind your back; every save and load is a deliberate action.
• Human-scale handles — a word you can say or type from memory, even when the context behind it runs to 100,000 characters.
• Vendor neutrality — any MCP-compliant client connects the same way.
• Privacy — handles resolve only inside your account.
• Portability — every context is stored as plain Markdown, browsable, editable, searchable, and downloadable as a .md file.
• Revocability — each connected AI gets scoped permissions and short-lived tokens, listed in Settings with one-click revoke; stored credentials are hashed.

Where It Fits in a Multi-Tool Workflow

The site identifies three primary use cases:

• Cross-tool handoffs — plan in Claude, implement in Cursor, draft in ChatGPT, carrying the brief between them.
• Session continuity — save a curated brief before hitting a context limit or closing for the night, rather than dragging a sprawling transcript forward.
• Standing briefs — keep project background, house style, and preferences saved to bootstrap any newly connected assistant on demand.

Setup Path

Setup is described as pasting one prompt: the AI configures itself and walks the user through OAuth sign-in. Each AI gets scoped permissions and short-lived tokens. The MCP transport used is streamable HTTP with OAuth.