By Ira Bodnar, Ryze AI · Updated · Test record: nothing was run
Quick answer
The main way to connect Claude Code to Amplitude is the Ryze AI connector. Store the Amplitude project keys and data residency on the Amplitude card in Ryze AI, then run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp in a shell. Open Claude Code, type /mcp, pick ryze, finish the browser sign-in and begin a fresh session.
- Copy the API key and secret key from your Amplitude project settings
- Put both keys and the data residency on the Amplitude card in Ryze AI
- Run the claude mcp add command in a shell, then authenticate ryze through /mcp
- Pick the workspace on the Ryze AI consent page and ask a first question
Claude Code to Amplitude at a glance
| Question | Answer |
|---|---|
| Main way to connect | The hosted Ryze AI connector, registered in Claude Code with a single claude mcp add command |
| Server address | https://connector.get-ryze.ai/mcp |
| How you sign in | Browser OAuth via /mcp or claude mcp login ryze. For scripts, a Ryze AI API key passed with --header |
| What Amplitude must supply | API key, secret key and data residency (us or eu), kept in Ryze AI rather than in your shell or repo |
| Amplitude tools | 1: amplitude__read, a read-only Dashboard REST API tool scoped to one project |
| Can it alter Amplitude | No. The sole Amplitude tool issues GET requests, so charts, cohorts and events stay untouched |
| Projects per connection | One, chosen by the key pair |
| Claude Code access | Pro, Max, Ultra, Team, Enterprise or Console. The free claude.ai plan lacks Claude Code |
| Ryze AI cost | Paid Ads at $89 per month after a 7-day free trial. The connector itself is free; the Amplitude tool needs a plan or trial |
| Amplitude's own server | Hosted at https://mcp.amplitude.com/mcp. Amplitude lists MCP as not included on Free and Growth, an add-on on Plus and included on Enterprise |
| Last checked | Amplitude pages and the connector address on November 20, 2026. No Amplitude call and no Claude Code step was run |
Before you start
- Claude Code access. Per Anthropic, you need a Pro, Max, Ultra, Team, Enterprise or Console account, and the free claude.ai plan is excluded. Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry also work as providers. The MCP page lists no additional plan for remote servers.
- Amplitude project keys. Open Settings, Projects, your project, General to find the API key and secret key. Ryze AI also asks where the project lives, us or eu. Whichever pair you enter fixes the project. Amplitude's Dashboard REST API reads them as a Basic authentication username and password.
- A Ryze AI workspace with a plan or trial. Paid Ads costs $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day trial, Agency $279 per month. Adding the connector is free; without a plan or trial the Amplitude tool stays unavailable.
How to connect Claude Code to Amplitude
Three steps happen in Amplitude and Ryze AI, three in Claude Code. The connector URL is the same for every user.
Get the keys from your Amplitude project
In Amplitude go to Settings, Projects, choose the project and open General. Copy the API key and the secret key. Do not paste them into chats, commits or CLAUDE.md, since together they let anyone read the project's chart data.
Store the keys on the Amplitude card in Ryze AI
Sign in to Ryze AI (or create an account), go to Integrations and click Connect on Amplitude. Enter the API key, the Secret key and the Data residency, then click Continue. Pick eu for an EU-hosted project; the wrong region makes the connection fail.
Register the connector with claude mcp add
Run this in a normal shell, outside any claude session: claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. By default the entry has local scope. Append --scope user to load it in every project. claude mcp list reports Needs authentication until you sign in.
Authenticate ryze
Start Claude Code, type /mcp, highlight ryze and choose Authenticate. A shell alternative is claude mcp login ryze, and adding --no-browser prints the URL for you to open elsewhere, handy on a remote machine.
Approve the workspace
The Ryze AI page asks you to sign in if needed. Select the workspace holding the Amplitude connection and click Allow connection. Afterwards claude mcp get ryze shows the status.
Open a new session and ask something
Claude Code defers MCP tools by default and loads them on demand through tool search. Try: List the events my Amplitude project tracks, then segment the busiest one by day for the last 30 days with uniques.
The Ryze AI Amplitude guide covers the Amplitude side of the connection, and the Claude Code MCP docs cover the client commands.
Sources: Claude Code MCP documentation, Claude Code MCP quickstart, Ryze AI Amplitude guide. Checked November 20, 2026.
OAuth, API key and claude.ai connectors
Claude Code accepts the Ryze AI connector three ways. Pick the one that matches where the session runs.
CLI with browser OAuth
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope userBest for a laptop. Local scope, the default, ties the entry to the current project; --scope user makes it global; --scope project writes .mcp.json so teammates share it, and each of them must approve it once in an interactive session. A scope cannot be edited in place, so remove the entry and add it again to move it.
CLI with a Ryze AI API key
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --header "Authorization: Bearer rk_live_..."Create the key in Ryze AI under Workspace Settings, Profile, API keys, Create key; it is displayed once. It differs from your Amplitude key pair. Ryze AI's help center says it works on /mcp and not on /sse. When Claude Code sees the header rejected, it marks the server failed and never retries with OAuth, so swap in a valid key.
A connector added in claude.ai
Add Ryze AI at claude.ai/customize/connectors, complete its sign-in, then log in to Claude Code with that same claude.ai subscription and open /mcp, where the connector carries a claude.ai marker. On Team and Enterprise only admins can add servers in claude.ai. Logins through ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, apiKeyHelper or a third-party provider skip these connectors.
Scripts and limits
Non-interactive runs (claude -p, Agent SDK) have no way to complete OAuth, so authenticate beforehand with /mcp or claude mcp login ryze, or choose the API key route. Results over 10,000 tokens trigger a warning and the default ceiling is 25,000 tokens, adjustable with MAX_MCP_OUTPUT_TOKENS. That ceiling can bite on a segmentation grouped by many values. Any HTTP tool call silent for five minutes is cut off.
Claude Code and MCP: the facts in one table
| Topic | What Anthropic's Claude Code docs say |
|---|---|
| Config file locations | ~/.claude.json holds local and user entries; .mcp.json in the project root holds project entries. ~/.claude/mcp.json is ignored |
| Transport options | HTTP is Anthropic's recommendation for remote servers like this one. SSE is deprecated and stdio serves local processes |
| Authentication | OAuth 2.0. A 401 or 403 from the server flags it as needing authentication until you choose Authenticate in /mcp, after which tokens renew automatically |
| Fixed headers | Pass --header (or -H), or write a headers object into the entry |
| Permission rules | An MCP tool is addressed as mcp__<server>__<tool>, and each rule can allow, ask or deny. Since 2.1.283, interactive sessions start in auto mode where available |
| Managing servers | claude mcp list, get and remove in a shell; /mcp inside a session |
| Directory listing for Ryze AI | Anthropic Directory, Community label, added August 2026. Community means screened without a deep review |
Sources: Claude Code MCP, permission modes, setup, changelog, Claude custom connectors, Ryze AI in the Anthropic Directory. Checked November 20, 2026.
Claude web, ChatGPT and Cursor
The same URL works in other MCP clients. The Amplitude keys are saved once in Ryze AI, so nothing changes on the Amplitude side.
Claude on the web and Desktop
Go to Customize, Connectors, click + Add, choose Add custom connector, call it Ryze AI and paste https://connector.get-ryze.ai/mcp. The free plan allows one custom connector, and on Team and Enterprise an Owner registers it first. The Claude and Amplitude guide on this site walks through it.
ChatGPT
OpenAI reserves full custom MCP servers for ChatGPT Business and Enterprise/Edu on the web, while Pro can attach custom servers with read and fetch permissions only. Add the URL as a custom MCP server using OAuth.
Cursor
Put the entry in ~/.cursor/mcp.json for every project or .cursor/mcp.json for one. Cursor signs in with OAuth plus PKCE and by default asks before running MCP tools.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Amplitude keys and access
Claude Code never touches Amplitude directly. It goes through the key pair stored in Ryze AI, and three settings bound what it sees.
- Project
- Whichever project owns the keys. A Ryze AI connection holds exactly one, and Amplitude is not among the platforms Ryze AI lists as supporting several accounts. To switch, press View on the Amplitude card, disconnect with the trash icon and reconnect with new keys, or hold the second project in a different workspace.
- Keys
- The API key and secret key you submitted. Reads are limited to what that pair can fetch from the Dashboard REST API, so regenerating the pair in Amplitude locks Claude Code out.
- Claude Code rules
- Allow, ask and deny rules decide whether an MCP tool call pauses for you. With a GET-only Amplitude tool, no choice of rule can modify anything in Amplitude.
What the Amplitude key pair covers
The Dashboard REST API offers no OAuth scopes. It relies on HTTP Basic authentication with the project key pair, and the rows below are what the Ryze AI connection depends on.
| Item | What it covers | Source |
|---|---|---|
| API key | Acts as the Basic authentication username and identifies the project that answers | Amplitude Dashboard REST API docs |
| Secret key | Acts as the Basic authentication password, typed only into Ryze AI | Amplitude Dashboard REST API docs |
| Data residency | Picks the regional host. The docs name https://analytics.eu.amplitude.com as the EU base URL | Amplitude Dashboard REST API docs |
| Location of the keys | Settings, Projects, the project, General | Ryze AI Amplitude guide |
Outside the Ryze AI Amplitude tool: building or editing charts, cohorts and events, since it only sends GET requests. Amplitude's own MCP server works differently. It uses OAuth, and its write calls need the Use MCP (write) RBAC action, a requirement that never applies to the Ryze AI connection.
Treat the secret key like a password. Amplitude documents it as the Basic authentication password, so anyone who holds both keys can read that project's chart data through the API.
Sources: Amplitude Dashboard REST API, Amplitude MCP server docs, Ryze AI Amplitude guide. Checked November 20, 2026.
Removing access
Cut access by pressing View on the Amplitude card in Ryze AI and disconnecting with the trash icon, or by regenerating the keys in Amplitude. Inside Claude Code run claude mcp logout ryze, then claude mcp remove ryze, because remove by itself drops the stored tokens without revoking them at the sign-in server. /mcp can also switch the server off while keeping its entry.
What Claude Code can do in Amplitude
Ryze AI exposes a single Amplitude tool through the connector, and it can only read. Its name comes from the Ryze AI app source in the facts file, not from a live tool list.
| Tool | Type | What it does |
|---|---|---|
| amplitude__read | Read | Runs a read-only Amplitude Dashboard REST API GET request for the connected project: event list, event segmentation, funnels, retention, active and new users, sessions, realtime, user activity and search, cohorts, annotations and saved chart results. |
Claude Code applies its own permission rules, and one aimed at this tool would be written mcp__ryze__amplitude__read, with your server name in the middle. The tool only reads, so Amplitude is unchanged whatever the rule says. Claude.ai connector settings (Customize, Connectors, Ryze AI, Tool permissions) set approvals per tool. The Ryze AI chat picker for Tool approvals begins on Skip all approvals, and scheduled tasks in Ryze AI run with no approval step.
Limits in numbers
Each figure belongs to Amplitude or Claude Code and is counted the way that vendor counts it. The one limit Ryze AI adds is a single Amplitude project per connection.
| Limit | What the docs say |
|---|---|
| Concurrency (Dashboard REST API) | 5 simultaneous requests per API key; more earns an HTTP 429 |
| Hourly cost (Dashboard REST API) | 108,000 cost per hour across every endpoint |
| User activity and search | 360 queries per hour combined, with at most 10 concurrent requests across both |
| Claude Code MCP output | Warning at 10,000 tokens, default cap 25,000 |
| Claude Code HTTP calls | Abandoned after five minutes without a response or progress |
| Ryze AI connection | One Amplitude project |
Sources: Claude Code permissions, Amplitude Dashboard REST API, Claude Code MCP output limits. Checked November 20, 2026.
First 3 prompts to run
Answers depend on your project, so no sample figures appear here. Only the shape of each reply is described. Spell out the event names, since the connector cannot guess them.
1. Daily trend for one event
For the event I name, show uniques per day across the past 30 days and split by a single property of my choosing.
Tools used: amplitude__read
What comes back: A segmentation result over the chosen dates, split the way you asked. Amplitude itself is not modified.
2. Locate the leakiest funnel step
Take these three events as an ordered funnel and say which transition loses the largest share of users.
Tools used: amplitude__read
What comes back: Step counts and conversion as Amplitude reports them, plus Claude Code's pick of the weakest transition.
3. Weekly retention of a signup cohort
Pull weekly retention for users who fired the starting event I name, measuring return with the event I name.
Tools used: amplitude__read
What comes back: A retention table for the dates you set, condensed into a few plain sentences in the terminal.
When you do not know the event names, first ask Claude Code to list them. Wide date ranges and many groups use more of Amplitude's hourly cost cap, so begin with a narrow request.
10 jobs to hand to Claude Code
Nine requests to give Claude Code, each paired with the Ryze AI tool that answers it. None was run for this guide.
| Job | Request in the terminal | Tool | Covered by the default connection |
|---|---|---|---|
| Tracked events | Which events does this project track? | amplitude__read | Yes |
| Single-event trend | Plot uniques of the event I name per day over a date range. | amplitude__read | Yes |
| Property breakdown | Split that event by two properties and list the biggest groups. | amplitude__read | Yes |
| Funnel drop | Run this funnel and highlight the steepest drop. | amplitude__read | Yes |
| New-user retention | Show weekly retention for newly acquired users. | amplitude__read | Yes |
| Audience size | Report active and new users over the past 8 weeks. | amplitude__read | Yes |
| One user's history | Find a single user and read their activity. | amplitude__read | Yes, inside the 360-per-hour allowance |
| Saved chart or cohort | Fetch the saved chart with this ID, or list cohorts and annotations. | amplitude__read | Yes |
| Build or rename something | Create a chart or cohort, or rename an event. | none | No. The tool is GET only; Amplitude's own server documents tools for it |
4 ways to connect Claude Code to Amplitude
Four routes can put Amplitude in reach of Claude Code. This guide treats the Ryze AI connector as the main way, because the Amplitude keys stay inside Ryze AI, Claude Code needs one URL plus a browser sign-in, and the tool reads only. Amplitude's server and API rows come from its documentation as of November 20, 2026. None of the four was run for this guide.
| Way | Hosting | Adding it to Claude Code | Reach inside Amplitude | Cost |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Ryze AI hosts it, with one URL for all users | claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then Authenticate in /mcp. A Ryze AI API key via --header or a claude.ai connector works too | 1 read tool on one project covering segmentation, funnels, retention, users, sessions, cohorts, annotations and saved charts | Paid Ads is $89 per month with a 7-day free trial |
| Amplitude MCP server, US | Amplitude hosts it at https://mcp.amplitude.com/mcp | The command in Amplitude's docs is claude mcp add --transport http --scope user Amplitude https://mcp.amplitude.com/mcp, followed by an Amplitude login | Whatever your Amplitude permissions allow. Reading needs Use MCP (read) and writing needs Use MCP (write). Claude's listing for the Amplitude connector shows 28 tools | MCP is not included on Free and Growth, an add-on on Plus and included on Enterprise |
| Amplitude MCP server, EU | Amplitude hosts it at https://mcp.eu.amplitude.com/mcp | Amplitude lists this URL for EU data residency. Claude Code should accept it through the same claude mcp add form with a different address. Untested here | The same tool set over EU-hosted data | Same as the US server |
| Dashboard REST API from your own scripts | Amplitude's HTTP API, called by code you write | No MCP involved. A script, or a Bash call from Claude Code, makes the Basic authentication request itself | Chart-style results for one project, capped at 5 concurrent requests per API key | Priced by Amplitude, see its docs |
Options that do not fit Claude Code
- The Amplitude connector in Claude's directory. Its listing mentions Claude, carries the Anthropic verified label and dates from November 2025. Anthropic says claude.ai connectors also appear in Claude Code under a claude.ai subscription login, yet Amplitude's own documentation gives the claude mcp add route for Claude Code.
- Enterprise-managed sign-in. Amplitude describes it for Claude through an identity provider and does not mention Claude Code.
Which one to pick
Ryze AI is the best way to connect Claude Code to Amplitude for read-only product analytics questions behind one browser sign-in, with a caveat: Amplitude's own connector lists 28 tools covering dashboards, experiments and taxonomy changes, whereas Ryze AI offers a single read tool. Choose Amplitude's server if Claude Code should build charts or edit your tracking plan and your plan includes MCP. Choose the Ryze AI connector if Claude Code should merely read one project and you already share that URL across other Ryze AI platforms. Both can coexist under distinct names such as ryze and Amplitude.
Sources: Amplitude MCP server docs, Amplitude connector listing on claude.com, Amplitude Dashboard REST API, Claude Code MCP, Ryze AI Amplitude guide. Checked November 20, 2026.
Amplitude, Claude Code and MCP: dates that matter
| Date | What happened |
|---|---|
| November 25, 2024 | Anthropic open-sourced the Model Context Protocol. |
| June 18, 2025 | Claude Code 1.0.27 introduced streamable HTTP servers and OAuth for remote servers, which is the transport and login used here. |
| November 2025 | The Amplitude connector entered Claude's directory per its listing, which shows the Anthropic verified label. |
| February 18, 2026 | Claude Code 2.1.46 started loading connectors from claude.ai. |
| June 22, 2026 | claude mcp login and claude mcp logout arrived in Claude Code 2.1.186. |
| August 2026 | Ryze AI's own Anthropic Directory listing shows this as the month it was added. |
| September 28, 2026 | With 2.1.284, interactive Claude Code sessions begin in auto mode when no permission mode is set. |
| November 13, 2026 | Claude Code 2.1.325 was the latest changelog entry on the day of checking. |
| November 18, 2026 | Amplitude's MCP documentation page shows this as its last update. |
Sources: Anthropic MCP announcement, Claude Code changelog, Amplitude MCP server docs, Amplitude connector listing on claude.com. Checked November 20, 2026.
How this guide was tested
A single check hit the live Ryze AI connector address on November 20, 2026. It needs no Amplitude project. The result is below.
| What was run | What came back |
|---|---|
| A POST to the connector address with no credentials | HTTP 401 carrying a WWW-Authenticate header that points to protected-resource metadata and reports invalid_token. Claude Code's docs say a server replying like this stays flagged as needing authentication until you sign in. |
Not run: any request to Amplitude. No project was linked, so no Amplitude tool fired and no Amplitude output is shown. The Claude Code steps were not run either, meaning nothing was added with claude mcp add and nobody signed in through /mcp. Claude Code details follow Anthropic's documentation read on November 14, 2026, Amplitude figures follow its pages read on November 20, 2026, and Ryze AI steps follow the Ryze AI help center. Since no Amplitude call was made, there is no table of tested calls, and the errors section describes documented behavior instead of copied output.
Errors and fixes
- ryze appears as Needs authentication
- Either no login is stored yet or it was wiped. Choose Authenticate on ryze inside /mcp, or run claude mcp login ryze. Any 401 or 403 from the server produces this label.
- The server fails to connect when an API key is set
- A rejected Authorization header marks the server failed, and Claude Code does not switch to OAuth. Confirm the value is a live rk_live_ Ryze AI key and the URL ends in /mcp, or delete the entry and add it again with no --header.
- claude -p or the Agent SDK cannot log in
- Neither can run OAuth. Sign in beforehand in an interactive shell with claude mcp login ryze, or use the API key route.
- Entries from .mcp.json stay unloaded
- Servers at project scope wait for your approval in an interactive session. Say yes when prompted.
- No Amplitude tool shows up
- If you registered the connector before linking Amplitude, run claude mcp remove ryze, add it again and open a new session. Tool search loads tools on demand, so they may be missing from an up-front list.
- Claude reports a subscription requirement
- The Amplitude tool needs an active Ryze AI plan or free trial. Without either, the connector can only list workspaces and connect platforms.
- Requests are throttled
- Beyond 5 concurrent requests per key or 108,000 cost per hour, Amplitude replies HTTP 429. Wait, narrow the range, drop groups or ask for one chart at a time.
- User lookups halt
- User activity and user search draw on the same 360 queries per hour. Wait out the hour or reduce lookups.
- An EU project will not connect
- Look at Data residency on the Amplitude card and choose eu, not us.
- Data from the wrong project
- The key pair picks the project. Press View on the Amplitude card in Ryze AI, disconnect via the trash icon and reconnect with the other pair.
- The one-time connection link gets refused
- A link requested from the Ryze AI agent works once within 24 hours and is refused while Amplitude is already linked in that workspace. Change projects in the Ryze AI app.
- A reply is huge
- Past 10,000 tokens Claude Code warns, and the default ceiling is 25,000. Request fewer groups or a shorter range, or raise MAX_MCP_OUTPUT_TOKENS.
Terms on this page
- MCP
- Model Context Protocol, the open standard Anthropic released in November 2024 so assistants such as Claude Code can call outside tools.
- API key and secret key
- Two strings Amplitude issues per project. The Dashboard REST API treats them as the Basic authentication username and password.
- Data residency
- The region, us or eu, where an Amplitude project keeps its data. It decides which Amplitude host replies.
- Event segmentation
- A read that counts one event across time, using metrics like uniques or totals and optionally grouped by properties.
- Cohort
- A stored group of users defined by behavior. Ryze AI can list cohorts but does not create them.
- Server scope
- Where Claude Code keeps a server entry: local, user or project.
- Dashboard REST API
- Amplitude's HTTP interface for chart-style results, which the Ryze AI tool calls with GET.
Sources: Anthropic on MCP, Amplitude Dashboard REST API, Amplitude MCP server docs. Checked November 20, 2026.
Frequently asked questions
How do I connect Claude Code to Amplitude?
Enter your Amplitude API key, secret key and data residency on the Amplitude card in Ryze AI, then run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. In Claude Code open /mcp, choose ryze, sign in on the Ryze AI page, pick the workspace and click Allow connection. claude mcp get ryze confirms the result.
Does Amplitude offer an MCP server for Claude Code?
Yes. Amplitude hosts one at https://mcp.amplitude.com/mcp (EU: https://mcp.eu.amplitude.com/mcp), and its docs show claude mcp add --transport http --scope user Amplitude https://mcp.amplitude.com/mcp for Claude Code. The Ryze AI connector at https://connector.get-ryze.ai/mcp is a different route with 1 read-only Amplitude tool.
Which URL do I give Claude Code for Amplitude?
Amplitude's own server uses https://mcp.amplitude.com/mcp, or https://mcp.eu.amplitude.com/mcp for EU data. The Ryze AI connector uses https://connector.get-ryze.ai/mcp for everyone.
Can both servers run side by side in Claude Code?
Yes, under separate names such as ryze and Amplitude. Their addresses differ, Claude Code's MCP page states no cap on servers, and every tool name includes its server name so you can see which one answered.
What Claude plan does Claude Code need?
Anthropic requires a Pro, Max, Ultra, Team, Enterprise or Console account, and the free claude.ai plan has no Claude Code. Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry are alternative providers.
Is OAuth or an API key better here?
On a personal machine OAuth through /mcp is simpler. A Ryze AI API key (Workspace Settings, Profile, API keys) fits scripts, since claude -p and Agent SDK runs cannot perform OAuth. It works on /mcp only and is distinct from your Amplitude keys.
Where are the Amplitude API key and secret key?
Under Settings, Projects, your project, General in Amplitude. Whichever pair you give Ryze AI selects the connected project.
Will Claude Code modify my Amplitude project?
Through Ryze AI, no. The one Amplitude tool sends GET requests and cannot create or edit charts, cohorts or events. Amplitude's own server documents write calls that need the Use MCP (write) RBAC action.
Does Amplitude's server require a paid Amplitude plan?
Per Amplitude's docs, MCP is not included on Free and Growth, is an add-on on Plus and is included on Enterprise. The Ryze AI connector relies on the Dashboard REST API key pair and instead needs an active Ryze AI plan or trial.
What limits does Amplitude set on queries?
The Dashboard REST API allows 5 concurrent requests per API key and up to 108,000 cost per hour, answering HTTP 429 beyond that. User activity and search are further capped at 360 queries per hour.
Can I link several Amplitude projects?
A connection holds one. To change projects, disconnect and reconnect with the other keys, or give the second project its own Ryze AI workspace.
What does the scope flag on claude mcp add do?
Local scope, the default, limits the entry to the current project. User scope applies it everywhere. Project scope writes .mcp.json for the team, and each person approves it interactively. To change scope, remove the entry and register it again.
Why is the Amplitude tool missing in Claude Code?
Open a new session and check /mcp. If you added the connector before linking Amplitude, remove and re-add it. A missing claude.ai connector means the active login is not a claude.ai subscription account.
What does it cost?
Adding the connector is free, but the Amplitude tool needs an active Ryze AI plan or free trial: Paid Ads $89 per month with a 7-day trial, SEO Starter $129 per month with a 3-day trial, Agency $279 per month. Annual billing takes 30% off the first year.
How do I disconnect it?
Disconnect Amplitude on its Ryze AI card or regenerate the keys in Amplitude, then run claude mcp logout ryze and claude mcp remove ryze.