Tui MCP Server

Tui MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. TOAST UI Utility: CodeSnippet.

What you get

You can also see the older versions of API page on the releases page.

What the assistant can call

Once Tui is connected, these are the calls the assistant has available:

• Bundle — Since v2.0, it does not provide bundle files. If you need a bundle file, you should make it yourself using the command npm run bundle
• Setup — Fork master branch into your personal repository. Clone it to local computer. Install node modules. Before starting development, you should check if
• Develop — Let's start development! Don't miss adding test cases and then make green rights

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

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. Tui's toolset — Bundle, Setup, Develop — is a fair guide to whether it matches your workflow. It is maintained by nhnent; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tui mcp server does with a few real requests.