LinkBit MCP vs Pageree
A side-by-side look at the LinkBit MCP and Pageree MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LinkBit MCP for marketing work as a local process; choose Pageree 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 LinkBit MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APP_URL, API_KEY. - You want tools like
shorten_url, shorten_urls, list_links.
Choose Pageree when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 77/100 · Great | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APP_URLAPI_KEY | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View LinkBit MCP | View Pageree |
Tools & capabilities
LinkBit MCP tools 9
shorten_urlExisting `utm_*` on the URL are not overwritten; `#fragment` is keptshorten_urlsBulk createlist_linksNewest firstupdate_linkPATCHdisable_linkStops redirects. `destructiveHint: truedelete_linkPermanent. `destructiveHint: trueget_qrsvg, `color`, `logo`, `printget_link_statsCountries, devices, referrers, dailyget_analyticsAccount overview
Pageree tools
No tool names declared yet. Check the project README from 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.
LinkBit MCP
{
"mcpServers": {
"linkbit-mcp": {
"command": "npx",
"args": [
"-y",
"linkbit-mcp"
],
"env": {
"APP_URL": "YOUR_APP_URL_HERE",
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
Pageree
{
"mcpServers": {
"pageree-2": {
"url": "https://mcp.pageree.com/"
}
}
}
Frequently asked questions
LinkBit MCP is categorized under Marketing and uses a local stdio subprocess. Pageree belongs to Marketing and uses a remote HTTP/SSE transport. Pick LinkBit MCP for marketing work and Pageree 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.
LinkBit MCP has no declared pricing — check the project's own site. Pageree 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 linkbit-mcp and pageree-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LinkBit MCP has a quality signal of 77/100 (Great) with 1 views, 0 installs and 0 GitHub stars. Pageree has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.