AskMVAR — MCP tools

Asking the server…

Connecting a client

{
  "mcpServers": {
    "askmvar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "ENDPOINT", "--transport", "http-only"]
    }
  }
}

Why --transport http-only: this server speaks Streamable HTTP. Left to choose, some clients probe the older SSE transport first, whose opening move is a session-less GET; this server answers that 400 and the client reports Invalid Accept header. Expected TEXT_EVENT_STREAM, which points at the header rather than at the transport. The flag skips the probe. If you see that error, the client is on the wrong transport, not sending the wrong header.

Paste into your client's config file. If it already has an mcpServers block, add the askmvar entry to it rather than replacing the file — a second mcpServers key silently wins over the first and the other servers disappear.

Claude Desktop — macOS ~/Library/Application Support/Claude/claude_desktop_config.json

Windows %APPDATA%\Claude\claude_desktop_config.json

Claude Code — claude mcp add --transport http askmvar ENDPOINT_PLAIN