2026-09-22
-
The Sui gRPC API now supports the gRPC-Web transport. Browsers and Node.js can call the Sui gRPC API over fetch without a separate proxy.
-
The Nodit MCP server now supports Streamable HTTP transport with OAuth sign-in. You can search for Nodit in the Claude connectors and connect directly, without placing an API Key in the URL.
Major Updates
1. Sui gRPC-Web Support
The Sui gRPC API can now be called over the gRPC-Web transport. Native gRPC requires HTTP/2, which made it difficult to call directly from browsers or HTTP/1.1 environments. gRPC-Web runs on fetch, so web applications and Node.js can use it without a separate proxy.
| gRPC | gRPC-Web | |
|---|---|---|
| Endpoint | sui-mainnet.nodit.io:443 | https://sui-mainnet.nodit.io:443 (same host) |
| Protocol | HTTP/2 + TLS | HTTP/1.1 or HTTP/2 |
| Authentication | x-api-key metadata | x-api-key header |
| Streaming | Server, client, and bidirectional | Server streaming only |
| Typical clients | grpcurl, grpcio, grpc-java | Sui TypeScript SDK (@mysten/sui/grpc), buf curl, Armeria |
Request and response messages are identical for both transports, so all 22 documented methods can be used as they are. The SuiGrpcClient in the official Sui TypeScript SDK uses gRPC-Web as its default transport, so pointing its endpoint at Nodit is all that is required.
Each Sui gRPC method page in the API documentation now has a gRPC / gRPC-Web tab. The gRPC-Web tab shows the headers and constraints of the transport, field names in the TypeScript SDK convention (lowerCamelCase), and code examples for buf curl, TypeScript, and Java.
2. Nodit MCP Streamable HTTP and Connector Support
The Nodit MCP server now supports Streamable HTTP transport with OAuth sign-in. The existing SSE method required appending ?apiKey=... to the server URL. Now, signing in with your Nodit account is all it takes to connect. The server automatically locates and uses an API Key from a project in the signed-in account, so the key is never exposed in a URL or configuration file.
| Before (SSE) | After (Streamable HTTP) | |
|---|---|---|
| Server URL | https://mcp.nodit.io/sse?apiKey={YOUR_API_KEY} | https://mcp.nodit.io/mcp |
| Authentication | API Key in the URL | Nodit account OAuth sign-in |
| API Key entry | Entered by the user | Not required (used automatically from the project) |
Connection steps by client are as follows.
- Claude (web/desktop): Enter
Noditin the connector search box, click [Connect], and sign in with your Nodit account. - Claude Code: Register with
claude mcp add --transport http nodit https://mcp.nodit.io/mcp. A sign-in window opens on the first tool call. - Cursor and other MCP clients: Set
urltohttps://mcp.nodit.io/mcpin the configuration file.
If the account has multiple projects in RUNNING status, use the newly added list_nodit_projects tool to review the list and specify the project in your prompt. If there is only one project, it is selected automatically.
The existing SSE method remains available for the time being, but it has been deprecated in the MCP specification, so Streamable HTTP is recommended for new connections. To migrate, remove the existing SSE connector and add it again using the new method.