fruits-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRODUCT_FRUITS_API_TOKEN | Yes | Your Product Fruits API token |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_articlesA | List all knowledge base articles. Optionally filter by category correlation ID. |
| import_articlesA | Import or update knowledge base articles (max 50 per request, up to 20 languages each). Each article requires 'correlationId' and 'contents'. Each content entry requires 'lang', 'title', and 'content'. Optional fields: 'format' (markdown|html), 'publishStatus' (published|draft), 'categoryCorrelationId', 'isPrivate', 'ignoreImportErrors'. |
| delete_articleB | Delete an entire article (all languages) by its correlation ID. |
| delete_article_languageA | Delete all content versions for a specific language from an article. |
| delete_article_content_versionC | Delete a specific content version from an article language. |
| list_categoriesA | Get all categories from the knowledge base. |
| get_categoryC | Retrieve a specific category by its correlation ID. |
| import_categoriesA | Import or update knowledge base categories. Creates if not found, updates if existing. Each category requires 'correlationId' and 'name'. Optional: 'parentCorrelationId', 'isPrivate', 'order'. |
| update_categoryC | Update an existing category by its correlation ID. |
| delete_categoryB | Delete a category by its correlation ID. |
| upload_imageA | Upload an image to use in knowledge base articles. Provide the image as a Base64-encoded string along with its MIME type (e.g. 'image/png') and filename (e.g. 'cover.png'). |
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 11 tools
The tools are mostly distinct, with clear descriptions for each. However, the multiple delete tools for articles (delete_article, delete_article_content_version, delete_article_language) could cause confusion at first glance, though their descriptions clarify the scope.
All tools follow a consistent verb_noun pattern in snake_case, such as delete_article, import_categories, list_categories. The naming is predictable and uniform across the set.
With 11 tools, the set is well-scoped for a knowledge base management system covering articles, categories, and images. Each tool serves a distinct purpose and the count is appropriate.
The set covers basic operations but has notable gaps: no get_article or update_article tool (only bulk import), and image management lacks delete/update capabilities. This may force workarounds.