Build a tool pack
In this page you build a tool pack whose MCP server gives agents one tool, load it into your own Jacker, and see an agent use it.
Before you begin
- Build the author kit. See The author kit.
- Start Jacker with plugins switched on. From the jacker repository, run:Without
JACKER_PLUGINS=1 pnpm desktop:dev
JACKER_PLUGINS=1, the Plugins page doesn’t appear. - Open a project. Tool packs work only in trusted projects: every project Jacker created, and imported projects you’ve confirmed.
Create the plugin
- Create a starter plugin. Replace
PUBLISHERwith your publisher name andNAMEwith the plugin’s name, both in lowercase letters, digits, and dashes:The folder containsjacker-plugin init tools ./NAME --id PUBLISHER.NAME
plugin.json,README.md, andserver/server.cjs, a small MCP server with one tool,echo. - Check it:The output ends with
jacker-plugin validate ./NAME
OK PUBLISHER.NAME 0.1.0, 3 files.
Load it into Jacker
- In Jacker, open Plugins in the rail.
- On the Installed tab, click Load local plugin… and choose the plugin folder.
The plugin appears with the labels Ready and Local, unverified.
Use the tool
- Start a chat in your project and ask the agent to use the echo tool, for example “Use the echo tool to repeat hello”.
- When Jacker asks whether the agent may use the tool, click Allow. To stop it asking again in this project, first select Don’t ask again for the tool.
The agent receives the tool’s answer. Its name in the run is plug_PUBLISHER_NAME_echo.
What’s next
- Replace
server/server.cjswith your own server. See Guidelines for MCP servers. - If your server needs a token or the network, declare it. See What a plugin’s programs can reach.
- When it works, see Package and publish.