Other MCP clients

Any client that speaks streamable HTTP MCP with OAuth works with Moshi. The configuration is the same three lines everywhere.

{
  "mcpServers": {
    "moshi": {
      "type": "http",
      "url": "https://mcp.moshi.ai/mcp"
    }
  }
}

After you add the block, trigger the sign-in flow from the client’s connector or MCP panel. You select your organization during sign-in.

Where the config lives

Client	Location	Note
Cursor	`~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one
VS Code	`.vscode/mcp.json`	VS Code names the top-level key `servers`, not `mcpServers`.
Anything else	Whatever the client calls its MCP config

Do not paste an OAuth access token into a configuration file. The hosted server issues and refreshes tokens through the browser sign-in flow.

Some clients support only a static credential. Use an organization API key in the authorization header instead:

Authorization: Bearer <moshi-api-key>

See Authentication for how to issue a key and what it scopes.

Symptom	Cause and fix
`Authorization required`, or a `401`	The connection is not signed in. Reconnect from the client’s MCP panel.
The client never opens a browser	The client does not support OAuth for remote servers. Use an API key.
A new Moshi tool is missing	The tool list is cached per connection. Reconnect the server.

Remove the server block from the config, or disconnect it in the client’s MCP panel.