Manufact

LeaderboardBack to leaderboard

amplitude-docs

amplitude.com/docs/api/mcp

View checks

Protocol: MCP 2025-11-25
Server version: 1.1.0
Supports: Tools

Overall score

How is this score calculated?

Last reviewed at Nov 7, 2026, 19:32:34 UTC

Server metadata

Warnings30/100

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

amplitude-docs

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.1.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools.

10/10Source

Discoverability

17/100

Client listings and public setup information.

mcp.json or server-card.json

Either mcp.json or an MCP Server Card declaring this endpoint passes.

No matching mcp.json manifest or MCP Server Card was found at the checked URLs.

Not foundSource

Setup instructions at MCP URL

The public page returned HTTP 405.

Not foundSource

ChatGPT

No ChatGPT listing has been confirmed yet.

UnverifiedHow to get listed

ClaudeVerified

Verified by Anthropic · full credit.

ListedSource How to get listed

CursorGrok BotGrok

No Cursor marketplace listing has been confirmed yet.

UnverifiedHow to get listed

Muse

No Muse listing has been confirmed yet.

UnverifiedHow to get listed

3 unverified checks. Unverified checks earn no points until confirmed.

Protocol

Pass100/100

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 3266ms

Source

Tools list returns results

5 tool(s) returned

Source

Resources list responds

0 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues78/100

Tool definitions, annotations, and client compatibility.

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

All tools have descriptions

All tools have non-empty descriptions

Claude tools declare applicable behavior hints

5 Claude behavior annotation issue(s) found

How to fix: For Claude directory submission, declare the applicable annotations.readOnlyHint or annotations.destructiveHint value as a boolean on every tool.

errorClaude.ai

Source

All tools have OpenAI behavior hints

15 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

All tools have a display title

5 tool(s) missing a display title: get_page, list_pages, search_docs, amplitude_implementation_planner, send_docs_mcp_feedback

How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.

errorClaude.ai

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Tool names use valid characters

All tool names use valid characters

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Not applicableOptional

App resources, metadata, and rendering requirements.

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

View resource metadata complete

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

Tool invocation metadata present

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

Views do not request nested iframe domains

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

Tool documentation quality

54/100

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

get_pageTitles 40Descriptions 76Inputs 75Annotations 0Outputs 051/100

get_page

Title40/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description76/100

Retrieve the full markdown content of an Amplitude documentation page

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

slug

Page slug, e.g. "sdks/browser/latest/getting-started"

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

rationale

Brief explanation of why you are calling this tool

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_page",
  "description": "Retrieve the full markdown content of an Amplitude documentation page",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "maxLength": 512,
        "minLength": 1,
        "description": "Page slug, e.g. \"sdks/browser/latest/getting-started\""
      },
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      }
    }
  }
}

list_pagesTitles 62Descriptions 78Inputs 75Annotations 0Outputs 057/100

list_pages

Title62/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

List all available Amplitude documentation pages with their titles and slugs

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

rationale

Brief explanation of why you are calling this tool

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_pages",
  "description": "List all available Amplitude documentation pages with their titles and slugs",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      }
    }
  }
}

search_docsTitles 65Descriptions 78Inputs 75Annotations 0Outputs 058/100

search_docs

Title65/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

Search Amplitude documentation and return typed results with section-level chunks (Guide, APIReference, SDKReference, Troubleshooting)

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

query

Keyword to search for across all documentation pages

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

rationale

Brief explanation of why you are calling this tool

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_docs",
  "description": "Search Amplitude documentation and return typed results with section-level chunks (Guide, APIReference, SDKReference, Troubleshooting)",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "Keyword to search for across all documentation pages"
      },
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      }
    }
  }
}

amplitude_implementation_plannerTitles 44Descriptions 73Inputs 75Annotations 0Outputs 051/100

amplitude_implementation_planner

Title44/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description73/100

Assemble an ordered multi-page setup sequence with code snippets for analytics, experiment, or session replay workflows

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

workflow

End-to-end integration workflow: analytics, experiment, or session_replay

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

rationale

Brief explanation of why you are calling this tool

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "amplitude_implementation_planner",
  "description": "Assemble an ordered multi-page setup sequence with code snippets for analytics, experiment, or session replay workflows",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "workflow"
    ],
    "properties": {
      "workflow": {
        "enum": [
          "analytics",
          "experiment",
          "session_replay"
        ],
        "type": "string",
        "description": "End-to-end integration workflow: analytics, experiment, or session_replay"
      },
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      }
    }
  }
}

send_docs_mcp_feedbackTitles 47Descriptions 78Inputs 75Annotations 0Outputs 053/100

send_docs_mcp_feedback

Title47/100

Not provided

Expand internal abbreviations and remove technical prefixes from the display title.

Description78/100

Report documentation gaps, broken examples, or ambiguous parameter descriptions to the Docs content backlog

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "send_docs_mcp_feedback",
  "description": "Report documentation gaps, broken examples, or ambiguous parameter descriptions to the Docs content backlog",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "category",
      "message"
    ],
    "properties": {
      "message": {
        "type": "string",
        "maxLength": 2000,
        "minLength": 1,
        "description": "Description of the documentation gap or issue"
      },
      "category": {
        "enum": [
          "missing_endpoint",
          "broken_example",
          "ambiguous_parameter",
          "missing_content",
          "other"
        ],
        "type": "string",
        "description": "Feedback category: missing_endpoint, broken_example, ambiguous_parameter, missing_content, or other"
      },
      "page_slug": {
        "type": "string",
        "maxLength": 512,
        "description": "Optional page slug where the issue was found"
      },
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      },
      "section_heading": {
        "type": "string",
        "maxLength": 200,
        "description": "Optional section heading where the issue was found"
      }
    }
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Search docsSearch Amplitude documentation and return typed results with section-level chunks (Guide, APIReference, SDKReference, Troubleshooting)
02Get pageRetrieve the full markdown content of an Amplitude documentation page
03List pagesList all available Amplitude documentation pages with their titles and slugs

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Developer tools

FAQ

amplitude-docs setup, tools, quality score, publishing readiness, and alternatives.

How do I add amplitude-docs to Claude, ChatGPT, or Cursor?

Add amplitude-docs to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://amplitude.com/docs/api/mcp.

Is amplitude-docs MCP ready for ChatGPT and Claude?

As of November 7, 2026, amplitude-docs scores 82/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and does not yet meet Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is amplitude-docs's MCP tool documentation?

As of November 7, 2026, amplitude-docs scores 54/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 5 of 5 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to amplitude-docs?

As of November 8, 2026, alternatives to amplitude-docs in developer-tools on the Manufact MCP leaderboard include Speko, Manufact, Context, AgentMail, and TPC Benchmarks.

How can amplitude-docs improve its MCP documentation?

get_page is the lowest-scoring reviewed tool at 51/100. Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

LeaderboardBack to leaderboardLeaderboardBack to leaderboard

Opening report…

Loading report overview

Server metadata

Loading server metadata

Discoverability

Loading discoverability

Protocol

Loading protocol

Tools

Loading tools

MCP Apps

Loading mcp apps

Tool documentation quality

Loading tool documentation quality

Title47/100

Not provided

Expand internal abbreviations and remove technical prefixes from the display title.

Description78/100

Report documentation gaps, broken examples, or ambiguous parameter descriptions to the Docs content backlog

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "send_docs_mcp_feedback",
  "description": "Report documentation gaps, broken examples, or ambiguous parameter descriptions to the Docs content backlog",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "category",
      "message"
    ],
    "properties": {
      "message": {
        "type": "string",
        "maxLength": 2000,
        "minLength": 1,
        "description": "Description of the documentation gap or issue"
      },
      "category": {
        "enum": [
          "missing_endpoint",
          "broken_example",
          "ambiguous_parameter",
          "missing_content",
          "other"
        ],
        "type": "string",
        "description": "Feedback category: missing_endpoint, broken_example, ambiguous_parameter, missing_content, or other"
      },
      "page_slug": {
        "type": "string",
        "maxLength": 512,
        "description": "Optional page slug where the issue was found"
      },
      "rationale": {
        "type": "string",
        "maxLength": 500,
        "description": "Brief explanation of why you are calling this tool"
      },
      "section_heading": {
        "type": "string",
        "maxLength": 200,
        "description": "Optional section heading where the issue was found"
      }
    }
  }
}

Manufact

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title40/100

Description76/100

Inputs75/100

Annotations0/100

Output schema0/100

Title62/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Title65/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Title44/100

Description73/100

Inputs75/100

Annotations0/100

Output schema0/100

Title47/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Put your MCP to the test

Overview

Related MCP servers

FAQ

Not your MCP?

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool documentation quality

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title40/100

Description76/100

Inputs75/100

Annotations0/100

Output schema0/100

Title62/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Title65/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Title44/100

Description73/100

Inputs75/100

Annotations0/100

Output schema0/100

Title47/100

Description78/100

Inputs75/100

Annotations0/100

Output schema0/100

Put your MCP to the test

Overview

Related MCP servers

FAQ

Not your MCP?

Tool documentation quality

Tool documentation quality