MCP Inflow Ingredients
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFLOW_API_KEY | Yes | Your Inflow API key | |
| INFLOW_API_URL | No | API base URL | https://cloudapi.inflowinventory.com |
| INFLOW_COMPANY_ID | Yes | Your Inflow company ID | |
| INFLOW_API_VERSION | No | API version | 2025-06-24 |
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_ingredientsC | List all ingredients/products in Inflow inventory with optional filters |
| get_ingredientC | Get detailed information about a specific ingredient/product |
| get_inventory_summaryC | Get inventory summary for a product including quantities on hand, available, reserved, etc. |
| search_ingredientsC | Search for ingredients using full-text search across name, description, SKU, and barcode |
| create_ingredientC | Create a new ingredient/product in Inflow inventory |
| update_ingredientC | Update an existing ingredient/product in Inflow inventory |
| create_stock_adjustmentC | Create a stock adjustment to modify inventory quantities for one or more products |
| list_stock_adjustmentsC | List stock adjustments with optional filters |
| get_stock_adjustmentC | Get details of a specific stock adjustment |
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 9 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, create_ingredient, get_ingredient, update_ingredient, and list_ingredients each handle different CRUD operations for ingredients, while stock adjustment tools focus on inventory modifications. The separation between ingredient management and stock adjustments is well-defined, preventing misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_ingredient, get_inventory_summary, and list_stock_adjustments. This uniformity makes the tools predictable and easy to understand, with no deviations in naming conventions across the set.
With 9 tools, the count is well-scoped for inventory and ingredient management. Each tool serves a specific function, such as CRUD operations for ingredients and stock adjustments, without redundancy. This number is appropriate for the domain, providing comprehensive coverage without being overwhelming.
The tool set offers strong coverage for ingredient and inventory management, including create, read, update, list, and search operations, as well as stock adjustments. A minor gap exists in the lack of an update_stock_adjustment tool, which could limit flexibility in modifying adjustments, but agents can work around this by creating new adjustments.