tasker

The Tasker MCP server provides a bridge between Tasker automation tasks and MCP-enabled clients. It exposes a CLI-based MCP server that serves tool descriptions for Tasker tasks and allows you to invoke those tasks remotely via the MCP protocol. You typically run the server in one of two transports: SSE (server-sent events) or stdio, depending on how your MCP client communicates with the server. The server uses a pre-generated toolDescriptions.json to describe the available Tasker tools and their arguments, which Tasker-based clients can discover and call.

To use it, start the server with the required tool definitions and Tasker connection details, then point your MCP-enabled app to the running server. Your app can call tools like tasker_flash_text or other Tasker actions defined in the exported tool descriptions. The server supports standard MCP requests (e.g., tools/call) and passes arguments to Tasker via the Tasker API key and host/port configured in the command line flags.

Prerequisites:

• A machine with Go tooling if you plan to build the CLI server from source.
• Access to the Tasker project export that generates a toolDescriptions.json file.

Install and run steps:

1. Build the CLI server (example for ARM64):

• Install Go: sudo apt-get update && sudo apt-get install -y golang-go
• Navigate to the project folder and build: cd cli GOOS=linux GOARCH=arm64 go build -o dist/tasker-mcp-server-cli-aarch64 main.go

2. Prepare tool descriptions:

• Export your Tasker project to mcp_server.prj.xml, then generate toolDescriptions.json using the provided script, for example: cd utils npm install node xml-to-tools.js /path/to/your/exported/mcp_server.prj.xml > toolDescriptions.json

3. Run the MCP server:

• Ensure the generated toolDescriptions.json is accessible by the server and fill in the correct Tasker host and API key.
• Start the server using the command and arguments shown in the mcp_config example (or your customized paths): /home/luis/tasker-mcp/dist/tasker-mcp-server-cli-x86_64 --tools /home/luis/tasker-mcp/dist/toolDescriptions.json --tasker-host 192.168.1.123 --tasker-api-key tk_... --mode stdio

Notes and tips:

• The Tasker API key must be kept secret; rotate it periodically and avoid sharing it in public configs.
• If you switch transports (stdio vs sse), ensure your MCP client is configured to match the mode.
• The toolDescriptions.json must reflect the exact Tasker tools and arguments; after exporting, re-generate descriptions if you modify tasks.
• If you need to rebuild tool descriptions after changes in Tasker, re-export and re-run the xml-to-tools conversion.