Omniscio

OmniscioGuidesMCP server has a "url" but no "type"

MCP server has a "url" but no "type" in Claude Code

Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .

What is the exact message?

MCP server "<name>" has a "url" but no "type"; add "type": "http" (or "sse" / "ws") to this entry

Your server's own name stands where the angle brackets are. The rest is printed as Anthropic's MCP page shows it.

What does it mean?

An entry with no type is read as a stdio server: a program Claude Code starts locally. A stdio server is launched by a command, not reached at a URL.

Your entry has a url and no type, so those two facts contradict each other. Anthropic calls it a configuration error, and Claude Code skips that one server while the rest of the session carries on.

Nothing is wrong with the server itself. The entry is incomplete, so Claude Code never gets as far as connecting to it, and one line is the whole repair.

How do I fix it?

  1. Find the entry. In .mcp.json, ~/.claude.json, or the file named by --mcp-config, locate the server the message names.
  2. Add the type. A remote HTTP server takes "type": "http". Anthropic also accepts "streamable-http" as an alias for http, so a config written for the MCP specification works unchanged.
  3. Use the other two only if they fit. "sse" is the deprecated Server-Sent Events transport, and "ws" is a WebSocket server. Anthropic recommends HTTP where it is available.
  4. Or let the CLI write the entry. claude mcp add --transport http <name> <url> adds a remote HTTP server with the transport set correctly.
  5. Retry the servers in a running session. /mcp reconnect all retries every server that failed or needs authentication. Anthropic notes it needs Claude Code v2.1.284 or later; earlier versions print MCP server "all" not found.

How do I know it worked?

  • The message no longer appears when the session starts.
  • claude mcp list shows the server with a health status such as ✔ Connected, instead of leaving it off the list.
  • claude mcp get <name> shows the entry without an Issue: line, which is where a failure detail appears.

Where these answers come from

  • The message, the reason for it, the types it names and the streamable-http alias: Connect Claude Code to tools via MCP, read November 18, 2026.
  • The claude mcp add --transport http form and the health statuses in claude mcp list: the same page, read November 18, 2026.
  • The Issue: line in claude mcp get: the same page's server status detail, read November 18, 2026.

Common questions

Does one bad entry stop the others?

No. Anthropic says Claude Code skips that server. The entry is reported and the rest of your MCP servers are still loaded.

Can I leave the type out and rely on the URL?

Not in Claude Code. It reads an entry with no type as a stdio server, so the URL alone is not enough and the entry stays skipped until it has a type.

Which type do I want for a hosted server?

http for the remote servers Anthropic recommends, and sse only where a server still offers that older transport. ws is for a WebSocket server.

I use plugins, not a config file. Does this apply?

The message names a configuration entry, so look for the entry the message names in whichever file holds it. The MCP errors guide covers the plugin-provided servers that fail for a different reason.