Smoke Signal

io.github.smoke-signal-appPublished by GitHub account smoke-signal-appv0.4.2Updated Oct 24, 2026

Phone notifications and phone-answered questions for AI agents: notify and decision-request tools.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that lets an AI agent send notifications to the user's phone and ask questions the user answers from the phone.

What you can do
  • Send phone notifications from the agent to the user.
  • Pose decision requests that the user answers on their phone.
  • The manifest lists no individual tools, so the exact tool set is not documented here.
When to use it
Useful when an agent runs long or unattended tasks and the user wants to be alerted on their phone or approve a choice remotely instead of watching the session.
Requirements
Runs as a local process on the user's machine over stdio, distributed as an .mcpb desktop bundle; desktop only, not web-executable. No authentication, environment variables or headers are declared.
Before you install
It pushes messages to the user's phone and relays their answers back to the agent, so notification content and replies leave the local machine. No credentials are declared, but the phone-side setup is not described in the supplied material.

Installation

In SourceWeft

  1. Open Smoke Signal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.