EveryPage vs Linkly
A side-by-side look at the EveryPage and Linkly MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose EveryPage for marketing work as a local process; choose Linkly for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose EveryPage when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EVERYPAGE_API_KEY.
Choose Linkly when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
test_authentication, list_workspaces, batchDeleteLinks.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 43/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | EVERYPAGE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 25 |
| Full listing | View EveryPage | View Linkly |
Tools & capabilities
EveryPage tools
No tool names declared yet. Check the project README from the listing page.
Linkly tools 25
test_authenticationTest API Authenticationlist_workspacesReturn details of authenticated workspacebatchDeleteLinksBatch delete multiple linksupdate_workspaceUpdate workspace settings. Only the fields provided are changed; omitted fields keep their current values.list_linksList links with sorting and searchpingHealth checkcreate_linkCreate short links and URL shorteners. Use this when the user asks to shorten a URL, create a short link, or make a link shorter.update_linkUpdate an existing Linkly link by its IDdelete_linkDelete a Linkly link by its IDget_linkGet details of a specific Linkly link by its IDget_clicksGet recent click data for the workspaceget_analyticsGet time-series click analytics data for charting. Returns click counts over time.- +13 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
EveryPage
{
"mcpServers": {
"everypage": {
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "YOUR_EVERYPAGE_API_KEY_HERE"
}
}
}
}
Linkly
{
"mcpServers": {
"linkly": {
"url": "https://mcp.linklyhq.com"
}
}
}
Frequently asked questions
EveryPage is categorized under Marketing and uses a local stdio subprocess. Linkly belongs to Marketing and uses a remote HTTP/SSE transport. Pick EveryPage for marketing work and Linkly for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
EveryPage has no declared pricing — check the project's own site. Linkly has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add everypage and linkly as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EveryPage has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Linkly has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.