Skip to main content
Glama
sekera-radim

@briefgate/mcp

by sekera-radim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @briefgate/mcp

No user-submitted related servers found.

    Related Servers

    • Dropl MCP by develanet

      Dropl MCPofficial

      develanet
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to create client-editable photo and video galleries, upload and organize media in bulk, generate embed code for popular site builders, and manage client feedback — so non-technical clients can update their own content without a CMS.
      0
      MIT

    • Agent Dashboard

      wildware-uk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create projects, post rich status updates with images and video, claim tasks, read replies, and gate work behind user approvals over a live browser dashboard.
      2 npm
      1
      MIT

    • kanban

      Antles
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents native tools to pull their next prioritized, unblocked task with a full briefing (description, acceptance criteria, context files, conventions), comment and tick off criteria with evidence, ask the human decision-maker questions, and submit structured handoffs for review. It lets agents plan epics and sprints, report checks, create new tasks, and release work with checkpoints — all against a self-hosted board rather than files in the repo.
      4 npm
      MIT
    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.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes tied to specific resources (intake status vs results, add_items vs update_item vs update_intake), and transitions are documented. Minor potential confusion between get_intake_status and get_intake_results, and the two generic 'manage_*' tools, but descriptions resolve these well.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun pattern (define_intake, list_intakes, update_item, request_revision, create_folder). Deviations are minor: login/logout lack a noun, and verbs vary slightly (define_ vs create_, get_ vs list_) though usage is intuitive.

    Tool Count5/5

    15 tools is well-scoped for a client-intake lifecycle product; each tool maps to a distinct operation (intake CRUD, items, recipients, folders, webhooks, auth) with no filler.

    Completeness4/5

    Strong lifecycle coverage: create, list, update, status, results, revisions, chases, recipients, folders, webhooks, auth. Minor gaps remain — no archive/delete intake tool (archive state is referenced but not settable) and no remove-item operation, and owner decisions cannot be answered via API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources