sape-mcp
Related Servers
Alternatives to sape-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.201,334 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the ChatGPT Ads API as tools an LLM host can call.4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for buying advertising outcomes such as Telegram subscribers and website traffic from a prepaid balance. Provides tools for campaign management, forecasting, and budget control, with guardrails so agents can spend but not fund or withdraw.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating FinanceMarker.ru with LLM agents, IDEs, n8n, and other MCP-compatible clients. It proxies the FinanceMarker REST API and exposes it as a set of MCP tools.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Linkavista's Advertiser API, enabling natural language management of backlink purchases: search sites, create orders, check balance, and more, secured via OAuth on Cloudflare Workers.2MIT
TDQS
Scored across 12 tools
Most tools have clearly distinct scopes: account, projects, URLs, anchors, page search, and placement creation. Minor overlap exists between get_balance and get_user, and between get_project_links and get_url_links, but descriptions clarify project-level versus URL-level scope. sape_call overlaps by design as a fallback but is explicitly framed that way.
The set mostly follows a predictable snake_case verb_noun convention: get_*, list_*, search_pages, create_placement, create_placements. The main deviations are the generic sape_call and the singular/plural pair create_placement/create_placements, which is readable but slightly easy to confuse.
Twelve tools is well within the appropriate range for a focused Sape integration. The set covers reads, search, single and batch purchases, plus a generic fallback without becoming bloated.
Core workflows are covered: account balance, user info, projects, URLs, anchors, existing links, page search, and link purchase. Dedicated update/delete operations for placements and project/URL lifecycle management are missing, but sape_call provides a generic escape hatch for unsupported API methods.