Bar Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAR_ASSISTANT_TOKEN | Yes | Your personal access token generated from Bar Assistant profile settings | |
| BAR_ASSISTANT_BAR_ID | No | The ID of your bar (optional - if not set, can be provided as parameter to tools or discovered using list_bars tool) | |
| BAR_ASSISTANT_API_URL | Yes | Your Bar Assistant instance URL + the API path (e.g., http://localhost:8000/api or https://bar.example.com/bar/api) |
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_barsB | List all bars you have access to and get their IDs |
| get_shelf_ingredientsB | Get all ingredients currently on your bar shelf with detailed information |
| get_shelf_cocktailsB | Get all cocktails you can make with ingredients on your bar shelf |
| add_ingredients_to_shelfC | Add ingredients to your bar shelf by their IDs |
| remove_ingredients_from_shelfC | Remove ingredients from your bar shelf by their IDs |
| search_ingredientsC | Search for ingredients by name to find their IDs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Bar Shelf Ingredients | List of all ingredients currently on your bar shelf |
| Bar Shelf Cocktails | Cocktails you can make with ingredients on your bar shelf |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: managing shelf ingredients (add/remove/get), searching for ingredients, listing bars, and getting cocktails from the shelf. The actions and targets are well-defined, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case (e.g., add_ingredients_to_shelf, get_shelf_cocktails). The naming is predictable and readable throughout the set, with no deviations in style.
With 6 tools, this server is well-scoped for a bar assistant domain. Each tool earns its place by covering core operations like ingredient management, cocktail discovery, and bar listing, without being too sparse or bloated.
The tool set covers key workflows: CRUD for shelf ingredients (add, remove, get), ingredient search, bar listing, and cocktail generation. A minor gap is the lack of tools for directly managing cocktails or bars (e.g., create/delete bars), but agents can work around this with the provided operations.