feat(integrations): add support for amplitude mcp#5568
Open
hassan254-prog wants to merge 1 commit intomasterfrom
Open
feat(integrations): add support for amplitude mcp#5568hassan254-prog wants to merge 1 commit intomasterfrom
hassan254-prog wants to merge 1 commit intomasterfrom
Conversation
![propel-code-bot[bot]](https://avatars.githubusercontent.com/in/1179004?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Changes suggested due to broken logo assets and missing or inconsistent documentation links.
Status: Changes Suggested | Risk: Medium
Issues Identified & Suggestions
- Restore valid SVG markup to prevent broken logos:
amplitude-mcp.svg,amplitude-mcp-eu.svg - Add connect guide URLs for MCP providers:
providers.yaml - Align integration guides section with standard template:
amplitude-mcp.mdx
Review Details
📁 11 files reviewed | 💬 4 comments
Instruction Files
├── .claude/
│ ├── agents/
│ │ └── nango-docs-migrator.md
│ └── skills/
│ ├── agent-builder-skill/
│ │ ├── EXAMPLES.md
│ │ └── SKILL.md
│ ├── creating-integration-docs/
│ │ └── SKILL.md
│ └── creating-skills-skill/
│ └── SKILL.md
├── AGENTS.md
└── GEMINI.md
👍 / 👎 individual comments to help improve reviews for you
hassan254-prog
commented
Mar 5, 2026
| optional: true | ||
| pattern: '^(?:analytics\.eu\.)?amplitude\.com$' | ||
|
|
||
| amplitude-mcp: |
Contributor
Author
There was a problem hiding this comment.
We will split this into two integrations and avoid using the nango subdomain interpolation as we do for other integrations. Since this uses dynamic client registration, our customers can configure them separately by registering two integrations for the 2 respective regions. Their end users can then select the region they belong to.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the problem and your solution
Add Amplitude MCP integration configuration and documentation
This PR introduces support for the Amplitude MCP provider, adding provider definitions for US and EU endpoints and corresponding documentation assets. It also adds new documentation pages, snippets, and logo references to surface the integration in the docs navigation.
Key Changes
• Added new provider entries
amplitude-mcpandamplitude-mcp-euwith MCP OAuth2 settings and proxy configuration inpackages/providers/providers.yaml• Created documentation page
docs/api-integrations/amplitude-mcp.mdxwith quickstart and usage examples• Added generated snippets for tooling and use cases in
docs/snippets/generated/amplitude-mcp/PreBuiltTooling.mdxanddocs/snippets/generated/amplitude-mcp/PreBuiltUseCases.mdx• Registered the new docs page in
docs/docs.jsonand added template logo references inpackages/webapp/public/images/template-logos/amplitude-mcp.svgandpackages/webapp/public/images/template-logos/amplitude-mcp-eu.svgPossible Issues
• Ensure the MCP server URLs and OAuth endpoints are correct for both regions (
mcp.amplitude.comvsmcp.eu.amplitude.com).• Verify that the docs path in
packages/providers/providers.yaml(https://nango.dev/docs/api-integrations/amplitude-mcp) matches the actual doc route.This summary was automatically generated by @propel-code-bot