ap-mcp-server
Related Servers
Alternatives to ap-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to query ContentRadar data and write low-risk content using natural language, with 15 tools for monitoring, analysis, and content management.MIT

APITube News MCP-Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search real-time and archived news from 300,000+ sources across 177 countries and 59 languages, with filters for sentiment, entities, categories, and more, plus taxonomy suggestion for precise queries.MIT
newspaper-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables LLM agents to discover news sources, list articles, parse and extract article text, search news, and perform NLP analysis such as keyword extraction and summarization.MIT- AlicenseAqualityCmaintenanceEnables AI-driven analysis of aggregated news and hot topics from 35+ platforms, providing tools for trend tracking, sentiment analysis, and similar-content retrieval through natural language conversations.27GPL 3.0
- FlicenseNot gradedqualityDmaintenanceExposes publisher journalism to LLMs and agent frameworks via search, retrieval, source grounding, and consistent citation, enabling accurate content retrieval with attribution and policy enforcement.-

Perigon MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables access to comprehensive news data through the Perigon API, including searching for articles, stories, journalists, sources, people, companies, topics, and Wikipedia content with advanced filtering capabilities.6Apache 2.0
TDQS
Scored across 26 tools
Most tools target distinct resources, but there is notable overlap between search_content and search_content_all, build_search_query and optimize_search_query, and get_trending_subjects and analyze_content_trends. Descriptions help differentiate them, but an agent could easily select the wrong one without careful reading.
Tool names are mostly snake_case with a verb_noun structure, but there are inconsistencies such as mixing get and list (get_account_info vs list_monitors) and using different verbs for similar actions (search, build, optimize, analyze). The pattern is readable but not perfectly uniform.
With 26 tools, the server exceeds the 25-tool threshold for heavy surface area. While the broad AP API scope justifies many tools, the count feels bloated and could benefit from consolidation or splitting into focused servers.
The tool surface covers major workflows: content search/retrieval including bulk and pagination, monitor CRUD and status, account info, RSS access, and query helpers. Minor gaps exist such as no tool to manage followed topics or update content, but these are likely intentional for a consumption-focused API.