This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
This project is a read-only adaptation of Logiwa IO WMS MCP by cgtykctn. It builds on the original TypeScript server and Logiwa API integration, adding remote access over Streamable HTTP, Auth0 authorization, and Vercel deployment. The original public Git history and Apache 2.0 license are preserved.
The server exposes 18 read-only tools for products, inventory, orders, returns, warehouses, business partners, reports, and reference lookups. Each organization deploys its own instance with its own Auth0 tenant and Logiwa API token. Auth0 controls who can connect, and the server uses the organization's Logiwa token for data requests.
You need a Vercel account, access to an Auth0 tenant, and a Logiwa API token for the data you want to query.
Import into Vercel. Import this GitHub repository as a project and select Node.js 24.x. The repository provides the build settings. Choose a stable production hostname and use its HTTPS URL ending in /api/mcp as the MCP endpoint. The connector must be able to reach that hostname, so use the production domain without a Vercel sign-in wall.
Configure Auth0. Create an RS256 API with the exact MCP endpoint as its Identifier, with no trailing slash. Enable RBAC, Add Permissions in the Access Token, and Allow Offline Access. Enable Resource Parameter Compatibility Profile in the tenant's Advanced settings. Create the API permission read:logiwa, add it to a role such as Logiwa Reader, and assign that role to authorized users. For each connector you intend to use, register a public Native app with Authorization Code, PKCE (S256), Refresh Token, and token endpoint authentication set to None. Under API access policies, grant each app user-delegated access to read:logiwa and deny machine-to-machine access. Enable an appropriate user connection on each app and disable public sign-ups if using a private database connection. Use the callbacks below. Auth0 RBAC · Resource parameter setup
Set production variables and deploy. Set AUTH0_ISSUER_URL to your Auth0 issuer (for example, https://YOUR-TENANT.us.auth0.com/) and MCP_RESOURCE_URL to the exact MCP endpoint. Store LOGIWA_API_TOKEN as a production secret with the raw token value, without the Bearer prefix. Deploy or redeploy. Environment example
Connect and test. Add the custom connector with the MCP endpoint and the corresponding Auth0 Client ID. Leave the client secret blank. Sign in as an authorized user and ask the connector to show the first page of Logiwa inventory.
Client | Connector settings | Auth0 callback |
Sign in now → Use your own OAuth client. Use Streamable HTTP. |
| |
OAuth → User-Defined OAuth Client. Use token endpoint authentication None, data scope | Copy the exact redirect URI shown in the connector settings. When the stable callback is available, it is |
Related MCP server: Skulabs MCP Server
Grant or remove access by assigning or removing the Auth0 role. Set a short API access-token lifetime, such as 900 seconds, because previously issued tokens remain valid until they expire.
Rotate the Logiwa token by updating the Vercel production secret and redeploying.
Troubleshoot by checking /api/health for liveness. A 401 from /api/mcp without a token is expected. A 403 after sign-in can mean the token lacks the required scope or permission. Check the user's role and reconnect.
Run npm ci --ignore-scripts and npm test to build and verify the project locally.
This server cannot be deployed
Warehouse ops from Claude: orders, stock, forecasts, parcel rates, labels you buy in the console
Read and write Sage Intacct from Claude or ChatGPT. Write tools are flagged for approval.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Read-only Google Ads, GA4 and Search Console data for Claude, with no Google Cloud setup.
