Skip to content

docs(integrations): document Go support for the Postman MCP server - #2211

Open
wolo-lab wants to merge 4 commits into
google:mainfrom
wolo-lab:wolo/postman-go
Open

docs(integrations): document Go support for the Postman MCP server#2211
wolo-lab wants to merge 4 commits into
google:mainfrom
wolo-lab:wolo/postman-go

Conversation

@wolo-lab

@wolo-lab wolo-lab commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Problem

docs/integrations/postman.md carries Python and TypeScript tabs only, so Go users have no documented path to the Postman MCP server. Nothing is missing in adk-go to support it: both transports the page describes are already covered by google.golang.org/adk/v2/tool/mcptoolset.

Summary

  • Adds the lst-go language-support span and a Go tab with the same Local MCP Server and Remote MCP Server sub-tabs as the other two languages.
  • The local sample runs the server through mcp.CommandTransport over exec.CommandContext(ctx, "npx", args...), and passes the key in cmd.Env layered on os.Environ() so npx keeps its PATH.
  • The remote sample uses Config.Endpoint with Config.Auth. Passing auth.StaticToken sets the same Authorization: Bearer <key> header that the Python and TypeScript samples write by hand.
  • Optional server flags live in an args slice, so the existing Configuration wording ("add --full or --code to the args list") reads correctly for Go as well and needed no change.

Verification

  • Both samples compile, pass go vet, and are gofmt-clean against google.golang.org/adk/v2@v2.3.0. Config.Endpoint and Config.Auth shipped in v2.1.0, so the remote sample needs that version or later.
  • mkdocs build --strict exits 0. The built page renders three top-level tabs (Python, TypeScript, Go), each with both sub-tabs, and two language-go code blocks.

Staged: https://deploy-preview-2211--adk-docs-preview.netlify.app/integrations/postman/

The Postman page carried Python and TypeScript tabs only, so Go users had no
documented way to reach the Postman MCP server even though adk-go needs no new
code for it. Both transports the page describes are already covered by
google.golang.org/adk/v2/tool/mcptoolset: mcp.CommandTransport for the local
npx server, and Config.Endpoint plus Config.Auth for the remote streamable HTTP
server, where auth.StaticToken produces the same Authorization: Bearer header
the Python and TypeScript samples set by hand.

Add the lst-go language-support span and a Go tab with the same Local and
Remote sub-tabs as the other two languages, following the pattern used by
agent-registry.md and mcp-toolbox-for-databases.md. The optional server flags
are held in an args slice so the Configuration section's "add --full or --code
to the args list" reads correctly for Go as well.
@netlify

netlify Bot commented Sep 8, 2026

Copy link
Copy Markdown

Deploy Preview for adk-docs-preview ready!

Name Link
🔨 Latest commit f3ce809
🔍 Latest deploy log https://app.netlify.com/projects/adk-docs-preview/deploys/6aa24d609e46f60008f0e700
😎 Deploy Preview https://deploy-preview-2211--adk-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants