Skip to main content
Glama
Sign In
@apinator/mcp

@apinator/mcp

Official
by apinator-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @apinator/mcp

No user-submitted related servers found.

    Related Servers

    • agent-bridge

      umairulh2001
      A
      license
      A
      quality
      B
      maintenance
      Enables multiple AI coding sessions (Claude Code, Codex, Opencode, scripts and CI bots) to exchange messages in real time, either directly by name or broadcast, with grouping into isolated rooms and queued delivery for offline agents. Supports push notifications into Claude Code conversations, long-poll waiting, HTTP webhooks and WebSocket agents, plus token authentication.
      6
      MIT

    • console-stream-mcp

      Topman-14
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to access live console logs, errors, and network requests from web applications via a local WebSocket connection, without copying data to chat.
      13 npm
      19
      MIT

    • browspark-mcp

      outofmemry
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse, click, and debug real websites in the user's own signed-in browser or a dedicated Chrome instance, with only explicitly shared tabs reachable and revocable at any time. Exposes the full developer toolbox — console, network, sources, debugger, elements, performance and CPU/memory profiling, storage, service workers, coverage, emulation, accessibility, security, Lighthouse, and Playwright-test recording — as first-class tools callable in one step.
      42 npm
      1
      MIT

    • agentic-mcp-server

      cintelis
      F
      license
      Not graded
      quality
      D
      maintenance
      Real-time observability dashboard for monitoring AI agents in multi-agent development workflows, with live WebSocket updates of tool calls, sessions, and usage statistics.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Webhook tools are cleanly partitioned by action (list/add/edit/delete/test/deliveries), and channel tools are similarly distinct (list/get, publish, sign auth, watch). There is little overlap; even the observability tools target different resources, such as webhook deliveries versus live channel events.

    Naming Consistency5/5

    Every tool follows a snake_case verb-first pattern with resource-oriented nouns: list_webhooks, add_webhook, edit_webhook, publish_event, sign_channel_auth, watch_channel. Singular/plural usage is consistent with get/list semantics, and there are no mixed conventions.

    Tool Count5/5

    The 11 tools map well to the domain: webhook lifecycle and delivery inspection plus channel listing, publishing, auth signing, and live watching. Each tool has a clear role, with no obvious filler or missing lightweight operation forcing extra calls.

    Completeness4/5

    Webhook coverage is essentially full CRUD plus testing and delivery inspection; channel coverage includes listing, lookup, publishing, auth signing, and live watching. Minor gaps remain, such as no single-webhook getter beyond list_webhooks or event-history retrieval, but core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources