@prompteden/mcp-server
OfficialRelated Servers
Alternatives to @prompteden/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseAqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to read an Amiqus ID account—clients, onboarding records and steps, check results, templates, case status counts and webhooks—and, when writes are enabled, create records.9MIT

prospectapis-mcpofficial
AlicenseAqualityCmaintenanceEnables MCP clients such as Claude Desktop, Claude Code, Cursor and Windsurf to search funding rounds, manage webhook watchlists and commission cited prospect research briefs through fourteen API-backed tools. Read-only lookups are free while paid actions such as research submissions and watchlist deliveries are metered against the account balance.14580 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Code or Codex to administer a Bifrost LLM gateway's governance API, including virtual keys, teams, customers, budgets, provider configs, routing rules, model/pricing config, request-log observability, and core gateway config.13 npm1MIT

AppDrift MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Desktop and Cursor to read tracked app keywords, opportunities, account apps, and action plans; generate or translate listing copy; review results; and apply accepted title, subtitle, keywords, or short-description fields to an editable draft without publishing to Apple or Google.63 npmMIT
apexapi-mcpofficial
AlicenseAqualityDmaintenanceEnables calling 120+ AI models and reading live web pages (scrape, crawl, structured extract) from any MCP client using one API key.9108 npmMIT
TDQS
Scored across 20 tools
Most tools target clearly distinct resources and actions across monitors, projects, analytics reports, and goals. The 11 analytics tools are separated by specific endpoint purpose, though several 'get' analytics reports could be momentarily confused without reading descriptions; overall boundaries remain clear.
Names are consistently snake_case and mostly follow a verb_noun pattern, with an analytics_ prefix grouping analytics tools. Minor deviations include agent_status (noun_status) and get_results (no monitor prefix), but the pattern remains readable.
20 tools is heavy for a single MCP server, even though they are grouped across monitors, analytics, projects, account, and providers. Each appears to map to a distinct API endpoint, but the count sits in the borderline heavy range of 16–25.
Core create/list/get coverage exists for projects, monitors, and analytics, but update and delete operations are missing for projects and monitors. These notable CRUD gaps could force agents to work around missing lifecycle operations.