Plugins
Plugins bring outside capabilities in — a local script, or an MCP server that already exists. Once installed, a plugin is a tool for the agent and for workflows, standing in the same row as everything built in.
Two ways to write one
01
A local script
One entry file plus a manifest, with tool inputs and outputs described in JSON Schema. Pure-computation tools need no permissions at all.
02
Wrap an existing MCP server
More and more platforms ship an MCP server themselves. In that case the plugin contains no code — it just declares which service to connect to, and the tool list comes from the other side.
Permissions are granted one by one
The manifest declares what it wants and you approve each item at install time; credentials are injected into that one connection and cannot reach the app's other secrets.
Official examples
These live in the repository — copy one and start from there.
Baidu Netdisk
Local scriptdev.mosael.baidu-pan · v0.3.1
Move files between Baidu Netdisk and the asset library. To pull: find an fs_id with pan_list or pan_search, then bring it in with pan_import. To push: use pan_upload to save something from the asset library to the netdisk (pass an asset_id and a target path).
network:baidu-panDetailsMCP Example
MCP serverdev.mosael.mcp-everything · v0.1.1
An example of wiring an existing MCP server up as an Mosael plugin. The tool list comes from the server itself, not from this file.
process:spawnDetailsText Toolkit
Local scriptdev.mosael.text-toolkit · v0.1.1
Small text utilities: count words, pull out hashtags, draft title candidates. All local, no permissions needed.
No permissionsDetailsTikHub
MCP serverdev.mosael.tikhub · v1.0.1
Read public data from Douyin / TikTok / Xiaohongshu / Bilibili / Kuaishou and other platforms: post details, creator profiles and their posts, keyword search, trending charts. For topic research, studying comparable accounts, and finding footage ideas.
network:tikhubDetails