Altmetric Mcp

Altmetric MCP Server

Model Context Protocol (MCP) server that enables AI agents to access Altmetric APIs for tracking the attention and reach of research outputs across news outlets, policy documents, social media, and other online platforms.

Altmetric monitors where research is being discussed beyond traditional academic citations - from mainstream media coverage to policy citations, patent references, and social media engagement - providing a comprehensive view of real-world research impact.

There are two ways to connect:

• Hosted server (recommended) - point your AI client at https://mcp.altmetric.com/mcp and sign in with your Altmetric account. No API keys to copy or store, and you automatically get the tools for whatever you have access to (Explorer, Details Page, or both). Start here.
• Run locally - run the server on your own machine with your own API keys, over stdio. For offline use or when you'd rather manage keys directly. See Run locally with your own API keys below.

What access you need

The server works with access to either one of Altmetric's APIs on its own - the Details Page API or the Explorer API - and gives you the tools for whichever you have. To get the full potential of Altmetric, having both is strongly recommended, because they answer different questions:

• Details Page API - the attention for a specific research output, looked up by identifier (DOI, PubMed ID, etc.), and a search of recent attention by timeframe.
• Explorer API - searching, filtering and aggregating research outputs, mentions, audience demographics and journals across the whole Altmetric database, and across your own institution's outputs.

With only one, you get only that API's tools. See Tools for which tools come with each API, and request API access if you're missing one.

Connect to the hosted server (recommended)

The easiest way to use Altmetric in your AI client is the hosted server at https://mcp.altmetric.com/mcp. Point your client at that URL and sign in with your Altmetric account when prompted - the client runs a standard OAuth flow in your browser, so there are no API keys to copy or store. You get exactly the tools your account has access to.

Claude Desktop

1. Open Settings → Customize → Connectors and click Add custom connector.
2. Name it Altmetric and enter the URL https://mcp.altmetric.com/mcp.
3. Click Add, then Connect, and sign in when the browser window opens.

Verify by asking Claude: "Use the Altmetric tools to look up the attention score for DOI 10.1038/nature12373"

Claude Code

claude mcp add --transport http altmetric https://mcp.altmetric.com/mcp

Then run /mcp inside Claude Code, select altmetric, and authenticate - a browser window opens for sign-in.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{  "mcpServers": {    "Altmetric": {      "url": "https://mcp.altmetric.com/mcp"    }  }}

Cursor runs a browser sign-in the first time the server is used.

VS Code (GitHub Copilot)

Add to .vscode/mcp.json (VS Code 1.101 or later):

{  "servers": {    "Altmetric": {      "type": "http",      "url": "https://mcp.altmetric.com/mcp"    }  }}

Open the Command Palette, run MCP: List Servers, select Altmetric, and start it; sign in when prompted.

ChatGPT

Open Settings → Connectors → Advanced and turn on Developer mode, then Settings → Connectors → Add custom connector, enter https://mcp.altmetric.com/mcp, and complete the OAuth sign-in. Requires a paid plan (Plus, Pro, Business, Enterprise, or Edu); custom connectors aren't available on the free tier. All Altmetric tools are read-only, so the read-only restriction on Plus/Pro plans doesn't limit them.

Other MCP clients

Any client that supports the Streamable HTTP transport with OAuth can connect. Point it at https://mcp.altmetric.com/mcp. On the first request the server returns 401 with a WWW-Authenticate header pointing at its discovery document (/.well-known/oauth-protected-resource), which the client uses to run the OAuth flow against Altmetric Explorer automatically.

How sign-in works

The hosted server is an OAuth 2.1 resource server. Your client obtains a bearer token from Altmetric Explorer (the authorization server) for the mcp scope. The server exchanges that token for your account's entitlements and calls the Altmetric APIs on your behalf - your bearer token is never forwarded to those APIs. The advertised toolset reflects your entitlements, so you only ever see the tools for the products you can use.

Example prompts

Once connected, ask in plain language - your client picks the tool. Each of these exercises a different one:

You only see the tools your account is entitled to, so the Explorer prompts need institutional access. The full toolset is in Tools below.

Data sources and licensing

Every tool calls Altmetric's own APIs - the Details Page API and the Explorer API, both first-party Altmetric (Digital Science) services. The server proxies no third-party API and holds no third-party data of its own.

What those APIs return includes attention collected from third-party platforms under Altmetric's own agreements with them, and one of those agreements changes what comes back. Under Altmetric's licence with X (formerly Twitter), mentions from X carry numeric identifiers only: no account handle, display name or post text, at any tier and on either API. Counts, ids and aggregate demographics are available; named accounts are not. See X mentions and X data in Altmetric's APIs.

Every other source - news outlets, blogs, Bluesky, Reddit, podcasts, policy documents, patents - comes back named.

Run locally with your own API keys

Prefer to run the server yourself - offline, or managing API keys directly? Run it over stdio with npx.

Prerequisites

• Node.js 20.6.0 or later - an actively-supported LTS release is recommended (download)
• Altmetric API credentials (at least one, both recommended - see What access you need above):
  • Details Page API key - Free tier or commercial access
  • Explorer API key + secret - Institutional access

Don't have keys yet? Request API access

Quick install (Claude Desktop on macOS)

Run the guided installer in Terminal - it checks Node.js, prompts for your API keys, and configures Claude Desktop automatically:

bash <(curl -fsSL https://raw.githubusercontent.com/altmetric/altmetric-mcp/main/install.sh)

Or if you've cloned the repo:

bash install.sh

Prefer to set things up manually? See the per-client instructions below.

Manual configuration

Configure your MCP client to run the server using npx. Include only the API credentials you have access to.

{  "type": "stdio",  "command": "npx",  "args": ["-y", "altmetric-mcp"],  "env": {    "ALTMETRIC_DETAILS_API_KEY": "your_details_api_key_here",    "ALTMETRIC_EXPLORER_API_KEY": "your_explorer_api_key_here",    "ALTMETRIC_EXPLORER_API_SECRET": "your_explorer_api_secret_here"  }}

claude mcp add --transport stdio altmetric-mcp \  --env ALTMETRIC_DETAILS_API_KEY=your_details_api_key_here \  --env ALTMETRIC_EXPLORER_API_KEY=your_explorer_api_key_here \  --env ALTMETRIC_EXPLORER_API_SECRET=your_explorer_api_secret_here \  -- npx -y altmetric-mcp

{  "servers": {    "Altmetric": {      "type": "stdio",      "command": "npx",      "args": ["-y", "altmetric-mcp"],      "env": {        "ALTMETRIC_DETAILS_API_KEY": "your_details_api_key_here",        "ALTMETRIC_EXPLORER_API_KEY": "your_explorer_api_key_here",        "ALTMETRIC_EXPLORER_API_SECRET": "your_explorer_api_secret_here"      }    }  }}

{  "mcpServers": {    "Altmetric": {      "type": "stdio",      "command": "npx",      "args": ["-y", "altmetric-mcp"],      "env": {        "ALTMETRIC_DETAILS_API_KEY": "your_details_api_key_here",        "ALTMETRIC_EXPLORER_API_KEY": "your_explorer_api_key_here",        "ALTMETRIC_EXPLORER_API_SECRET": "your_explorer_api_secret_here"      }    }  }}

Deploying the local server safely

The local server runs as a child process of the MCP host (Claude Desktop, Claude Code, etc.). A few things are worth knowing before you wire it into a sensitive workflow.

What the server does

• Read-only proxy to two Altmetric HTTP APIs over outbound HTTPS. The one exception is an idempotent POST to the Explorer identifier_lists endpoint (create-or-find), used internally to scope an Explorer query to a supplied set of identifiers; it creates no user-visible state and is not destructive.
• No inbound network surface; no destructive operations.
• Treats upstream text as untrusted: scans for prompt-injection markers, redacts suspicious matches in the LLM-facing summary, and surfaces raw values only via structuredContent.

What you should do

• Set API keys via your MCP host's env block, not via a committed .env file. Keys appear in URL query strings; treat them as bearer-equivalent credentials.
• Run with reduced privileges if your host allows it. The server only needs outbound HTTPS to api.altmetric.com and www.altmetric.com. If your host or container runtime supports it, deny filesystem writes outside $TMPDIR and deny other network egress.
• Consider an egress allowlist (forward proxy / DLP). If you're using the server inside an environment that processes sensitive data, route outbound traffic through a proxy that only allows the two Altmetric hosts. The server doesn't need to talk to anyone else.
• Respect your data-classification zone. This server forwards tool arguments verbatim to a third party. If your prompt contains restricted or regulated data, it leaves your boundary.

What's enforced for you

• Outbound URLs are asserted to use https:.
• Upstream responses are capped at 20 MB and 60 s.
• Inbound tool arguments are capped at 8 MB total / 64 KB per string.
• Filter values are validated client-side (date format, length, pagination ranges) before any upstream call.
• Upstream error bodies are logged to stderr by SHA-256 prefix only, not verbatim.

For vulnerability reports and supported versions see SECURITY.md.

Troubleshooting

API Tiers

Details Page API

• Free Tier: Access to get_citation_counts and search_citations
• Commercial Tier: Access to all Details Page tools including get_citation_details

If you attempt to use get_citation_details with a free API key, you'll receive a 403 error.

Explorer API

• Institutional Access Only: All Explorer API tools require institutional credentials
• Provides access to research outputs and attention data across the entire Altmetric database
• Organizations with data integrations can also access their own institutional research outputs in isolation
• Includes advanced filtering by author, department, journal, and custom organizational metadata

Tools

This server provides twelve tools across two APIs:

All Explorer tools additionally accept researcher_id and grant_id filters (Dimensions IDs), and an identifiers parameter that scopes a query to a raw list of scholarly identifiers - the server builds the corresponding identifier list for you. Explorer responses also include sentiment data (sentiment-analysis-totals on research outputs, sentiment-analysis on X/Bluesky mentions).

For detailed parameters and examples, see TOOLS.md.

API Documentation

• Details Page API: https://docs.altmetric.com/details-page-api/
• Explorer API: https://docs.altmetric.com/explorer-api/

License

MIT