MCP servers, skills, and plugins
Connect MCP servers and install or create skills and plugins.
Connect an MCP server
Open Settings → Extend → MCP servers. Search names, descriptions, publishers, or categories. Use the sliders button for category, installed, and sort filters. Details opens an in-app description. Connect starts provider authentication for supported servers. Complete consent in your browser.
Custom servers
Use Custom to enter a server URL or advanced local command configuration. Providers can require account access or a registered OAuth client. A directory entry does not guarantee access. Check the provider’s own instructions if connection fails. Test the connection from Details.
Install a skill or plugin
Choose Skills or Plugins, then Install. Enter a GitHub repository, local folder, or archive. Review the package and selected skills before installation. Prefer publisher-owned repositories, inspect instructions and code, and pin a reviewed revision where possible. Installed code and tools can access resources you allow.
Create from chat
Choose Create from chat or ask a task to make a workflow into a skill or plugin. Describe when it should run, its inputs, and its expected output. Review the result before use. Managed packages live under ~/.muniment. Open folder reveals their files.
Use extensions for one turn
Open the composer’s ellipsis menu. Enable the MCP servers needed for this turn. Choose a skill or plugin to insert its /command into the message. With assistance on, the decision model named in the composer picks MCP servers and skills, and you can turn it off for one message. Selections reset after submission and remain with an unsent task draft.
How chats use tools
The model calls your MCP servers through codemode, a short script that calls tools and returns only what the reply needs. Each server keeps its own name, and the reply labels its calls, such as MCP Context7. Enabled skills are listed by name and description, and the model reads a skill when a task needs it.