Seltz MCP Server Moves to Markdown, Console Sign-In
New hosted endpoint, same tool names
Seltz published an update to its Model Context Protocol (MCP) server on November 12, 2026, moving the service to a new hosted endpoint at mcp.seltz.ai/mcp, according to the company's own changelog docs.seltz.ai. The migration changes the server's infrastructure address but leaves its existing tool names intact, meaning developers who integrated the search and fetch tools should not need to rename calls in their agent code, per the changelog.
Search and fetch now return Markdown
The most consequential change for developers building retrieval-augmented agents is a shift in output format. Previously, Seltz's search and fetch tools returned a JSON document complete with structuredContent and an outputSchema. As of this update, both tools instead return compact Markdown, the changelog states docs.seltz.ai. For agent frameworks that pipe tool output directly into a language model's context window, Markdown is generally lighter-weight and easier for models to parse than nested JSON, though it also means any downstream code expecting structured fields will need to be rewritten to parse the new format.
Console sign-in replaces bare key requirements
Authentication has also changed. Clients that connect to the MCP server without an API key are now redirected to the Seltz Console, where they sign in, select an organization if more than one is available, and approve access before the connection proceeds, the changelog says docs.seltz.ai. Developers who prefer static credentials can still authenticate using an API key passed in the x-api-key header or as an Authorization: Bearer token — both methods remain supported alongside the new console flow. Once a call is approved through the Console, billing is routed to whichever organization the user selected during sign-in.
Argument names aligned with REST API
Seltz also used the update to bring consistency across its surfaces: MCP tool arguments now use the same snake_case naming convention as the company's REST API, according to the changelog docs.seltz.ai. The alignment is a small but practical change for teams that maintain both REST and MCP integrations against Seltz, since it reduces the mental and code overhead of mapping between two different naming schemes for the same underlying parameters. Seltz's MCP server also appears in third-party directories tracking available MCP infrastructure Hugging Face dataset, underscoring its position as one of a growing number of hosted search-and-fetch tools agent builders can plug into without running their own infrastructure.


