Featurebase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEATUREBASE_API_KEY | Yes | Your FeatureBase API key | |
| FEATUREBASE_ORG_URL | No | Your organization's FeatureBase URL (e.g., "https://feedback.spacelift.io"). Required only if using resolve_post_slug tool. | |
| FEATUREBASE_BASE_URL | No | Custom API base URL (defaults to "https://do.featurebase.app/v2") | https://do.featurebase.app/v2 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_postsC | List posts with optional filtering. Available fields: id, title, content, author, authorId, authorPicture, commentsAllowed, organization, upvotes, upvoted, postCategory(category,private,prefill,roles,hiddenFromRoles,id), postTags(name,color,private,id), postStatus(name,color,type,isDefault,id), date, lastModified, comments, isSubscribed, inReview, lastDraggedTimestamps |
| create_postC | Create a new post |
| update_postC | Update an existing post |
| delete_postC | Delete a post permanently |
| get_post_upvotersB | Get list of users who upvoted a post |
| add_upvoterC | Add an upvoter to a post |
| get_commentsC | Get comments for a post or changelog. Available fields: upvoted, downvoted, inReview, isSpam, pinned, emailSent, sendNotification, organization, submission, author, authorId, authorPicture, isPrivate, isDeleted, confidenceScore, content, upvotes, downvotes, score, parentComment, path, createdAt, updatedAt, id, replies(upvoted, downvoted, inReview, isSpam, pinned, emailSent, sendNotification, organization, submission, author, authorId, authorPicture, isPrivate, isDeleted, confidenceScore, content, upvotes, downvotes, score, parentComment, path, createdAt, updatedAt, id) |
| create_commentC | Create a new comment or reply |
| update_commentC | Update an existing comment |
| delete_commentA | Delete a comment (soft delete if has replies) |
| resolve_post_slugC | Convert a post slug to post ID and get post details |
| get_similar_submissionsC | Find posts similar to the given query text |
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 12 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as create_post vs. update_post, or get_comments vs. delete_comment, with no overlapping functionality that could cause confusion.
All tools follow a consistent verb_noun pattern (e.g., create_post, delete_comment, get_similar_submissions), using snake_case throughout without any deviations or mixed conventions.
With 12 tools, the server is well-scoped for a Featurebase domain, covering core CRUD operations for posts and comments, along with utility functions like upvoting and similarity search, without being overly sparse or bloated.
The tool set provides complete lifecycle coverage for posts and comments, including creation, retrieval, updating, deletion, and auxiliary actions like upvoting and similarity search, with no obvious gaps for the domain.