LabscoMCP early access ↗
tulipMCP SERVER · OFFICIAL PROJECT

Tulip MCP Server

Read and write a Tulip manufacturing workspace — tables, machines, stations, apps — from an MCP client.

by tulip ↗ERP & Vertical Business Systems✓ Official

LABSCO SUMMARY

The Tulip API in a conversation, read-only until you choose otherwise.

A default launch switches on only the read-only tools. Everything that creates, changes, archives or deletes comes on only when you add its category to ENABLED_TOOLS, and the scopes on your Service Account are the boundary that actually holds.

What it is

A server for one Tulip instance that puts the Tulip API in front of an MCP client. It runs from npx against a file holding your instance URL and API credentials.

What you get

  • Tools grouped by what they touch: tables, machines, users, apps, interfaces, stations and station groups
  • A tool set you widen yourself with ENABLED_TOOLS — by tool name, by security category, or by resource type
  • Access through a Tulip Service Account, so the key carries only the scopes you grant it

Requirements

Node.js, and a .env file, in any folder, holding TULIP_API_KEY, TULIP_API_SECRET and TULIP_BASE_URL. TULIP_WORKSPACE_ID applies only to an Account API key — a Workspace API key leaves it blank.

Setup effort

One command plus a key — npx @tulip/mcp-server, then supply credentials