Tools & skills
Give your agents tools and skills
Connect the systems your team uses through MCP, plugins and the tool marketplace, then write down how the work is done as skills. Agents, workflows and Evose AI use them within your permissions.
Connect once and every agent can use it
Three ways to connect
Point to an MCP server, turn an HTTP API into a plugin, or install a ready-made tool from the marketplace.
Skills are written-down know-how
Write reply guidelines, review standards or report formats as a SKILL.md with templates and scripts. Agents load it when the task calls for it, so prompts don't have to repeat it.
Controlled by workspace and account
Agents, workflows and Evose AI can call what you connect. Workspaces and authorization decide who can use it and whose account it runs as.
From connection to agent
Three steps to turn a system into a tool your agents can use.
- 01
Connect it
Enter an MCP server address, install from the marketplace, or describe an API and let AI draft a plugin. Its tools sync in once connected.
- 02
Test it
Run it once with a set of parameters and check the response. Plugins can stay in draft until they're right.
- 03
Hand it to an agent
Pick the tool in an agent or a workflow. Turn on all of its tools or only the few you need.
Write down how the work is done
A skill is a folder with a SKILL.md and the templates and scripts it needs. Agents load it when a task calls for it.
- Write it in chat or import itDescribe the problem it solves, when to use it and the rules it must follow, and AI drafts the skill. Existing skills import from a ZIP or a folder.
- Review changes file by fileEvery edit marks which files were added, modified or deleted, and opening one shows the changed lines.
- Compare before you publishLoad the old version and the new draft into the same agent, run both on the same input and compare side by side.
Ways to use it
Connect an internal system
Turn your order system's API into a plugin with only the calls you need.
Prompt “Turn our order system's API into a plugin with just the subscription and invoice lookups. Leave out the plan change and refund calls until I've reviewed them.”
Write reply guidelines
Turn the support team's experience into a skill every support agent follows.
Prompt “Write the support team's refund reply guidelines as a skill with our three reply templates. Refunds over $500 always go to a person, so put that in the rules. Compare it with the old version before publishing.”
Everyone on their own account
Personal tools like calendar and email are authorized per person.
Prompt “Install the calendar tool from the marketplace in personal account mode so everyone authorizes with their own account. Don't share my account with the whole team.”
What you can connect
Tools act in your systems. Skills tell agents how that kind of work should be done.
MCP
Connect remote servers over Streamable HTTP or SSE. Their tools sync in, and you can test each one.
Plugins
Define any HTTP API as a tool with shared parameters and headers. Plugins have drafts and published versions.
Marketplace tools
Install ready-made toolkits and connect them with OAuth, an API key or an organization credential. No API work needed.
Skills
A SKILL.md plus templates and scripts. Skills are versioned and can be taken online or offline. Organizations can send skills to chosen workspaces.
Built-in tools
Web search, web page generation and a code sandbox come from your organization, and admins choose the search provider.
Where they're used
Agents, Orchestrated Agents, workflow nodes and Evose AI can all call them. Each tool lists the apps that use it.
You decide who uses what, and with whose account
Once a tool is connected, you manage its authorization, credentials and scope separately.
- Shared or personal accountsA shared account is authorized at install and used by everyone. A personal account is authorized on first use, and each run uses the account of the person who called it.
- Credentials managed centrallyAdmins keep organization credentials and choose which workspaces can use them. Members pick one when adding a tool and never handle the secret.
- See who uses whatEvery tool and skill lists the agents, workflows and projects that use it. Take skills you no longer need offline at any time.
Questions
Connect the systems your team already uses
Start with one tool and hand it to one agent.