Skip to main content
Glama
pos-buzz

posbuzz-mcp

Official
by pos-buzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to posbuzz-mcp

No user-submitted related servers found.

    Related Servers

    • claudecode-mcp

      trevoraspencer
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT

    • mcp-api-gateway

      rflpazini
      F
      license
      A
      quality
      D
      maintenance
      A universal MCP server that integrates any API with Claude Desktop by pointing it at a Swagger/OpenAPI spec, automatically generating tools for interaction.
      3
      44
      -

    • ringg-mcp

      sabaljain
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that lets Claude Code read Ringg AI assistants, knowledge bases, and call history, and make targeted edits to prompts, custom variables, and knowledge base attachments without placing calls.
      10
      MIT

    • mcp-gateway

      dooosp
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes local agents as tools for Claude Code, enabling capabilities in quant, trading, news, reports, robotics, Notion, and FreeCAD.
      12 npm
      1
      -

    • mcp_sdk_eyra_accelerator

      Vaishnavi-jagan
      F
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server that exposes API endpoints as tools for AI assistants by proxying requests to a target API defined in an OpenAPI specification. It supports various authentication methods and utilizes Server-Sent Events (SSE) to facilitate integration with clients like Claude and ChatGPT.
      -
    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

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: workspaces, runs, results, EC sync, and token usage are clearly separated. Overlap between result readers is mitigated by explicit 'big picture' vs 'post-level' vs 'per-account' vs 'EC performance' descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (read_, list_, create_, start_, import_, delete_). No mixed conventions or vague verbs like 'process' or 'run' standalone.

    Tool Count5/5

    Fourteen tools is well within the ideal range and each maps to a clear step in the analysis workflow: manage workspaces, start runs, check status, fetch results, and sync/delete EC data. No redundant tools.

    Completeness4/5

    The core lifecycle is covered: workspace create/read/list, run start/status/list, and full result retrieval (summary, social posts, accounts, EC metrics). Minor gaps like workspace update/delete and run cancellation are absent, but they are not essential to the primary analysis workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources