Other clients

Requirements

• Transport: Streamable HTTP. The server is stateless; every request is a POST to the workspace URL.
• Auth: OAuth 2.1 authorization code with PKCE, discovered from the 401 challenge. Dynamic client registration is open, so no pre-registered client id is needed. Clients that insist on a static client id and secret cannot connect.
• Protocol: the current MCP specification; the previous generation is also answered.

Static bearer tokens are not an option. There is no API key that opens the MCP endpoint.

Configuration shape

Most clients take a JSON entry of this shape, with the field names varying slightly:

{
  "mcpServers": {
    "general-input": {
      "type": "http",
      "url": "https://cloud.generalinput.com/v1/mcp/<organizationId>"
    }
  }
}

On first use the client challenges, registers, and opens the General Input login page in a browser. Sign in and allow.

Verifying

A working connection lists the tools in the tool reference. A 404 means the URL lacks the workspace id; a 403 means the signed-in account is not a member of that workspace. See troubleshooting.