Parse.ly MCP Server

by parsely-dash Your server? Claim it

answering

Parse.ly MCP is answering right now. Last checked 5 min ago.

Query your Parse.ly content analytics: top content, referrers, campaigns, trends and real-time data.

Uptime history 48 days of history · worst day 98%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

207 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Parse.ly MCP does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://dash.parsely.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://dash.parsely.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://dash.parsely.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://dash.parsely.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://dash.parsely.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://dash.parsely.com/mcp	streamable-http	sign-in	224 ms	5 min ago

Alternatives to Parse.ly MCP

same job, measured the same way

Logly

by logly-uk

Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.

43 installs/wk local only

Nevent MCP

by nevent-dev

Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT.

117 installs/wk 63 tools answering

Pulse Analytics MCP server

by ciphera

Read-only web analytics from Pulse: your sites, totals, trends, breakdowns and realtime visitors.

answering

Measure.events Analytics

by meetclawdius

Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.

13 tools answering

Getcims

by getcims

Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents

7 tools answering

Toffu

by toffu

AI marketing platform your agent runs end to end: ads, analytics, content, and reports.

answering

Mcpulse

by getmcpulse

Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.

answering

Analytics

by zenovay

Real-time web analytics for AI agents: query traffic, funnels, revenue, and manage your sites.

answering

Parse.ly MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Parse.ly MCP?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Parse.ly MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 207 ms. The bar chart above shows every period we have measured.

How do I connect Parse.ly MCP?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Parse.ly MCP?

No API key is involved. Parse.ly MCP answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Parse.ly MCP?

It answers our handshake in 207 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.