Developer Tools
amplitude.com
Retrieves and searches Amplitude documentation and creates step-by-step implementation guides for analytics, experimentation, and session replay.
ENDPOINT 1
https://mcp.amplitude.com/mcp
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.amplitude-com]
url = "https://mcp.amplitude.com/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"amplitude-com": {
"type": "http",
"url": "https://mcp.amplitude.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: amplitude-com
Remote MCP URL: https://mcp.amplitude.com/mcp
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"amplitude-com": {
"url": "https://mcp.amplitude.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"amplitude-com": {
"type": "http",
"url": "https://mcp.amplitude.com/mcp",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "amplitude-com bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "amplitude-com",
"transport": "streamable-http",
"url": "https://mcp.amplitude.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://amplitude.com/docs/api/mcp
MCP server metadata
- Name
- amplitude-docs
- Version
- 1.1.0
Known tools 5
list_pagesList all available Amplitude documentation pages with their titles and slugs
Inferred read-onlysearch_docsSearch Amplitude documentation and return typed results with section-level chunks (Guide, APIReference, SDKReference, Troubleshooting)
Inferred read-onlyamplitude_implementation_plannerAssemble an ordered multi-page setup sequence with code snippets for analytics, experiment, or session replay workflows
Inferred read-onlysend_docs_mcp_feedbackReport documentation gaps, broken examples, or ambiguous parameter descriptions to the Docs content backlog
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.amplitude-docs]
url = "https://amplitude.com/docs/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"amplitude-docs": {
"type": "http",
"url": "https://amplitude.com/docs/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: amplitude-docs
Remote MCP URL: https://amplitude.com/docs/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"amplitude-docs": {
"url": "https://amplitude.com/docs/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"amplitude-docs": {
"type": "http",
"url": "https://amplitude.com/docs/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "amplitude-docs",
"transport": "streamable-http",
"url": "https://amplitude.com/docs/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.