Go FAQs

Question 1

What authentication and authorization features does Go include?

Accepted Answer

Go provides robust OIDC (OpenID Connect) authentication and authorization server discovery. This ensures your MCP servers are secure and standards-compliant, validating tokens via JWKS and handling `WWW-Authenticate` headers for unauthorized requests.

Question 2

Can server capabilities be customized per session with Go?

Accepted Answer

Yes, Go features dynamic capability negotiation. This allows for per-session logic to tailor capabilities like tools, resources, sampling, and elicitation, based on client requirements. You can use both static containers and dynamic provider functions for configuration.

Question 3

What kind of session management does Go offer?

Accepted Answer

Go includes pluggable session storage, offering both in-memory and Redis implementations out-of-the-box. This flexibility ensures persistent and scalable session management for your MCP servers.

Question 4

How does Go support flexible deployment and scaling?

Accepted Answer

Go offers seamless deployment flexibility, enabling you to start with a minimal stdio CLI prototype and incrementally scale up to horizontally distributed HTTP services. It's built to handle high loads without requiring changes to your application's fundamental business logic.

Question 5

What is Go (mcp-server-go) designed to do?

Accepted Answer

Go (mcp-server-go) is a Go module for building scalable Model Context Protocol (MCP) servers. It allows you to create API services that range from simple CLI applications to horizontally scaled, OIDC-protected streaming HTTP deployments without rewriting your core business logic.

Go

Go

Key Features

Use Cases

Key Features

Use Cases