Tasker MCP

Created By
dceluisa year ago
An MCP server for Android's Tasker automation app.
Overview

What is Tasker MCP?

Tasker MCP is a server designed for the Tasker automation app on Android, enabling users to automate tasks and integrate various tools seamlessly.

How to use Tasker MCP?

To use Tasker MCP, import the provided Tasker profile into your Tasker app, generate an API key, and run the server using the appropriate CLI binary for your device.

Key features of Tasker MCP?

  • Integration with Tasker for automation tasks
  • Support for multiple transport modes (SSE and stdio)
  • Customizable tool definitions through JSON files

Use cases of Tasker MCP?

  1. Automating notifications and alerts on Android devices.
  2. Integrating third-party tools with Tasker for enhanced functionality.
  3. Running custom scripts and commands through Tasker.

FAQ from Tasker MCP?

  • Can Tasker MCP work with any Android device?

Yes! As long as the device supports the Tasker app, Tasker MCP can be used.

  • Is there a cost to use Tasker MCP?

Tasker MCP is open-source and free to use under the MIT license.

  • How do I troubleshoot connection issues?

Ensure that the server is running and that the correct API key is being used in your Tasker profile.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dceluis
Star
2
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago