@sentry/junior-amplitude 0.95.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,21 @@
1
+ # `@sentry/junior-amplitude`
2
+
3
+ Read-only Amplitude product analytics for Junior through Amplitude's hosted MCP server.
4
+
5
+ ## Install
6
+
7
+ ```bash
8
+ pnpm add @sentry/junior @sentry/junior-amplitude
9
+ ```
10
+
11
+ ```ts
12
+ import { defineJuniorPlugins } from "@sentry/junior";
13
+
14
+ export const plugins = defineJuniorPlugins(["@sentry/junior-amplitude"]);
15
+ ```
16
+
17
+ Junior starts Amplitude's per-user OAuth flow when the agent first needs Amplitude data. The plugin exposes a fixed allowlist of Amplitude's documented search, retrieval, list, and query tools across analytics, taxonomy, session replay, experiments, feature flags, cohorts, guides and surveys, feedback, and agent analytics. Rendering, creation, editing, update, sync, merge, and deletion tools are not available to the agent.
18
+
19
+ The default MCP endpoint is `https://mcp.amplitude.com/mcp`. Set `AMPLITUDE_MCP_URL` to the regional endpoint documented by Amplitude when the deployment uses another data region.
20
+
21
+ Full setup guide: https://junior.sentry.dev/extend/amplitude-plugin/
package/package.json ADDED
@@ -0,0 +1,18 @@
1
+ {
2
+ "name": "@sentry/junior-amplitude",
3
+ "version": "0.95.0",
4
+ "private": false,
5
+ "publishConfig": {
6
+ "access": "public"
7
+ },
8
+ "type": "module",
9
+ "repository": {
10
+ "type": "git",
11
+ "url": "git+https://github.com/getsentry/junior.git",
12
+ "directory": "packages/junior-amplitude"
13
+ },
14
+ "files": [
15
+ "plugin.yaml",
16
+ "skills"
17
+ ]
18
+ }
package/plugin.yaml ADDED
@@ -0,0 +1,53 @@
1
+ name: amplitude
2
+ display-name: Amplitude
3
+ description: Read-only Amplitude analytics, taxonomy, replay, feedback, experiments, and product content
4
+
5
+ env-vars:
6
+ AMPLITUDE_MCP_URL:
7
+ default: https://mcp.amplitude.com/mcp
8
+
9
+ mcp:
10
+ url: ${AMPLITUDE_MCP_URL}
11
+ allowed-tools:
12
+ - search
13
+ - get_from_url
14
+ - get_context
15
+ - get_project_context
16
+ - get_workspace_context
17
+ - get_charts
18
+ - get_dashboard
19
+ - get_cohorts
20
+ - get_experiments
21
+ - get_users
22
+ - get_flags
23
+ - get_deployments
24
+ - get_agent_results
25
+ - get_events
26
+ - get_properties
27
+ - get_custom_or_labeled_events
28
+ - get_transformations
29
+ - get_group_types
30
+ - get_session_replays
31
+ - list_session_replays
32
+ - get_session_replay_events
33
+ - query_chart
34
+ - query_charts
35
+ - query_amplitude_data
36
+ - query_experiment
37
+ - get_cohort_sync_destinations
38
+ - get_cohort_syncs
39
+ - get_cohort_sync_history
40
+ - get_branches
41
+ - list_guides_surveys
42
+ - get_guide_or_survey
43
+ - get_feedback_insights
44
+ - get_feedback_comments
45
+ - get_feedback_mentions
46
+ - get_feedback_sources
47
+ - get_feedback_trends
48
+ - query_agent_analytics_metrics
49
+ - query_agent_analytics_sessions
50
+ - query_agent_analytics_spans
51
+ - get_agent_analytics_conversation
52
+ - search_agent_analytics_conversations
53
+ - get_agent_analytics_schema
@@ -0,0 +1,64 @@
1
+ ---
2
+ name: amplitude
3
+ description: Query read-only Amplitude product analytics. Use when users ask about active users, product usage, events, segmentation, funnels, conversion, retention, charts, dashboards, experiments, cohorts, taxonomy, session replay, feature flags, guides, surveys, feedback, agent analytics, or individual user activity in Amplitude. Do not use for changing Amplitude charts, dashboards, experiments, cohorts, flags, taxonomy, or project configuration.
4
+ ---
5
+
6
+ # Amplitude Analytics
7
+
8
+ Use this skill for read-only product analytics through Amplitude's hosted MCP server.
9
+
10
+ ## Workflow
11
+
12
+ 1. Define the question before querying:
13
+
14
+ - Identify the metric or analysis type: active users, event segmentation, funnel, retention, chart, dashboard, experiment, cohort, taxonomy, session replay, feature flag, guide or survey, feedback, agent analytics, or user activity.
15
+ - Preserve explicit event names, property names, chart IDs, dashboard IDs, experiment IDs, cohort IDs, and user IDs exactly.
16
+ - Use the user's explicit time range. For relative ranges, state the concrete dates in the answer.
17
+ - If the request has no time range, use the shortest conventional range that answers it and state the assumption.
18
+
19
+ 2. Discover the current Amplitude tool:
20
+
21
+ - Inspect the available Amplitude MCP tools for the required analysis.
22
+ - Use the exact live tool name and schema. Do not guess Amplitude MCP tool names or arguments.
23
+ - Prefer direct chart, dashboard, experiment, cohort, or user lookup when the user provides its identifier.
24
+ - If project or organization scope is ambiguous, inspect accessible scope through the read-only catalog and ask one focused question only when multiple plausible targets remain.
25
+
26
+ 3. Query narrowly:
27
+
28
+ - Request only the events, properties, segments, metrics, and dates needed for the answer.
29
+ - Prefer one complete query over several overlapping queries.
30
+ - For comparisons, keep metric definitions and windows consistent.
31
+ - Stop once the requested result is supported; do not enumerate unrelated project metadata.
32
+
33
+ 4. Report the result:
34
+
35
+ - Lead with the metric, trend, conversion, retention, or experiment finding.
36
+ - Include the date range, project or scope, filters, and metric definition needed to interpret it.
37
+ - Distinguish unique users, event totals, sessions, and percentages explicitly.
38
+ - Include Amplitude links returned by the MCP server when available.
39
+ - State when data is empty, delayed, inaccessible, or insufficient rather than inferring a value.
40
+
41
+ ## Common Analyses
42
+
43
+ - **DAU, WAU, MAU:** use active-user or event-segmentation tools with the requested interval and clarify whether the result is unique users or event totals.
44
+ - **Event segmentation:** preserve the exact event and property filters; report the aggregation and interval.
45
+ - **Funnels:** preserve ordered steps, conversion window, exclusions, and segment filters; report overall conversion and material drop-off steps.
46
+ - **Retention:** report the starting event, returning event, cohort interval, and retention horizon.
47
+ - **Saved charts and dashboards:** fetch by ID when available and summarize the returned definition and results without recreating the analysis from memory.
48
+ - **Experiments:** report status, variants, exposure window, primary metric, and result confidence exactly as returned.
49
+ - **Session replay:** narrow by time, user, or event before retrieving replay details; summarize only the interactions needed to answer the question.
50
+ - **Feature flags:** report definitions, variants, and configuration without exposing deployment API keys or other credential fields.
51
+ - **Guides, surveys, and feedback:** preserve source and date filters, distinguish processed themes from raw comments, and avoid returning unrelated customer text.
52
+ - **Agent analytics:** distinguish sessions, spans, conversations, quality metrics, cost, and latency; return transcript content only when the user explicitly requests it.
53
+ - **User activity:** use an explicit user identifier when possible and avoid exposing unrelated profile properties or event history.
54
+
55
+ ## Guardrails
56
+
57
+ - Read-only only. The plugin exposes a fixed allowlist of Amplitude search, retrieval, and query tools.
58
+ - Do not create, update, archive, delete, launch, stop, or otherwise modify Amplitude resources.
59
+ - If the user asks for a change, explain that this plugin is read-only and offer to inspect the current state or describe the change they would need to make.
60
+ - Do not weaken or bypass the plugin's tool filter, including by calling Amplitude APIs through shell commands.
61
+ - Treat event and user properties as potentially sensitive. Return only fields needed to answer the request.
62
+ - Never expose API keys, credential fields, or unrelated conversation and feedback content returned by read tools.
63
+ - Do not fabricate event names, property values, metric definitions, experiment conclusions, or missing data.
64
+ - On authorization failure, let Junior present Amplitude's OAuth flow. On permission failure, report that the connected Amplitude account cannot access the requested scope.
@@ -0,0 +1,28 @@
1
+ # Amplitude Skill Sources
2
+
3
+ Last updated: 2026-07-10
4
+
5
+ ## Source inventory
6
+
7
+ | Source | Trust tier | Confidence | Contribution | Usage constraints |
8
+ | ---------------------------------------------------------- | --------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
9
+ | `https://amplitude.com/docs/amplitude-ai/amplitude-mcp` | canonical | high | Hosted MCP endpoints, OAuth behavior, supported analytics surfaces, regional setup, and Amplitude access controls. | Treat live MCP schemas as authoritative for tool names and arguments. |
10
+ | `https://github.com/amplitude/mcp-marketplace` | canonical | high | Amplitude-authored agent workflow examples and coverage across charts, dashboards, experiments, funnels, retention, cohorts, taxonomy, and users. | Adapt workflow intent; do not copy provider-specific prompt structure wholesale. |
11
+ | `https://github.com/getsentry/junior/issues/810` | local product context | high | Required Junior use cases: active users, event segmentation, funnels, retention, saved charts, real-time activity, and user search. | The issue's REST/CLI options predate the hosted MCP recommendation. |
12
+ | `specs/plugin.md` | local canonical | high | Manifest-owned provider integration and host-managed MCP activation model. | Junior runtime contract. |
13
+ | `specs/plugin-manifest.md` | local canonical | high | Hosted MCP, environment expansion, and strict tool allowlist contract. | Junior runtime contract. |
14
+ | `packages/junior/src/chat/tools/skill/search-mcp-tools.ts` | local canonical | high | Junior-native progressive provider and tool discovery. | Use instead of Amplitude's progressive-discovery URL. |
15
+
16
+ ## Adaptation decisions
17
+
18
+ - Preserve Amplitude's analytics coverage and live schema authority.
19
+ - Replace upstream client-specific commands with Junior's `searchMcpTools` and `callMcpTool` bridge.
20
+ - Collapse many upstream workflow skills into one Slack-oriented read-only analytics skill for the initial release.
21
+ - Allow only tool names that Amplitude's official MCP reference describes as search, retrieval, or query operations.
22
+ - Include the standard server's documented search, retrieval, list, and query tools.
23
+ - Omit render, create, update, edit, sync, branch mutation, merge, delete, launch, stop, and configuration workflows.
24
+ - Keep provider schemas and tool names out of bundled prose because the MCP server is the current source of truth.
25
+
26
+ ## Retrieval stopping rationale
27
+
28
+ The official MCP documentation, Amplitude marketplace, issue requirements, and Junior plugin contracts cover authentication, runtime integration, analytics workflows, safety boundaries, and failure handling. Additional REST endpoint documentation would duplicate the live MCP schema and encourage stale tool assumptions.
@@ -0,0 +1,53 @@
1
+ # Amplitude Skill Specification
2
+
3
+ ## Classification
4
+
5
+ - Class: `integration-documentation`
6
+ - Primary execution shape: `inline-guidance`
7
+ - Simpler-shape decision: one coherent workflow is sufficient; references or scripts would duplicate live MCP schemas.
8
+ - Portability: provider-specific MCP discovery is isolated to Junior's standard bridge tools.
9
+
10
+ ## Intent
11
+
12
+ Answer product analytics questions from Amplitude while preventing the agent from invoking any provider tool outside the package's documented read-tool allowlist.
13
+
14
+ ## Trigger expectations
15
+
16
+ Should trigger for:
17
+
18
+ - DAU, WAU, MAU, active users, or new users in Amplitude
19
+ - event counts, uniques, sessions, or property segmentation
20
+ - funnel conversion and drop-off analysis
21
+ - retention analysis
22
+ - saved Amplitude chart or dashboard interpretation
23
+ - experiment, cohort, taxonomy, session-replay, feature-flag, guide, survey, feedback, agent-analytics, or user-activity inspection
24
+
25
+ Should not trigger for:
26
+
27
+ - repository code or telemetry that merely mentions Amplitude
28
+ - implementing Amplitude instrumentation or SDK setup
29
+ - creating or editing Amplitude resources
30
+ - analytics questions explicitly assigned to another provider
31
+
32
+ ## Runtime invariants
33
+
34
+ 1. Load the live Amplitude MCP catalog through Junior's provider bridge.
35
+ 2. Use exact discovered tool names and schemas.
36
+ 3. Expose only official Amplitude tools documented as search, retrieval, or query operations.
37
+ 4. Never bypass MCP filtering through direct HTTP or shell calls.
38
+ 5. Preserve explicit identifiers, filters, and time ranges.
39
+ 6. State assumptions and distinguish users, events, sessions, and percentages.
40
+
41
+ ## Validation
42
+
43
+ - `pnpm skills:check`
44
+ - `pnpm --filter @sentry/junior exec vitest run tests/component/plugins/amplitude-plugin.test.ts`
45
+ - `pnpm release:check`
46
+ - Pack `@sentry/junior-amplitude` and inspect the archive contents.
47
+ - Manual OAuth smoke test through `pnpm cli -- chat ...` when an Amplitude account is available.
48
+
49
+ ## Maintenance
50
+
51
+ - Update `SKILL.md` when supported read-only workflows or user-facing guardrails change.
52
+ - Update `SOURCES.md` when Amplitude MCP endpoints, authentication, access controls, or marketplace guidance changes.
53
+ - Update this file when trigger boundaries, runtime invariants, or validation requirements change.