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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago