Fishbowl MCP Server

What is Fishbowl MCP Server?

A middleware server that provides a RESTful API to integrate with Fishbowl Inventory software. It handles authentication, token management, and proxies all requests to the Fishbowl API, enabling simplified access to Fishbowl functionality.

How to use Fishbowl MCP Server?

Clone the repository, install dependencies (npm install), configure a .env file with Fishbowl credentials and API URL, then start with npm run dev. For production deployment, follow the Railway instructions: install the Railway CLI, login, set environment variables (e.g., FISHBOWL_API_URL, FISHBOWL_USERNAME, FISHBOWL_PASSWORD), and deploy with railway up.

Key features of Fishbowl MCP Server

• Automatic authentication with Fishbowl API
• Simplified API access to Fishbowl functionality
• Support for parts, inventory, purchase orders, manufacture orders
• Memo management for purchase and manufacture orders
• Endpoints for vendors, units of measure, users, and products

Use cases of Fishbowl MCP Server

• Search and update part inventory programmatically
• Create, issue, and void purchase orders via API
• Manage manufacture orders from creation to closure
• Add, update, and delete memos on orders
• List vendors, UOMs, or users for integration workflows

FAQ from Fishbowl MCP Server

What are the prerequisites?

Node.js 18 or higher and a Fishbowl Inventory instance with API access and valid credentials.

How does the server handle authentication?

It automatically authenticates with the Fishbowl API using credentials stored in environment variables. Exposed endpoints include /api/login and /api/logout.

Where should I store Fishbowl credentials?

Store credentials securely in a .env file using environment variables (FISHBOWL_USERNAME, FISHBOWL_PASSWORD, etc.). Never hardcode them.

Can I deploy Fishbowl MCP Server to Railway?

Yes. Detailed steps are provided: install the Railway CLI, set environment variables, and run railway up.

What API endpoints are available?

Endpoints cover parts and inventory, purchase orders, manufacture orders, memos (for POs and MOs), products, UOMs, vendors, users, and a health check (/api/health). A full list is in the README.