Direct answer: Amplitude's MCP server can expose provider-supported product analytics, funnels, cohorts, metrics, charts, experiments, and feature-flag context under the connected user's permissions. Aurora's catalog points to the official US endpoint, allowing a verified connection to support traction analysis and investor-update preparation without presenting Aurora as an event-ingestion pipeline or a substitute for metric governance.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Amplitude remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Amplitude connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.amplitude.com/mcp |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Amplitude remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Review permitted Amplitude users, events, funnels, cohorts, metrics, charts, and dashboards.
- Analyze provider-supported retention, conversion, or behavioral questions for a defined cohort and date range.
- Inspect experiment and feature-flag context where available to the authenticated user.
- Prepare a reproducible traction summary with source chart, filters, metric definition, and reporting period.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Amplitude
Fundraising traction narrative
Outcome: A defensible set of adoption, conversion, or retention evidence for a fundraising update.
- Agree on the Amplitude project, metric definition, cohort, segment, and comparison period.
- Retrieve the relevant funnel, cohort, chart, or metric and preserve its source reference.
- Draft a concise explanation that separates observed result, interpretation, and caveat.
Human decision: The product or data owner validates the metric and the founder approves external wording.
Investor product-diligence response
Outcome: A source-backed answer to a specific question about activation, engagement, retention, or experiment learning.
- Translate the diligence question into an explicit analysis plan and permitted Amplitude objects.
- Retrieve the smallest evidence set that answers the question and note missing data.
- Prepare the answer with chart links, dates, filters, and a clear boundary on what can be concluded.
Human decision: A data owner confirms accuracy and leadership decides what is appropriate to disclose.
How to connect Amplitude to Aurora
- Select Amplitude in Aurora's catalog and confirm whether the account is hosted in the US or EU region.
- Complete Amplitude OAuth as a user with access limited to the required organization and project.
- For EU accounts, validate the provider's EU endpoint rather than assuming the US catalog endpoint will route correctly.
- Discover tools and retrieve one known chart or metric from the target project.
- Compare the result with Amplitude before using it in any investor-facing draft.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Amplitude inherits the user's permissions and can expose sensitive product behavior. Aurora may analyze and prepare, but the metric owner must approve definitions, cohorts, filters, time windows, statistical interpretation, and disclosure. Any chart, cohort, experiment, flag, or project write needs separate explicit approval.
Limitations to understand
- Amplitude MCP is not an event-ingestion method and does not replace a correct analytics implementation.
- US and EU accounts use different provider endpoints.
- Available tools depend on Amplitude plan, organization settings, project permissions, and admin MCP controls.
- A chart can be technically correct while still answering the wrong business question.
Verification checklist
- Confirm the live catalog endpoint, oauth_dynamic auth type, and account region.
- Complete OAuth with a least-privilege user and record the organization and project.
- Discover the live tool list and retrieve one known metric or chart.
- Compare result, filters, cohort, and date window with the Amplitude UI.
- Have the metric owner reproduce and approve the result.
- Confirm no page copy implies event ingestion, guaranteed accuracy, or autonomous investor reporting.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Amplitude official MCP documentation (amplitude.com)
- Amplitude official MCP documentation 2 (amplitude.com)
- Amplitude official MCP documentation 3 (amplitude.com)