@kjadeja/open-featurebase-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_featurebase_postsB | List posts on the configured Featurebase feedback board. |
| get_featurebase_postB | Get a single post by slug, optionally with full comment thread. |
| get_featurebase_postsA | Batch-fetch multiple posts by slug array. |
| search_featurebase_postsA | Search posts by keyword over title + body. |
| get_featurebase_stats | Board-wide statistics and aggregates. |
| get_featurebase_stalled_promisesC | Find posts where admin replied, customer spoke last, admin silent for N+ days. |
| find_featurebase_userB | Look up user IDs by partial name match. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
Six tools is well-scoped for a Featurebase integration, covering core read operations and a specialized query without being overwhelming or insufficient.
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.