grpcc | A gRPC cli interface for easy testing against gRPC servers

To use it, you only need the service's .proto file, which describes the RPC service, and the address (host:port) of the service. grpcc can talk to local or remote services:. By default, grpcc will attempt to make a secure connection to the service. If you need an insecure connection, you can pass in the -i flag.
client - this is the gRPC client connection to your service. The usage instructions will show the available methods, as will using tab completion by typing client.<tab>
printReply - a convenience callback for printing the response of an RPC call (nicer than console.log) (alias: pr)
streamReply - a convenience callback for printing the response of an stream's 'data' event (nicer than console.log) (alias: cr)
createMetadata - a convenience function for converting plain javascript objects to gRPC metadata (alias: cm)
printMetadata - a convenience callback for printing the metadata of an RPC call (nicer than console.log) (alias: pm)
All calls require an argument matching the spec, so if you have an empty message type in your proto for some calls, you'll be sending in {} as the first argument to those calls
Remember that Protobuf.js will camelCase class and property names
Unary calls can take a callback as the second argument which has the signature function(err, reply). reply will be an object matching the message type as per your proto
For streaming calls, you'll want to use the EventEmitter object that is returned when the call is made and connect to the appropriate events. Note the grpc nodejs docs are out of date, check out the examples to see how to work with streams.