gRPC CLI vs gRPC Swagger

gRPC CLI is a free, open-source command-line tool in the gRPC repository for inspecting services and calling remote methods. It can send unary RPCs, attach metadata to requests, display metadata received from a server, and handle common server authentication. With server reflection, it can list services and methods; when reflection is unavailable, local proto files can supply service definitions and request or response types. Requests can be read in proto text or wire form. Responses can be displayed as text or written to a file in wire form. Streaming RPC support is described as a desired capability, not part of the documented core functionality. The tool runs on Linux, macOS, and Windows, but must be built from repository source. The documented process uses CMake and the `make grpc_cli` build target. Its documentation describes the tool as not yet up to par in user-friendliness and says grpcurl is better maintained in its current state. The gRPC repository identifies its license as Apache-2.0.

gRPC Swagger is a free, open-source debugging tool for discovering and calling gRPC methods through Swagger UI. It uses server reflection to scan a registered endpoint, identified by host and port, and then displays available services, method definitions, and parameters. Users can invoke methods with Swagger UI’s “Try it out” control, supplying request data and headers as JSON; the headers are passed to the gRPC server as metadata. Reflection must be enabled on the gRPC service, but the setup instructions say proto files and related implementations do not need modification. The project runs from a released JAR or from source and defaults to port 8080. Configuration can show registered services and expire inactive registrations after a chosen number of seconds. Documented endpoints cover registration, service listing, method calls, and Swagger documentation. It is self-hosted, available for API and web use, and licensed under MIT.