Skip to main content
Glama
Sign In
@prompteden/mcp-server

@prompteden/mcp-server

Official
by yulanventures
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @prompteden/mcp-server

No user-submitted related servers found.

    Related Servers

    • Taskade MCP Server

      kevindeluca27194
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents, and to build automations through natural language. It also includes an OpenAPI codegen that turns any OpenAPI spec into MCP tools.
      2,807 npm
      MIT

    • Cursor Cloud MCP

      BenItBuhner
      A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      29
      MIT

    • Amiqus MCP server

      dragosh29
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      MIT
    • prospectapis-mcp

      prospectapis-mcpofficial

      ProspectAPIs
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      14
      663 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources