Sequel exposes a single hosted MCP endpoint. Point any MCP-capable AI tool at it and authenticate with your API key:
https://api.sequel.sh/mcpThere are two ways to install it into your agent: the Sequel CLI (one command — it creates the API key and writes the config for you) or manual setup (copy-paste the config into each tool yourself).
Fastest: the Sequel CLI
The CLI installs Sequel into a coding agent in a single step. It signs you in, provisions a scoped API key for that agent, and writes the right config to the right place — no keys to copy by hand.
Install the CLI
One line installs the latest CLI (@sequelsh/cli) with whatever package manager you have:
curl -fsSL https://sequel.sh/install | shPrefer npm directly? npm install -g @sequelsh/cli@latest works too (or pnpm add -g, bun add -g, yarn global add).
Sign in
sequel loginThis opens your browser to authenticate and pick an organization.
Install Sequel into your agent
Run install and pick an agent from the list, or pass its slug directly:
sequel installThe CLI creates an API key named after the agent, then writes its MCP config. For agents that support it, you'll also be asked for a scope — global (available everywhere on this machine) or local (this project only). Pass --scope to skip that prompt:
sequel install claude-code --scope globalWith the slug and --scope given, install never prompts, so a coding agent can run it for you. Add --no-browser (on login or install) to print the sign-in URL instead of opening a browser.
When sequel login is run without a terminal (piped, as a coding agent runs it), it returns straight away with JSON containing the sign-in url and finishes the sign-in in the background; sequel login --status reports logged_in, pending, or failed, and sequel login --wait blocks until a pending sign-in completes. A piped sequel install waits for a pending sign-in rather than starting its own.
For agents with a skills directory, the same command also installs the Sequel skill: a short SKILL.md that tells the agent Sequel's playbooks exist and how to reach them. Every agent gets the playbooks through MCP regardless; the skill file just makes the agent reach for them without being told.
| Agent | Slug | Scopes | Skill file |
|---|---|---|---|
| Claude Code | claude-code | global, local | ~/.claude/skills/sequel/ or .claude/skills/sequel/ |
| Claude Desktop | claude | global | via MCP only |
| Cursor | cursor | global, local | via MCP only |
| VS Code | vscode | global, local | via MCP only |
| Windsurf | windsurf | global | via MCP only |
| Zed | zed | global, local | via MCP only |
| Codex | codex | global | via MCP only |
| OpenClaw | openclaw | global | via MCP only |
| Hermes | hermes | global | via MCP only |
Verify
Restart the agent and ask it to "list my Sequel connections." If it answers, you're connected.
Already have the CLI? sequel install claude-code (or any slug above) re-runs setup for that agent at any time.
Manual setup
Prefer to wire it up yourself — or using ChatGPT, Claude.ai, or Gemini? Generate a key under Settings → API Keys in your Sequel dashboard and drop it into the Authorization header shown in each snippet below. Some tools — like ChatGPT and Claude.ai — can also sign in with OAuth instead of a static key; see API keys & authentication for the difference.
Expand a tool for its exact setup. Replace sql_your_api_key with a real key from your dashboard.
Claude (web)Install the Sequel MCP server in Claude (web)
Click 'Open in Claude' to add Sequel as a custom connector on claude.ai, then sign in with your Sequel account when Claude asks. No API key needed. Or add the connector manually with the details below.
Open in Claude (web)claude.ai → Settings → Connectors (fallback — manual install)
Name: Sequel Remote MCP server URL: https://api.sequel.sh/mcp Authentication: OAuth — sign in with Sequel when prompted
Claude CodeInstall the Sequel MCP server in Claude Code
Run the command below in your terminal to register Sequel with Claude Code globally — `--scope user` makes it available across every project. Drop that flag to install it for the current project only.
Run in your terminal
claude mcp add --scope user --transport http sequel https://api.sequel.sh/mcp \
--header "Authorization: Bearer sql_your_api_key"Replace sql_your_api_key with a real key from your Sequel dashboard.
CursorInstall the Sequel MCP server in Cursor
Click 'Open in Cursor' to install automatically, or add the config below to .cursor/mcp.json manually.
.cursor/mcp.json (fallback — manual install)
{
"mcpServers": {
"sequel": {
"url": "https://api.sequel.sh/mcp",
"headers": {
"Authorization": "Bearer sql_your_api_key"
}
}
}
}Replace sql_your_api_key with a real key from your Sequel dashboard.
VS CodeInstall the Sequel MCP server in VS Code
Click 'Open in VS Code' to install automatically. VS Code will prompt you for your API key. Or add the config below to .vscode/mcp.json manually.
.vscode/mcp.json (fallback — manual install)
{
"servers": {
"sequel": {
"type": "http",
"url": "https://api.sequel.sh/mcp",
"headers": {
"Authorization": "Bearer sql_your_api_key"
}
}
}
}Replace sql_your_api_key with a real key from your Sequel dashboard.
WindsurfInstall the Sequel MCP server in Windsurf
Add the snippet below to your Windsurf MCP config file, then reload Windsurf. Note Windsurf uses `serverUrl` (not `url`).
~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sequel": {
"serverUrl": "https://api.sequel.sh/mcp",
"headers": {
"Authorization": "Bearer sql_your_api_key"
}
}
}
}Replace sql_your_api_key with a real key from your Sequel dashboard.
ChatGPTInstall the Sequel MCP server in ChatGPT
In ChatGPT, go to Settings → Connectors and add a new MCP connector with the details below. ChatGPT also supports signing in with OAuth instead of a static key.
ChatGPT Settings → Connectors
Server URL: https://api.sequel.sh/mcp Authorization header: Bearer sql_your_api_key
Replace sql_your_api_key with a real key from your Sequel dashboard.
CodexInstall the Sequel MCP server in Codex
Run the command below in your terminal to register Sequel with OpenAI Codex.
Run in your terminal
codex --add-mcp-server \
--name sequel \
--transport http \
--url https://api.sequel.sh/mcp \
--header "Authorization: Bearer sql_your_api_key"Replace sql_your_api_key with a real key from your Sequel dashboard.
ZedInstall the Sequel MCP server in Zed
Add the snippet below to your Zed settings file (Cmd+, to open it), then restart Zed.
~/.config/zed/settings.json
{
"context_servers": {
"sequel": {
"url": "https://api.sequel.sh/mcp",
"settings": {
"headers": {
"Authorization": "Bearer sql_your_api_key"
}
}
}
}
}Replace sql_your_api_key with a real key from your Sequel dashboard.
GeminiInstall the Sequel MCP server in Gemini
Add the snippet below to your Gemini CLI settings file, then restart the CLI.
~/.gemini/settings.json
{
"mcpServers": {
"sequel": {
"url": "https://api.sequel.sh/mcp",
"httpOptions": {
"headers": {
"Authorization": "Bearer sql_your_api_key"
}
}
}
}
}Replace sql_your_api_key with a real key from your Sequel dashboard.
OpenClawInstall the Sequel MCP server in OpenClaw
Run the command below to register Sequel with your OpenClaw gateway, then reload it with `openclaw mcp reload`. You can also add the server to `~/.openclaw/openclaw.json` under `mcp.servers` by hand.
Run in your terminal
openclaw mcp set sequel '{"url":"https://api.sequel.sh/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer sql_your_api_key"}}'Replace sql_your_api_key with a real key from your Sequel dashboard.
HermesInstall the Sequel MCP server in Hermes
Add the snippet below to your Hermes config under `mcp_servers`, then run `/reload-mcp` in Hermes (or restart it).
~/.hermes/config.yaml
mcp_servers:
sequel:
url: "https://api.sequel.sh/mcp"
headers:
Authorization: "Bearer sql_your_api_key"Replace sql_your_api_key with a real key from your Sequel dashboard.
Grok BotInstall the Sequel MCP server in Grok Bot
Grok Bot has no MCP config file; you add a server by asking the bot. Paste the message below into a chat, confirm the name and URL it reads back, then click Authorize on the connect card and sign in to Sequel. Say “custom server” so it adds this endpoint instead of searching the plugin marketplace. Check it under Settings → Plugins → Yours, then attach it to a task with @sequel.
Send to your bot in chat
Add a custom MCP server called sequel at https://api.sequel.sh/mcp
MuseInstall the Sequel MCP server in Muse
Muse has no “add MCP server” screen; it writes its own custom connector instead. Send it the message below and it will build an MCP client on its VM, test Sequel's tools, and save the integration as a reusable skill. Sign in through Muse's secure credential prompt rather than pasting anything into the conversation.
Send to Muse in chat
Build a custom connector to Sequel. It is a remote MCP server over streamable HTTP at https://api.sequel.sh/mcp and it uses OAuth, so ask me to sign in through the secure credential flow. Connect with the official MCP SDK, test every tool end to end, and save it as a reusable skill.
dotsInstall the Sequel MCP server in dots
A dot uses the plugins on your ChatGPT account, so you add Sequel in ChatGPT and the dot has it with no extra step. Turn on developer mode in Settings, add a connector named Sequel with the URL below, choose OAuth and sign in. Then set the plugin to “Allow read-only tools” under Settings → Plugins so reads run without interruption.
ChatGPT → Settings → Connectors (developer mode)
Server URL: https://api.sequel.sh/mcp Authentication: OAuth, sign in with Sequel when ChatGPT asks
Using a tool that isn't listed?
Any client that supports the Model Context Protocol over streamable HTTP can connect using the URL and Authorization header above.