Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Keypup Engineering Analytics

by keypup-ioversion 1.0.1i★ –iRuns in the cloud
Registry nameio.keypup/engineering-analytics

Install

Overview

Description from the maker (original English)

Generate answers & visualizations from your engineering data to track software development health.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Marketing & social media
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http engineering-analytics https://hq.keypup.io/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "engineering-analytics": {
      "url": "https://hq.keypup.io/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "engineering-analytics": {
      "type": "http",
      "url": "https://hq.keypup.io/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret required HTTP header
    The Bearer API token for authentication. See: https://docs.keypup.io/en/articles/15360547-using-the-mcp-server

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain keypup.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 2958 servers in this category
  • Published to the registry more recently than 12% of the other 2958 servers in this category
  • Basic checks equal to or better than 100% of the other 2958 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Keypup Engineering Analytics safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago
Install

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 9 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Keypup MCP Server

Ask your Keypup engineering data in plain language to track delivery, quality and team workload.

The Keypup MCP (Model Context Protocol) server plugs your Keypup engineering analytics directly into any MCP-compatible AI assistant — Claude, Cursor, Kiro, ChatGPT Desktop, Gemini CLI, VS Code, and others.

Once connected, you ask questions about your engineering activity in plain language and the AI builds and runs the underlying reporting queries for you. No query language to learn, no code to write.

Unlike the GraphQL API, which is designed for developers writing application code, the MCP server is designed to be driven conversationally by an AI on your behalf.

Beta: The Keypup MCP server is currently in beta. The exposed capabilities

are continuously expanded during this phase. Feedback and use cases are

welcome via the in-app chat.

What it can do

The server exposes a focused set of read-only tools that let an AI explore and query your Keypup data:

  • Discover your companies — list the companies (teams) you belong to.
  • Explore datasets — browse the available datasets and the fields each one exposes.
  • Discover formula operators — list the functions and operators available when building metrics, dimensions, and filters.
  • Run reporting queries — execute aggregated queries against any dataset, with metrics, dimensions (group-by), filters, sorting, and pagination.
  • Generate a query from natural language — turn a plain-language request into a ready-to-run structured query that the AI can then execute.

The AI orchestrates these tools automatically. A typical flow:

  1. List your companies
  2. Pick the relevant dataset
  3. Look up the fields it needs
  4. Build the query
  5. Run it
  6. Summarize the results

You only ask the question.

Tools

ToolDescription
list_companiesList the companies (teams) the authenticated user belongs to. Returns each company's id, name, created_at and updated_at. The id is required by most other tools.
list_datasetsList the datasets (facts) available for querying, each with its id, label and description.
list_dataset_fieldsList the fields available on a given dataset for a company. Supports filtering by source (NATIVE/CUSTOM) and a regex pattern matched against the field id, plus pagination.
list_formula_operatorsList the operators and functions usable in custom formulas. Supports filtering by scope (DIMENSION/METRIC) and a regex pattern, plus pagination. Set verbose: true for full per-operator documentation.
query_datasetRun an aggregated report against a dataset. Metrics, dimensions and filters are expressed as text-based formulas, with optional sorting, limit and offset.
generate_dataset_queryTurn a natural-language prompt into a structured query compatible with query_dataset.
Datasets

The reporting engine runs over the following datasets (facts):

  • `ISSUES_PULL_REQUESTS` — issues and pull requests.
  • `ACTIVITY_EVENTS` — transitions on issues/PRs (status changes, assignments, work logged, open/close/reopen).
  • `COMMENTS` — comments on issues, PRs and reviews.
  • `COMMITS` — commits attached to pull requests.
  • `REVIEWS` — pull request reviews.

Example questions

Delivery & throughput

  • "How many pull requests did we merge each month over the last 6 months?"
  • "What's our weekly issue closing rate this quarter?"
  • "How many commits were made per author last month?"

Cycle time & performance

  • "What's the average time between PR creation and merge over the last 12 weeks?"
  • "Show me the review turnaround time trend for the last 3 months."
  • "Which repositories have the slowest cycle time?"

Quality & process

  • "How many bugs were raised vs. closed each week this quarter?"
  • "What proportion of our pull requests resolve at least one issue?"
  • "How many PRs were merged without a review?"

Workload & collaboration

  • "Who are our most active reviewers this month?"
  • "How is work distributed across the team right now?"
  • "How many comments do our pull requests receive on average?"

Open-ended exploration

  • "Summarize our engineering activity over the last month."
  • "Compare open vs. closed issues over time."
  • "What labels are most common on our issues?"

You can refine iteratively: "now break that down by repository", "restrict it to the backend team", and so on.

Setup

Endpoint
https://hq.keypup.io/mcp

The server uses the streamable HTTP transport and supports two authentication methods:

  1. OAuth 2.1 (recommended) — the client registers itself dynamically and you authorize access through your browser. No token to copy or store.
  2. API token — a Keypup API token passed in the Authorization header. Use this when your client does not support OAuth dynamic client registration.
Option 1 — OAuth (recommended)

If your client supports OAuth 2.1 with dynamic client registration (e.g. via a Client ID Metadata Document), point it at the endpoint with no credentials:

{

"mcpServers": { "keypup": { "type": "http", "url": "https://hq.keypup.io/mcp" } } }

On first connection the client opens a browser window to sign in to Keypup and authorize access. There is no token to generate, copy, or rotate — this is the configuration shipped in this repo's .mcp.json.

If your client does not open an authorization prompt (or fails to register),

it likely does not support dynamic client registration yet. Use the API token

method below instead.

Option 2 — API token

For clients without OAuth dynamic client registration support, add a keypup server entry pointing at the endpoint, with your API token in the Authorization header:

{

"mcpServers": { "keypup": { "url": "https://hq.keypup.io/mcp", "headers": { "Authorization": "Bearer my_keypup_api_token" } } } }

Notes:

  • Replace my_keypup_api_token with the token you generate (see below). Keep the Bearer prefix.
  • The server name (keypup) is arbitrary — name it however you like.

Once saved, restart or reconnect the MCP server in your client. The Keypup tools should appear in the client's tool list, and you can start asking questions.

Generating an API token

Only needed for Option 2 (API token). If you authenticate via OAuth, skip

this section.

The MCP server authenticates with the same API tokens used by the GraphQL API.

  1. Go to Settings → Account and open the API Token tab.
  2. Click Create token.
  3. Set a descriptive name (e.g., "MCP - Claude Desktop") and an expiration. Setting an expiration is strongly recommended.
  4. Select the token scopes. The minimal recommended scopes for the MCP server are:
  • Reports read (viz:reports:read) — required to explore datasets/fields and run reporting queries.
  • Companies read (hq:companies:read) — required to list the companies you belong to and resolve the company ID used in queries.
  1. Click Create. The token is shown only once and can be copied for one minute — copy it into your MCP client configuration right away.

Following the principle of least privilege, grant only the scopes you need. The two scopes above are enough to use the full analytics capabilities of the MCP server.

The token grants the same level of data access you already have in the Keypup user interface — queries are automatically scoped to the companies you are a member of.

Security

  • All Keypup MCP tools are read-only — they never modify your data.
  • Queries are automatically scoped to the companies you belong to (data isolation).
  • Treat your API token like a password. Anyone holding it can query your Keypup data within the granted scopes.
  • Prefer short-lived tokens with an expiration, and rotate them periodically.
  • Keep tokens out of shared or version-controlled files. Store them in your MCP client's local configuration only.

Resources

Ask PopNx