https://mcp.seltz.ai/mcp, so you have nothing to install or update. You need a Seltz account, which you can create in the Console. Your client opens the Console so you can sign in when it connects. You only need an API key if your client can’t sign in.
Already connected? Connections you made with an API key keep working. To switch to Console sign-in, remove the server and add it again. If a tool call fails with an unknown argument name, refresh or reconnect the server. See the November 2026 changelog for what changed.
Install
Pick your client below. If you don’t see it, the Other clients tab has the settings any MCP client needs.- Claude Code
- VS Code
- Codex
- Cursor
- Antigravity
- Other clients
Add the server:Then run
/mcp in Claude Code, select seltz, and authenticate. Sign in to the Seltz Console in the browser that opens, then click Allow.Claude Desktop and claude.ai
Claude’s desktop and web apps connect through the Seltz connector in Claude’s connector directory.- In Claude, open Customize from the menu in the left panel, then go to Connectors. On claude.ai, you can go straight to Customize → Connectors.
- On the Discover tab, search for Seltz and click Connect.
- In the Seltz Console page that opens, sign in, choose your organization if you belong to more than one, and click Allow.
Add to Claude
Name it
Seltz and set the remote MCP server URL to https://mcp.seltz.ai/mcpClaude connectors require a paid Claude plan (Pro, Max, Team, or Enterprise).
Clients that only run local servers
Some clients can only launch MCP servers as local processes, as Claude Desktop does for servers in itsclaude_desktop_config.json file. The mcp-remote package bridges them to the hosted server. It needs Node.js.
mcp-remote opens the Seltz Console sign-in in your browser the first time it connects. To send your API key directly instead, pass it as a header. The key goes in env because some clients on Windows split arguments that contain spaces:
Authentication
Every request to the server bills one Seltz organization. Clients connect in one of two ways:
With sign-in, Seltz bills the organization you pick and attributes the calls to you. With an API key header, Seltz bills the key’s organization. Either way, calls cost the same as the matching Search and Fetch API calls.
Manage connected apps
Connected apps in the Console lists the apps you’ve allowed, per organization. You can remove one app or disconnect them all. Organization admins also see members’ connections on the Organization tab. They can remove a member’s apps, or block the member from connecting until they lift the block. Seltz refuses calls from a removed or blocked connection right away, and the client asks you to sign in again.Tools
The server exposes two tools. Your client reads their full schemas from the server, so the agent knows how to call them. Both tools return Markdown for an agent to read.search takes a required query, plus these optional arguments:
fetch takes urls, a list of 1 to 5 absolute URLs, and rejects duplicates. It reads HTML and plain-text pages, and returns unsupported_content_type for PDFs, images, and other binaries. One call returns at most 100,000 characters of page text, split equally among the pages, and the server cuts a longer page and notes its full length. It returns one result per URL, either ok with the page as Markdown or error with a code such as url_not_accessible or timeout, and one URL failing doesn’t affect the others. See Fetch for more on how it reads pages.
Parsing results in code? Use the REST API instead. The MCP server writes its output for agents to read, and its wording can change. The Search and Fetch endpoints return JSON described by the OpenAPI spec, take the same argument names, and accept an API key from the Console.
Troubleshooting
Sign-in shows "MCP access is blocked"
Sign-in shows "MCP access is blocked"
An organization admin blocked you from connecting. Ask them to lift the block under Connected apps → Organization in the Console.
Tool calls say "The Seltz API refused the request. Reconnect the Seltz server"
Tool calls say "The Seltz API refused the request. Reconnect the Seltz server"
This message has two causes:
- Someone removed the app under Connected apps. Reconnect the server and sign in again. In Claude Code, run
/mcp, select the server, and authenticate. - Your organization is out of credit. Reconnecting won’t fix this. Add credit under Billing in the Console, then try the call again.
Tool calls fail with "Invalid, expired, or revoked API key"
Tool calls fail with "Invalid, expired, or revoked API key"
This applies to clients that connect with an API key header. The client connected, but Seltz rejected the key when a tool ran. Check the key in the Console, and make sure the header reads
Bearer YOUR_API_KEY with a space after Bearer.A tool call fails with an unknown argument name
A tool call fails with an unknown argument name
search takes snake_case names such as max_results and from_date, the same as the REST API. A call with an old camelCase name such as maxResults fails, and the error lists the names the tool accepts. If your client keeps a saved copy of the tool list, such as a ChatGPT connector, refresh or reconnect the server.The client doesn't list the Seltz server
The client doesn't list the Seltz server
Check the config file for JSON syntax errors, then restart the client or reload its MCP servers. Clients also name the URL field differently: Antigravity expects
serverUrl, and VS Code expects a servers block with "type": "http". If your client can only launch local servers, use mcp-remote.mcp-remote fails to start
mcp-remote fails to start
mcp-remote runs through npx, so the client needs Node.js on its PATH. Run npx -y mcp-remote https://mcp.seltz.ai/mcp in a terminal to see the error directly.