The GSA MCP server exposes the same tenant-isolated commerce and result services as REST, with scope-filtered discovery, mutation guards, spend controls, and published-only result reads.
Transport is stateless Streamable HTTP (JSON responses) over HTTPS. The server implements initialize, ping, tool discovery and calls, reference resources (quickstart, webhook signing, the OpenAPI contract), and guided prompts(order-testing, verify-coa, track-order). Discovery filters tools by the key's scopes; event-specific read scopes for webhook creation are enforced when that tool is called.
Two auth paths. Hosted connectors (claude.ai, Claude Desktop, ChatGPT, and any OAuth-capable client) onboard with just the endpoint URL — the server implements OAuth 2.1 authorization-code + PKCE with dynamic client registration, and tokens map onto the same scoped, spend-capped key model. CLIs and editors can instead send a static, revocable gsa_live_… bearer key. Never put a real key in an install URL; the one-click links here carry only the endpoint.
Client setup
Connect any agent in under a minute
The server speaks both auth paths: OAuth 2.1 with dynamic client registration — hosted connectors (claude.ai, ChatGPT) need only the endpoint URL — and scoped API keys for CLIs and editors. Endpoint: https://www.goldstandardanalytics.com/api/mcp
Claude (claude.ai, Desktop, Code, API)
OAuth one-click + API key
Hosted Claude connects with just the URL via OAuth. Claude Code takes one command. The Claude API attaches the server per-request with the MCP connector.
claude.ai / Claude Desktop
Settings → Connectors → Add custom connector.
Paste https://www.goldstandardanalytics.com/api/mcp and click Add. The OAuth sign-in and consent screen run automatically — no key to paste.
Enable the connector's tools from the chat composer's tools menu.
Codex reads remote Streamable HTTP MCP servers from config.toml and resolves the bearer token from an environment variable, so no secret is ever written to the file.
Create a scoped key in Account → Developer API and export it as GSA_AGENT_TOKEN in your shell profile.
Add the server under [mcp_servers.gold_standard_analytics] in ~/.codex/config.toml.
Restart Codex, then confirm the server with /mcp inside a session.
For hosts without native remote MCP support, the mcp-remote bridge exposes this server as a local stdio process and handles the OAuth flow in your browser.
Add a conservative per-order and daily spending cap. Keep tool approval enabled.
Status and COA reader
orders:read, shipments:read, results:read
Tracks samples and reads published results without ordering or payment permissions.
Automation worker
Use webhooks:writeplus every subscribed event's resource-read scope; add webhooks:read or payment scopes only when the worker needs them.
Do not reuse this high-privilege key in a general chat client.
Mutation safety
A write-capable key is authorization, not intent. Order creation still requires a locked quote, confirm: true, an idempotency key, accepted customer terms, configured account addresses, scope checks, rate limits, and spend limits. Keep your client’s approval prompt enabled for quote consumption, orders, payment changes, and webhook mutations.
Verify the connection
List tools and confirm only the scopes you granted are visible.
Call gsa.catalog.list with a small limit and inspect the catalog revision.
Create a quote only after the read path works; confirm the cent total and expiry.
Before enabling ordering, set spend caps and leave mutation approval on.