Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Bitly MCPShortlist candidate | Google Search Console MCP Server for SEOsMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Bitly · Publisher source ↗ | Community implementation github:aminforou · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 15, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 1,712 GitHub stars · checked 2026-09-24T04:14:16.248000Z |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | OAuth 2.1 is the recommended method for clients that support it; an API token is also supported for simpler/non-OAuth setups. | Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property. |
| Cost | The reviewed MCP page does not document a separate MCP charge. Bitly has a free tier and paid plans; plan entitlements affect available features, custom domains, sites, analytics and other capabilities. | The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented. |
| Permissions | Bitly tools operate on organizations/groups the authenticated user can access. Several administrative tools require group/admin authority, and the server exposes both read and write operations. | Lists Google Search Console properties and reads analytics, URL inspection, and sitemap data. Site and sitemap add/delete tools are disabled unless GSC_ALLOW_DESTRUCTIVE=true. |
| Data handling | Not documented in the reviewed sources. The reviewed Bitly MCP documentation does not provide a separate MCP-specific retention/training statement. Tools can retrieve link/group analytics and export data. | Search Console properties, queries, pages, crawl and indexing results, and sitemap data are returned to the connected client. OAuth tokens are saved for reuse; service-account JSON is read from a configured path. Further retention is not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can create/update/delete links, QR codes and Bitly Sites, publish drafts, change redirect destinations, manage custom domains, and export analytics/data. A mistaken mutation can redirect public traffic or take a live site/link offline. | Can expose private Search Console data and, when explicitly enabled, modify sites or sitemaps. Protect credential files, leave destructive tools disabled unless required, and restrict remote SSE deployments. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-08-11 |
| Candidate evidence | 2026-10-19 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →