Parse.ly

MCP server by Parse.ly (Automattic)

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

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Parse.ly

Parse.ly needs sign-in. Connect with its own URL:

https://dash.parsely.com/mcp

Your client opens Parse.ly (Automattic)’s sign-in the first time you use it. The token stays between your client and Parse.ly (Automattic).

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/parsely

About

Connects to Parse.ly, the content analytics platform, so an assistant can answer questions about site performance. It covers top content, referrers, campaigns, trends and real-time data from your Parse.ly account.

The server is hosted at https://dash.parsely.com/mcp and uses streamable HTTP. Users sign in with OAuth and no local install is needed. Individual tool names are not published in the available documentation.

What you can do

  • Look up top-performing content
  • Break down traffic by referrer
  • Review campaign performance
  • Check content trends over time
  • View real-time audience data

Tools

Parse.ly lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • What were my top posts this week on Parse.ly?

  • Which referrers sent the most traffic to my site yesterday?

  • Show how my newsletter campaign performed this month.

  • What content is trending right now?

Set up

Every client connects to dash.parsely.com, and Parse.ly (Automattic) asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http parsely https://dash.parsely.com/mcp
  1. Start Claude Code, type /mcp, pick parsely and choose Authenticate. A browser window opens for the Parse.ly (Automattic) sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Parse.ly and paste this URL:
https://dash.parsely.com/mcp
  1. Click Add, then Connect, and sign in when Parse.ly (Automattic) asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://dash.parsely.com/mcp and click Add.
  2. Click Connect and sign in when Parse.ly (Automattic) asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://dash.parsely.com/mcp as the server URL and choose OAuth. ChatGPT sends you to Parse.ly (Automattic) to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"parsely","type":"http","url":"https://dash.parsely.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

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

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "parsely": {
      "serverUrl": "https://dash.parsely.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add parsely --url https://dash.parsely.com/mcp
codex mcp login parsely

Or edit ~/.codex/config.toml directly:

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

Gemini CLI

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

Then, inside Gemini CLI, run /mcp auth parsely to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://dash.parsely.com/mcp.

FAQ

Can I paste mcp.tc/i/parsely into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://dash.parsely.com/mcp, so your client talks to Parse.ly directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Parse.ly need an API key or a sign-in?

Yes, you need a Parse.ly (Automattic) account. The first time your client connects, it opens Parse.ly (Automattic)’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Parse.ly a remote or a local server?

Remote. Parse.ly (Automattic) hosts it at https://dash.parsely.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Parse.ly do?

You can look up top-performing content, break down traffic by referrer and review campaign performance.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read Parse.ly’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show Parse.ly in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Parse.ly on mcp.tc](https://mcp.tc/i/parsely/badge.svg)](https://mcp.tc/i/parsely)
HTML
<a href="https://mcp.tc/i/parsely"><img src="https://mcp.tc/i/parsely/badge.svg" alt="Parse.ly on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/parsely.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/parsely" title="Parse.ly on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/parsely.json

What each field means

mcp.tc isn’t affiliated with Parse.ly (Automattic). This page was built from Parse.ly’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.