Mammoth Analytics

Name: Mammoth Analytics
Author: EdgeMetric

by EdgeMetricversion 0.2.12i★ –iRuns in the cloud

Registry nameio.mammoth/mcp

Install

Overview

Description from the maker (original English)

Explore, clean, transform and export your Mammoth Analytics data from an AI client.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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

Install

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

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.mammoth.io/mcp

Run this in your terminal

claude mcp add --transport http mammoth https://mcp.mammoth.io/mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "mammoth": {
      "url": "https://mcp.mammoth.io/mcp"
    }
  }
}

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": {
    "mammoth": {
      "type": "http",
      "url": "https://mcp.mammoth.io/mcp"
    }
  }
}

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.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.mammoth.io/mcp

Menu names can differ slightly by plan and over time.

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

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

What it can do

The server asks you to sign in before it lists its tools.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain mammoth.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
✓ Pass
Endpoint responds
Responded in 637 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… 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 2969 servers in this category
Published to the registry more recently than 92% of the other 2969 servers in this category
Basic checks equal to or better than 100% of the other 2969 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 Mammoth Analytics safe?

It passed 3 of 3 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (0.2.12) reached the registry 2 days 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

MCP YouTube Transcript

by jkawamoto

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago

Install

Google Analytics MCP

by surendranb

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

Runs on your computer★ 244MITUpdated 9 days ago

Install

BibiGPT YouTube Video Summarizer

by JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Runs in the cloud★ 137MITUpdated 10 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.

mammoth-mcp-server

The Mammoth MCP server. An AI client (Claude, ChatGPT) uses its tools to explore, clean, transform and export data in Mammoth, as the signed-in user.

The server depends on one Mammoth package: the SDK (mammoth-io). Every tool reaches Mammoth through the API, as the SDK does. The server imports no backend code.

Hosted or local

Hosted: Mammoth runs this server at https://mcp.mammoth.io/mcp. Add that URL to your MCP client and sign in with your Mammoth account (OAuth). Nothing to install.
Local: pip install mammoth-mcp-server, then set MCP_ENCRYPTION_KEY and start mammoth-mcp-server (see From a virtual environment below). MCP_ENCRYPTION_KEY must be a Fernet key: 32 url-safe base64-encoded bytes. Generate one with python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())". The server refuses to start without it, or with a value that is not a Fernet key.

Layout

Path	What it holds
`mammoth_mcp_server/tools/`	The tools, one module per area (views, pipeline, files, dashboards, ...).
`mammoth_mcp_server/sdk.py`	The SDK client a tool call is given, and the API's errors in words a model can use.
`mammoth_mcp_server/jobs.py`	The wait for a job that an API route started.
`mammoth_mcp_server/task_params.py`	The map from a transformation to the pipeline task the API takes.
`mammoth_mcp_server/tokens.py`	The check of a caller's token: Mammoth says whether it is live and which server it is for.
`mammoth_mcp_server/store.py`	Short-lived records in Redis: upload tickets.
`mammoth_mcp_server/upload_routes.py`	The page a user drops a local file on.
`mammoth_mcp_server/server_card.py`	The public server card at `/.well-known/mcp/server-card.json`.
`mammoth_mcp_server/shape.py`	What a read tool hands the model, cut from the API's answer.
`mammoth_mcp_server/app.py`	The ASGI app and `main()`.
`mammoth_mcp_server/config.py`	Every deployment setting, read from the environment.

Settings

Variable	Default	Meaning
`MCP_SERVER_URL`	`https://mcp.mammoth.io`	This server, as a client reaches it.
`MAMMOTH_APP_URL`	`https://app.mammoth.io`	The web app, for the links a tool gives the user.
`MAMMOTH_DASHBOARD_URL`	`MAMMOTH_APP_URL`	The host that serves a published dashboard.
`MAMMOTH_API_URL`	`MAMMOTH_APP_URL` + `/api/v2`	The API every tool call goes to.
`MAMMOTH_API_ROOT`	`/api/v2`	The path the API is served under. Set it empty for an API reached directly.
`MAMMOTH_OAUTH_URL`	`MAMMOTH_APP_URL` + `/api/v2`	Mammoth's authorization server (its issuer), where a client signs the user in.
`MCP_REDIS_URL`	`redis://localhost:6379/0`	Where upload tickets are kept.
`MCP_ENCRYPTION_KEY`	none	A Fernet key. The caller's token in an upload ticket is sealed with it. Required.
`MCP_STORE_PREFIX`	`mammoth_mcp`	Keeps this deployment's records apart in a shared Redis.
`MCP_HOST`, `MCP_PORT`	`127.0.0.1`, `8270`	Where the server listens.

Sign-in

This server signs nobody in. Mammoth's own authorization server does: the OAuth server the Mammoth API serves. This server is an OAuth resource server only.

A client calls /mcp with no token. The server answers 401 and points to /.well-known/oauth-protected-resource/mcp.
That document names Mammoth's authorization server (MAMMOTH_OAUTH_URL). The client reads the server's metadata there and sends the user to it.
The user signs in to Mammoth, picks a workspace and a project, and approves. The client asks for a token for this server's URI, /mcp (the resource parameter, RFC 8707).
The client calls /mcp with that token. On every request the server asks Mammoth what the token is for (GET /workspaces/current). The server takes the token only when Mammoth says it is live and was issued for this server's URI.
Each tool call goes to the Mammoth API with the same token, so the user's permissions apply.

A token belongs to one workspace. A tool call for another workspace is refused. A Mammoth API token made by hand in Workspace settings was issued for no server, so this server refuses it.

The server keeps no sign-in and no token, with one exception: an upload link holds the caller's token, sealed, in Redis until the user uploads or 30 minutes pass.

What Mammoth needs

The MCP server's URI, /mcp, in mvc-service const.ini, section [oauth], key MCP_RESOURCES. Mammoth issues a token for no other resource.
GET /workspaces/current must return the token's resource beside the workspace id. Without it this server refuses every token.

Before it works in an environment below lists every step, in the order to check them.

Run

As a container, which needs nothing on the host but Docker

The image is built from this repository, so a deployment never waits for a release of the SDK. Build it from the repository root, which is the build context:

cp mammoth-mcp-server/deploy/.dockerignore.example .dockerignore

docker build -f mammoth-mcp-server/deploy/Dockerfile -t mammoth-mcp-server . docker run --env-file mammoth-mcp-server/deploy/.env -p 8270:8270 mammoth-mcp-server

With a Redis of its own, as one stack:

cp mammoth-mcp-server/.env.example mammoth-mcp-server/deploy/.env   # then set the values

docker compose -f mammoth-mcp-server/deploy/compose.yaml up -d --build

The server keeps nothing in memory between requests, so it scales by adding containers. They share only Redis.

From a virtual environment

pip install mammoth-mcp-server

cp .env.example .env # then set the values mammoth-mcp-server # or: uvicorn mammoth_mcp_server.app:create_app --factory

What `deploy/` holds

File	What it is for
`Dockerfile`	The image, built from this repository
`compose.yaml`	The server and a Redis, as one stack
`.dockerignore.example`	Copy to the repository root before building
`mammoth-mcp-server-container.service.example`	systemd, running the container
`mammoth-mcp-server.service.example`	systemd, running a virtual environment
`nginx.example.conf`	Both server blocks a deployment needs

Before it works in an environment

Each of these stops the sign-in on its own, so check them in order.

DNS and the front door point MCP_SERVER_URL at the server's port. deploy/nginx.example.conf holds the server block.
`MCP_ENCRYPTION_KEY` is set. It is the only secret this server keeps. Nothing else is required that has no default; see Settings.
Mammoth knows this server: MCP_RESOURCES = /mcp, in mvc-service const.ini, section [oauth]. Mammoth issues a token for no other resource.
The Mammoth host serves its OAuth metadata where a client looks for it. For an issuer with a path, RFC 8414 puts the document at /.well-known/oauth-authorization-server/api/v2, and apiv2 serves it at its own path, so the front door has to join the two. The second server block in deploy/nginx.example.conf does it. Check it with:

   curl https://<mammoth host>/.well-known/oauth-authorization-server/api/v2

It must answer the document, not 404.

The web app's OAuth consent page is deployed. Without it the user lands on a page that does not exist, and approves nothing.

Then a client connects to /mcp, and the user signs in to Mammoth and picks a workspace and a project.

Tests

cd mammoth-mcp-server

python -m pytest tests -q

The tests reach no server. The SDK client and the tools are real; only the HTTP transport under the client is replaced.

Mammoth Analytics

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

mammoth-mcp-server

Hosted or local

Layout

Settings

Sign-in

What Mammoth needs

Run

As a container, which needs nothing on the host but Docker

From a virtual environment

What deploy/ holds

Before it works in an environment

Tests

What `deploy/` holds