docs: add Discord, Amplitude, Mixpanel, and Stripe connectors - #910
Merged
Conversation
…t scope - Discord Bot (new, 205 tools) with full Bot Token setup guide - Discord: 16 -> 34 tools, plus documentation of the bot scope, Bot Permissions bitfield, guild_id, disable_guild_select, and integration_type fields with a permissions calculator screenshot
Pranesh-Raghu
requested review from
AkshayParihar33,
ravibits and
saif-at-scalekit
as code owners
July 28, 2026 10:40
Contributor
WalkthroughThe PR adds Amplitude, Discord, Mixpanel, and Stripe connector catalogs, provider metadata, setup guides, quickstarts, connector pages, and generated tool indexes. Discord user and bot capabilities are expanded alongside new analytics, ingestion, compliance, experimentation, and payment tool definitions. ChangesAmplitude connector expansion
Discord connector expansion
Mixpanel connector expansion
Stripe connector expansion
Estimated code review effort: 5 (Critical) | ~120 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Deploy Preview for scalekit-starlight ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@public/data/agent-tools-index.json`:
- Line 18234: Remove the unnecessary backslash escaping before backticks in the
Discord connector descriptions, including the entries corresponding to the
affected entitlement endpoints, then regenerate the derived tools index so
rendered descriptions contain plain backticks without literal backslashes.
In `@src/components/templates/agent-connectors/_setup-discord.mdx`:
- Line 68: Update the Bot Permissions guidance in the Discord setup
documentation to remove the misleading applications link or replace it with
Discord’s actual permissions reference. Preserve the instruction to generate the
bitfield from the application’s Bot page and retain the recommended default
value.
In `@src/data/agent-connectors/discord.ts`:
- Around line 424-425: Remove “threads” from the description for
discord_list_guild_channels and update the upstream metadata source accordingly,
then regenerate the connector file so the generated description reflects that
this endpoint returns guild channel objects only.
In `@src/data/agent-connectors/tools-index.json`:
- Line 18234: Remove the unnecessary backslash escaping before backticks in the
Discord entitlement descriptions defined in discord.ts, then regenerate the
agent tools indexes so the corresponding entries contain plain backticks without
literal backslashes. Verify all affected entries, including the additional
entitlement descriptions, are updated consistently.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: e6962646-f076-47ae-8c92-4db1187bd8a5
⛔ Files ignored due to path filters (2)
src/assets/docs/agent-connectors/discord/bot-permissions.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/discordbot/bot-tab.pngis excluded by!**/*.png
📒 Files selected for processing (10)
public/data/agent-tools-index.jsonsrc/components/templates/agent-connectors/_setup-discord.mdxsrc/components/templates/agent-connectors/_setup-discordbot.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/discord.mdxsrc/content/docs/agentkit/connectors/discordbot.mdxsrc/data/agent-connectors/catalog.tssrc/data/agent-connectors/discord.tssrc/data/agent-connectors/discordbot.tssrc/data/agent-connectors/tools-index.json
…nectors - Amplitude Analytics — 58 tools, HTTP Basic Auth - Amplitude Experiment Management — 57 tools, Bearer token Both setup guides cover US and EU data residency regions.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/templates/agent-connectors/_setup-amplitudeanalytics.mdx`:
- Around line 57-104: The Amplitude credential examples need explicit
server-side-only security warnings. In
src/components/templates/agent-connectors/_setup-amplitudeanalytics.mdx lines
57-104, add a warning before each TypeScript and Python sample covering API Key
and Secret Key exposure, explaining that browser-side exposure lets attackers
reuse them and that the code must run server-side; in
src/components/templates/agent-connectors/_setup-amplitudeexperimentmanagement.mdx
lines 55-98, add equivalent warnings before each language sample for the
Management API key.
- Around line 57-79: The Amplitude connector snippets use upsertConnectedAccount
without initializing the client. Update both
src/components/templates/agent-connectors/_setup-amplitudeanalytics.mdx (lines
57-79) and
src/components/templates/agent-connectors/_setup-amplitudeexperimentmanagement.mdx
(lines 55-75) to include the standard Node.js scalekit and Python
scalekit_client setup, or explicitly label each example as a continuation
snippet.
In `@src/content/docs/agentkit/connectors/amplitudeexperimentmanagement.mdx`:
- Line 6: Shorten the connector’s upstream metadata label from “Amplitude
Experiment Management” to 30 characters or fewer, then re-sync/regenerate the
page so the generated sidebar label reflects the upstream change. Do not
manually patch the generated MDX output.
In `@src/data/agent-connectors/amplitudeexperimentmanagement.ts`:
- Around line 1046-1055: Update the upstream catalog metadata for
amplitudeexperimentmanagement_remove_flag_variant_user so its description
references amplitudeexperimentmanagement_get_flag_variant_users as the available
way to obtain the variant inclusion list, removing the claim that this endpoint
is outside the tool set. Then re-sync the generated connector file while
preserving the tool’s actual behavior and parameter semantics.
In `@src/data/agent-connectors/catalog.ts`:
- Around line 1643-1651: Add a discordbot entry to the connector catalog
alongside the provider metadata, using the authoritative Discord bot icon URL,
bot-specific authentication type, and appropriate category so consumers do not
fall back to defaults.
In `@src/data/agent-connectors/tools-index.json`:
- Around line 3333-3336: Remove the unnecessary backslashes before backticks in
the template-literal descriptions within amplitudeexperimentmanagement.ts,
including the holdout-group and update-flag-variant entries, so generated text
contains plain backticks. Regenerate tools-index.json and the corresponding
public agent-tools index from the source rather than editing generated JSON
directly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: cabd2a4e-6152-48bb-9e07-8b63640beb67
⛔ Files ignored due to path filters (3)
src/assets/docs/agent-connectors/amplitudeanalytics/api-keys.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/amplitudeanalytics/secret-keys.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/amplitudeexperimentmanagement/management-api-keys.pngis excluded by!**/*.png
📒 Files selected for processing (10)
public/data/agent-tools-index.jsonsrc/components/templates/agent-connectors/_setup-amplitudeanalytics.mdxsrc/components/templates/agent-connectors/_setup-amplitudeexperimentmanagement.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/amplitudeanalytics.mdxsrc/content/docs/agentkit/connectors/amplitudeexperimentmanagement.mdxsrc/data/agent-connectors/amplitudeanalytics.tssrc/data/agent-connectors/amplitudeexperimentmanagement.tssrc/data/agent-connectors/catalog.tssrc/data/agent-connectors/tools-index.json
- Mixpanel Analytics — 37 tools, Service Account (US/EU/India regions) - Mixpanel Ingestion — 25 tools, Service Account (US/EU/India regions) - Mixpanel Compliance — 5 tools, GDPR/CCPA token (US/EU/India regions) - Stripe — 110 tools (excludes stripe_zz_test_echo_probe_dahlia, a test-only tool flagged by CodeRabbit that forwards Stripe Bearer tokens to an external echo service)
Pranesh-Raghu
changed the title
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/templates/agent-connectors/_setup-mixpanelanalytics.mdx`:
- Around line 52-99: Initialize the SDK clients before the connection examples
so the snippets are runnable: add the appropriate Node.js import and client
setup, and the corresponding Python import and client setup, before the calls
using scalekit or scalekit_client. Apply this to
src/components/templates/agent-connectors/_setup-mixpanelanalytics.mdx lines
52-99, src/components/templates/agent-connectors/_setup-mixpanelcompliance.mdx
lines 55-98, and
src/components/templates/agent-connectors/_setup-mixpanelingestion.mdx lines
52-99.
In `@src/components/templates/agent-connectors/_setup-mixpanelcompliance.mdx`:
- Around line 24-29: Update the Mixpanel compliance setup instructions near the
GDPR token step to explain how to locate the Mixpanel project_token and
distinguish it from the GDPR OAuth token. State that the project_token must be
provided in the input for every compliance tool, and replace or clarify the
unexplained YOUR_PROJECT_TOKEN quickstart placeholder accordingly.
In `@src/data/agent-connectors/tools-index.json`:
- Around line 40631-40968: Fix the source descriptions or generator responsible
for connector metadata truncation, ensuring complete Mixpanel and Stripe
descriptions are preserved rather than cut off mid-word. Regenerate
tools-index.json from the corrected source and verify the affected entries,
including mixpanelanalytics_* and mixpanelingestion_* connectors, contain their
full descriptions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: d11ff2d8-65cc-48df-bea2-57e6dc903add
⛔ Files ignored due to path filters (3)
src/assets/docs/agent-connectors/mixpanelanalytics/add-service-account.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/mixpanelcompliance/gdpr-token.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/mixpanelingestion/add-service-account.pngis excluded by!**/*.png
📒 Files selected for processing (15)
public/data/agent-tools-index.jsonsrc/components/templates/agent-connectors/_setup-mixpanelanalytics.mdxsrc/components/templates/agent-connectors/_setup-mixpanelcompliance.mdxsrc/components/templates/agent-connectors/_setup-mixpanelingestion.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/mixpanelanalytics.mdxsrc/content/docs/agentkit/connectors/mixpanelcompliance.mdxsrc/content/docs/agentkit/connectors/mixpanelingestion.mdxsrc/content/docs/agentkit/connectors/stripe.mdxsrc/data/agent-connectors/catalog.tssrc/data/agent-connectors/mixpanelanalytics.tssrc/data/agent-connectors/mixpanelcompliance.tssrc/data/agent-connectors/mixpanelingestion.tssrc/data/agent-connectors/stripe.tssrc/data/agent-connectors/tools-index.json
saif-at-scalekit
approved these changes
Jul 28, 2026
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
2 participants
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.
Summary
Split out of PR #891 into its own PR for a cleaner review. Includes:
Discord
discord, with a full Bot Token setup guidebotscope, Bot Permissions bitfield, and related fieldsAmplitude
Mixpanel
Stripe
stripe_zz_test_echo_probe_dahlia, a test-only tool flagged by CodeRabbit that forwards Stripe Bearer tokens to an external echo serviceTest plan
pnpm format:checkpassespnpm buildcompletes successfullyhttps://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/agentkit/connectors/mixpanelanalytics/Summary by CodeRabbit
New Features
Documentation