When you ask your AI assistant to "check the weather," "find that PDF from last month," or "turn off the living room lights," it needs actual capabilities to make those things happen. That's why Meggy ships with 110+ tools organized across 24 providers — not just text generation, but real actions that interact with your files, your network, your devices, and the web.
Every tool invocation passes through a trust-based approval system before execution. You stay in control of what happens on your machine.
Tools are organized into logical provider groups:
| Provider | Tools | Examples |
|---|---|---|
| Filesystem | Read, write, list, move, delete, glob, search files | read_file, write_file, list_directory, glob_search |
| Workspace | Project-level operations and code analysis | workspace_summary, find_references |
| Terminal | Execute shell commands, stream output | run_command, run_background_command |
| Browser | Headless Chromium navigation, screenshots, DOM interaction | navigate, screenshot, click_element, fill_input |
| Web Search | Search the web via configurable providers | web_search, fetch_url |
| Web Fetch | Retrieve and parse web page content | fetch_page, extract_content |
| Git | Stage, commit, diff, log, branch operations | git_status, git_diff, git_commit |
| Scheduler | Create cron and one-shot scheduled tasks | schedule_task, list_schedules, delete_schedule |
| Vault | Document ingestion and semantic search | vault_search, vault_ingest, vault_list |
| Memory | Store and retrieve facts and context | remember_fact, recall_facts, forget_fact |
| Smart Devices | Discover and control IoT devices on your network | scan_devices, control_device, wake_on_lan |
| Creative | Image generation via multiple providers | generate_image |
| Presentations | Create and export slide decks | create_presentation, export_slides |
| Network | DNS lookup, HTTP requests, port scanning | dns_lookup, http_request |
| System Monitor | CPU, memory, disk, and process monitoring | system_info, process_list |
| Outbound Messaging | Send messages across connected channels | send_message, send_channel_message |
| People | Manage the People Knowledge Graph | add_person, find_person, update_person |
| Converter | Unit and format conversion utilities | convert_units, convert_currency |
| Date & Time | Timezone, calendar, and scheduling utilities | current_time, time_difference |
| Generator | Random data, UUIDs, passwords | generate_uuid, random_password |
| Questions | Cross-channel interactive question engine | ask_user, ask_channel |
| Admin | Administrative and configuration operations | get_settings, update_config |
| Weather | Current conditions and forecasts | get_weather, weather_forecast |
| Clipboard | Read and write system clipboard | clipboard_read, clipboard_write |
Having 110+ tools is powerful — but you don't want your AI deleting files without asking. That's why Meggy implements a three-tier trust model:
| Tier | Who | Permissions |
|---|---|---|
| Owner | The primary user | Full access — can approve dangerous tools |
| Trusted | Vetted agents and channels | Pre-approved for safe/moderate tools |
| Unknown | New or unverified agents | Requires explicit approval for every tool call |
Every tool is classified into one of three risk levels:
The ToolApprovalManager supports multiple approval modes:
Beyond built-in tools, Meggy supports loading external tools via the Model Context Protocol (MCP). MCP servers expose tools, resources, and prompts that the AI can discover and invoke — extending Meggy's capabilities without modifying its core. This means the tool ecosystem grows with you.