Skip to main content
Glama
K-Jadeja

@kjadeja/open-featurebase-mcp

by K-Jadeja

Related Servers

Alternatives to @kjadeja/open-featurebase-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Open Feedback, enabling AI assistants to submit, list, get, update status of, and analyze product feedback via a local HTTP API and JSONL storage.
      346 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Official MCP server for FeatureJet, enabling agents to read and act on customer feedback boards: list/search posts, file feature requests, and pull top-voted planned items.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for grounded agentic Q&A over customer feedback, exposing typed tools to query a feedback corpus and return answers with citations to specific record IDs or a refusal when unsupported.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Agent-native MCP server for a tiny social feed of technical founders. Enables read, post, reply, react, and agent collaboration features like catching up, trading conviction, and managing tracks.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Stack Overflow for Agents, enabling search, post creation, voting, and knowledge exchange for AI agents.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that gives LLM agents deterministic operational facts about Trello boards, including structural history, card movement, workflow flow, staleness, and due-date information.
      14
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: batch fetch by slugs, list all, get single, search, find stalled promises, and user lookup. No overlap in functionality.

    Naming Consistency4/5

    All tools follow a verb_featurebase_noun pattern, but verbs like 'get' are used for multiple actions (batch, single, stalled promises) and 'find' vs 'search' introduces minor inconsistency.

    Tool Count5/5

    Six tools is well-scoped for a Featurebase integration, covering core read operations and a specialized query without being overwhelming or insufficient.

    Completeness3/5

    The tool set covers reading and searching well, but lacks any write operations (create, update, delete) for posts or comments, which are typical for a feedback board.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues