FlowAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment (production, development) | production |
| LOG_LEVEL | No | Logging level (error, warn, info, debug) | info |
| FLOW_API_URL | Yes | The base URL of your FlowAPI instance, e.g., https://your-flowapi-instance.com/api | |
| MCP_SERVER_NAME | No | Name of the MCP server | flowapi-server |
| FLOW_API_SYS_KEY | Yes | The system key for authentication with FlowAPI | |
| MCP_SERVER_VERSION | No | Version of the MCP server | 1.0.0 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flowapi_health_checkB | Check FlowAPI system health and connectivity. Verifies system is operational. |
| flowapi_system_infoA | Get system information including configuration and connectivity status. |
| search_usersC | Search for users with optional filters. System-level operation for administrative purposes. |
| create_userB | Create a new user in the system. System-level operation for user management. |
| get_userA | Get user information by various identifiers. At least one identifier must be provided. |
| delete_userA | Delete a user by user ID. System-level administrative operation. |
| get_user_walletsC | Get wallet information for a user by various identifiers. System-level operation for wallet management. |
| list_external_workersB | List external workers with pagination. System-level operation for worker management. |
| create_external_workerC | Create a new external worker. System-level operation for worker management. |
| get_external_workerB | Get external worker details by ID. System-level operation. |
| update_external_workerC | Update external worker configuration. System-level operation. |
| delete_external_workerC | Delete an external worker. System-level administrative operation. |
| get_invited_walletsB | Get invited wallet addresses for a specific chain. System-level operation for invite management. |
| get_invited_wallets_by_tokenC | Get invited wallet addresses for a specific chain and token. System-level operation requiring authentication. |
| list_artsC | Get list of arts with optional parameters and filters. Works with sys_key authentication. |
| get_artA | Get art details by ID. System-level operation. |
| get_recommended_artsC | Get recommended arts for discovery. System-level operation. |
| list_art_collectionsC | List art collections with optional filters. System-level operation. |
| get_art_collectionB | Get art collection details by ID. System-level operation. |
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 19 tools
Most tools have distinct purposes, but there is slight overlap between health_check and system_info (both check system status) and between get_invited_wallets and get_invited_wallets_by_token (similar but differentiated by token parameter). Overall, descriptions are clear enough to avoid major confusion.
Tool names are inconsistent in prefix usage: some start with 'flowapi_' (e.g., flowapi_health_check), others do not (e.g., search_users). The pattern is mostly verb_noun but varies between 'search' and 'list' for similar operations. This mix reduces consistency.
With 19 tools covering multiple domains (users, workers, arts, collections, wallets), the count is appropriate for the server's scope. It is slightly on the higher side but still well-scoped without feeling bloated.
The tool set provides full CRUD for external workers but lacks update for users and delete for arts and collections. Also, arts and art collections are limited to read-only operations. There are notable gaps that agents may need to work around.