gRPC Support

Bifurc supports saved gRPC request definitions, proto-aware exploration, server reflection, and a dedicated gRPC mock server workflow.

---

What you can do

• save gRPC requests with service, method, metadata, and message body
• import and store .proto files
• discover services and methods through server reflection
• detect unary, server-streaming, client-streaming, and bidirectional workflows
• run gRPC mocks through the Bifurc gRPC mock server
• keep protocol definitions and request examples under workspace version control

---

Typical workflow

1. Open Request → gRPC
2. Create a request tab
3. Enter the server address
4. Import a proto file or use server reflection
5. Select a service and method
6. Fill in the JSON request body and metadata
7. Invoke the method and inspect the response

---

Mocking workflow

1. Open Mock → gRPC
2. Add or reuse a proto file
3. Create a mock bound to a service and method
4. Define success or error responses
5. Start the Bifurc gRPC mock server
6. Point your client at the configured mock-server port

---

Important architecture note

gRPC is not intercepted through the HTTP proxy path the same way REST, GraphQL, and SOAP traffic are. Instead, Bifurc provides a dedicated gRPC mock server flow because gRPC relies on HTTP/2 framing.

---

Good use cases

• local development against unstable gRPC backends
• validating request and response shapes from proto contracts
• standing up fast mock services for streaming-oriented clients