lua mcp lists the MCP servers attached to the agent and turns the ones from your project on or off. An active server’s tools are available to the model; a deactivated server’s tools are not.
Verified against lua-cli 3.33.0.
Synopsis
Description
With no action the command opens a menu covering every action. Every action runs against production.list groups the agent’s servers by who manages them, in this order:
Each row shows 🟢 when the server is active or ⚪ when it isn’t, then the label saying who manages it, the transport, the URL, and the ID. A custom server shows the name it was given and its
Host: instead of a URL, because Lua never shows a custom server’s address. Groups with no servers are left out, and a closing line reminds you that activate, deactivate, and delete change only servers from your project. Earlier lua-cli versions listed active servers first, then inactive ones, with no groups.
activate and deactivate change whether the server’s tools are offered to the model. Both are no-ops with exit 0 when the server is already in the requested state.
delete removes the server from the agent. The non-interactive form has no confirmation prompt; only the menu asks. To get the server back, push it again.
activate, deactivate, and delete change only servers from your project. On any other server they stop with exit 2 before calling the platform, and say where to manage it: lua integrations mcp (or lua integrations disconnect, for delete) for an integration server, the Tools page or the admin dashboard for a custom server. The menu offers only servers from your project. Earlier lua-cli versions let these actions change integration servers too.
The server name can be given as the positional argument or with --server-name; matching is case-insensitive, and a custom server also matches the name list shows for it. Every form needs a project directory and a credential.
MCP servers are not versioned and are not a lua deploy type. A server goes live when it is active: define it with LuaMCPServer, register it on the LuaAgent, and push it with lua push mcp --name <name>. That push asks whether to activate the server straight away (default No); --auto-deploy activates without asking, and --force alone skips the question and leaves the server inactive. lua push all pushes servers without activating them and ignores --auto-deploy, so follow it with lua mcp activate <name>.
Arguments
Accepted spellings:
ls, l → list; on, enable → activate; off, disable → deactivate; rm, remove, del → delete.
Options
Examples
List the servers, grouped by who manages them.Output
Output
lua integrations mcp.
Output
Exit codes
The full table is in Errors and exit codes.
See also
LuaMCPServer— transport, URL, and headers- Use an MCP server
lua push—lua push mcpand--auto-deploylua integrations—lua integrations mcpfor integration-created servers- Add a custom MCP server — servers added by URL from the Tools page or the admin dashboard
lua logs—--type mcp