Granc 🦀
⚠️ Status: Experimental
This project is a working prototype intended for testing and development purposes. APIs, command-line arguments, and internal logic are subject to breaking changes. Please use with caution.
Granc (gRPC + Cranc, Crab in Catalan) is a lightweight, dynamic gRPC CLI tool written in Rust.
It allows you to make gRPC calls to any server using simple JSON payloads, without needing to compile the specific Protobuf files into the client. By loading a FileDescriptorSet at runtime, granc acts as a bridge between human-readable JSON and binary Protobuf wire format.
It is heavily inspired by tools like grpcurl but built to leverage the safety and performance of the Rust ecosystem (Tonic + Prost).
🚀 Features
- Dynamic Encoding/Decoding: Transcodes JSON to Protobuf (and vice versa) on the fly using
prost-reflect. - Metadata Support: Easily attach custom headers (authorization, tracing) to your requests.
- Fast Fail Validation: Validates your JSON before hitting the network.
- Smart Dispatch: Automatically detects if a call is Unary, Server Streaming, Client Streaming, or Bidirectional based on the descriptor.
- Server Reflection: Can fetch schemas directly from the server, removing the need to pass a local file descriptor set file (
.binor.pb). - Introspection Tools: Commands to list services and describe services, messages, and enums.
- Local Introspection: In addition to making network requests, Granc can also be used as a local introspection tool for file descriptor binary files. You can load a local
.binfile to inspect services, messages, and enums without needing to fetch the schema from a server.
- Local Introspection: In addition to making network requests, Granc can also be used as a local introspection tool for file descriptor binary files. You can load a local
- Zero Compilation Dependencies: Does not require generating Rust code for your protos. Just point to a descriptor file.
- Tonic 0.14: Built on the latest stable Rust gRPC stack.
📦 Installation
🛠️ Prerequisites
Granc needs to know the schema of the service you are calling. It can obtain this in two ways:
- Automatic Server Reflection: If the server has Server Reflection enabled, Granc can download the schema automatically.
- Local Descriptor File: You can provide a binary
FileDescriptorSet(.bin) generated byprotoc.
Generating Descriptors (Optional)
If your server does not support reflection, you must generate a descriptor file:
# Generate descriptor.bin including all imports
Note: The
--include_importsflag is crucial. It ensures that types defined in imported files (likegoogle/protobuf/timestamp.proto) are available for reflection.
📖 Usage
Syntax:
Global Arguments
| Argument | Description | Required |
|---|---|---|
<URL> |
Server address (e.g., http://[::1]:50051). Must be the first argument. |
Yes |
--file-descriptor-set |
Path to the binary FileDescriptorSet (.bin). If omitted, Granc attempts to use Server Reflection. |
No |
Commands
1. call (Make Requests)
Performs a gRPC call using a JSON body.
| Argument/Flag | Description | Required |
|---|---|---|
<ENDPOINT> |
Fully qualified method name (e.g., my.package.Service/Method). |
Yes |
--body |
The request body in JSON format. Object {} for unary, Array [] for streaming. |
Yes |
--header, -H |
Custom header key:value. Can be used multiple times. |
No |
Example using Server Reflection:
Example using a Local Descriptor File:
2. list (Service Discovery)
Lists all services exposed by the server (via reflection) or contained in the provided descriptor file.
Available Services:
- grpc.reflection.v1.ServerReflection
- helloworld.Greeter
Listing services from a file:
3. describe (Introspection)
Inspects a specific symbol (Service, Message, or Enum) and prints its Protobuf definition in a colored, human-readable format.
service Greeter {
rpc SayHello(helloworld.HelloRequest) returns (helloworld.HelloReply);
rpc StreamHello(stream helloworld.HelloRequest) returns (stream helloworld.HelloReply);
}
Describing a Message using a Local File:
message HelloRequest {
string name = 1;
int32 age = 2;
repeated string tags = 3;
}
Describing an Enum:
enum Status {
UNKNOWN = 0;
ACTIVE = 1;
INACTIVE = 2;
}
🔮 Roadmap
- Interactive Mode: A REPL for streaming requests interactively.
- Pretty Printing JSON: Enhanced colored output for JSON responses.
- TLS Support: Configurable root certificates and client identity.
🧩 Using as a Library
The core logic of Granc is decoupled into a separate library crate, granc-core.
If you want to build your own tools using the dynamic gRPC engine (e.g., for custom integration testing, proxies, or automation tools), you can depend on granc-core directly.
- Documentation & Usage: See the
granc-coreREADME for examples on how to use theGrancClientprogrammatically. - Crate:
granc-core
⚠️ Common Errors
**1. Service 'x' not found**
- Cause: The service name in the command does not match the package defined in your proto file.
- Fix: Check your
.protofile. If it haspackage my.app;andservice API {}, the full name ismy.app.API.
**2. Method 'y' not found in service 'x'**
- Cause: Typo in the method name or the method doesn't exist.
- Fix: Ensure case sensitivity matches (e.g.,
GetUservsgetUser).
**3. h2 protocol error**
- Cause: This often occurs when the JSON payload fails to encode after the connection has already been established, or the server rejected the stream structure.
- Fix: Double-check your JSON payload against the Protobuf schema.
🤝 Contributing
Contributions are welcome! Please run the Makefile checks before submitting a PR:
📄 License
Licensed under either of:
- Apache License, Version 2.0 (LICENSE-APACHE)
- MIT license (LICENSE-MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.