Skip to content

docs: add amplitude setup guide - #235

Closed
cursor[bot] wants to merge 2 commits into
mainfrom
forgebot/grw-367-intake-test-amplitude-setup-guide-and-catalogue-entry-fixes-docs
Closed

cursor[bot] wants to merge 2 commits into
mainfrom
forgebot/grw-367-intake-test-amplitude-setup-guide-and-catalogue-entry-fixes-docs

Conversation

@cursor

@cursor cursor Bot commented Nov 3, 2026

Copy link
Copy Markdown

Linear: GRW-367 (synthetic intake test for the MCP catalogue worker, not a customer request). Please keep this PR as a draft.

Guide slug: amplitude

Related Speakeasy PR (catalogue entry change): https://github.com/speakeasy-api/gram/pulls?q=is%3Apr+head%3Aforgebot%2Fgrw-367-intake-test-amplitude-setup-guide-and-catalogue-entry-fixes

Why

Amplitude runs two hosted MCP servers, one per data region (US and EU). The Speakeasy catalogue entry com.amplitude/mcp only carries the US remote, so readers need a guide that tells them which URL to use and adds the server by URL. The ticket settles the add-server path: Hosted remotely for both regions, with no doctrine change.

What changed

New guide under guides/amplitude/ only:

  • meta.yaml: US https://mcp.amplitude.com/mcp and EU https://mcp.eu.amplitude.com/mcp remotes, both tenanted: true (the reader picks the URL for their region), OAuth with dynamic client registration.
  • external.md: find the region from the Amplitude sign-in hostname (app.amplitude.com or app.eu.amplitude.com), then two conditional admin checks: Settings > Content Access > MCP, and the Use MCP (read) / Use MCP (write) role actions under Org Settings > Role Management > AI Features. MCP access is on by default, so most organizations change nothing.
  • speakeasy.md: Hosted remotely with both URLs, User Identity with Auto-Configure and the region's issuer, Server Availability fallback, and first sign-in.
  • research.md: the dossier, with provenance for every rendered fact.

The branch also carries a merge of main (for the lint-guide task fix). It doesn't change the PR diff.

Review first

  • The region step in external.md.
  • The admin step wording: Amplitude publishes the menu path for the MCP content access page but not the labels of its allow or block controls, so the guide says "content access controls" as Amplitude does.

Checks

  • mise run lint-guide -- ../guides/amplitude: passed (--json returned []).
  • Guide validation as in CI (cd go/internal/gen && go run .): passed. It adds refs amplitude/us and amplitude/eu. go/generated is 1384 KiB, under the 5 MiB budget, with no file over 512 KiB. Generated output was discarded, not committed.
  • go test . in go/ with the generated output in place, and go test ./internal/guidecheck ./cmd/lint-guide: passed.

Not verified

  • Both /mcp URLs return 401 with a resource_metadata challenge, and both issuers advertise CIMD and a /register endpoint (re-probed 2026-11-03). CIMD or DCR registration was not exercised end to end, because anonymous registration would create a client at Amplitude.
  • The rendered Speakeasy dashboard was not spot-checked. Screenshots in the guide are placeholders.

Release

The guide reaches the product only after the docs Go module release and the Speakeasy bump PR. Both are bot-owned.

Open in Web View Automation 

speakeasyforgebot and others added 2 commits November 2, 2026 09:13
Covers finding the Amplitude region, the organization admin checks for MCP access and MCP role actions, adding the US or EU server in Speakeasy with Hosted remotely, and first sign-in.

Linear: GRW-367
Co-authored-by: forge.bot <forge.bot@speakeasy.com>
Linear: GRW-367
Co-authored-by: forge.bot <forge.bot@speakeasy.com>
@linear-code

linear-code Bot commented Nov 3, 2026

Copy link
Copy Markdown

GRW-367

@TristanSpeakEasy

Copy link
Copy Markdown
Member

Closing so the catalogue worker can be rerun end to end from a clean state.

@TristanSpeakEasy
TristanSpeakEasy deleted the forgebot/grw-367-intake-test-amplitude-setup-guide-and-catalogue-entry-fixes-docs branch November 3, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants