@Tailor MCP Server

The tailorctl command-line utility, with a focus on MCP (Model Context Protocol) server functionality. The @tailor mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

The npm package @tailor-platform/tailor-mcp is a tool for automatically installing the tailorctl command-line utility, with a focus on MCP (Model Context Protocol) server functionality.

Tailor Platform is a headless ERP platform that enables building composable applications:

• Automatically installs the appropriate tailorctl binary for your platform
• Supports all major platforms:
• macOS (x86_64, arm64)
• Linux (x86_64, arm64)
• Windows (x86_64, arm64)
• Provides easy access to MCP server functionality

Its toolset

Everything the assistant can do here goes through one of these:

• Low — code Development**: Build applications without extensive coding, with automatic GraphQL interface generation
• LLM-friendly — Create data models, business logic, and workflows without writing code, leveraging the power of large language models
• Enterprise-Ready — Build mission-critical core business applications that scale with your organization
• create_resource — Creates resources of various types
• update_resource — Updates resources of various types
• destroy_resource — Destroys resources of various types
• fetch_resource_by_trn — Fetches resources by TRN
• search_resource — Searches resources by workspace ID and resource type
• query_graphql — GraphQL Query tool
• graphql_sdl — Fetch SDL for GraphQL

Configuration

You will need one environment variable: TAILOR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as @tailor-platform/tailor-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. @Tailor's toolset — Low, LLM-friendly, Enterprise-Ready and 7 more — is a fair guide to whether it matches your workflow. It is maintained by tailor-platform; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against @Tailor's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch @Tailor.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the @tailor mcp server does with a few real requests.