home / skills / plurigrid / asi / signal-messaging

signal-messaging skill

This skill helps you interact with Signal via MCP by sending, reading, and automating Signal conversations and attachments.

npx playbooks add skill plurigrid/asi --skill signal-messaging

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.4 KB

---
name: signal-messaging
description: Send and receive Signal messages via MCP. Use this skill when you need to interact with Signal messenger - sending messages, reading conversations, or automating Signal-based workflows.
compatibility: Requires signal-mcp server built with Cargo. Signal account must be registered.
---

# Signal Messaging via MCP

Interact with Signal messenger through the local MCP server.

## Setup

The Signal MCP server is configured in `~/.mcp.json`:

```json
{
  "signal": {
    "command": "cargo",
    "args": ["run", "--release", "--example", "signal-server-stdio"],
    "cwd": "/Users/alice/signal-mcp",
    "env": {
      "RUST_LOG": "signal_mcp=info"
    }
  }
}
```

## Prerequisites

1. Clone and build the signal-mcp server:
   ```bash
   cd /Users/alice/signal-mcp
   cargo build --release --example signal-server-stdio
   ```

2. Register/link your Signal account with the server

## Usage

Use `read_mcp_resource` to interact with Signal:

```json
{"server": "signal", "uri": "signal://..."}
```

## Capabilities

- Send messages to contacts or groups
- Read incoming messages
- List conversations
- Handle attachments

## Troubleshooting

- Ensure the server starts: `cargo run --release --example signal-server-stdio`
- Check logs: `RUST_LOG=signal_mcp=debug`
- Verify Signal account is registered/linked
- Restart Amp after config changes

Overview

This skill lets you send and receive Signal messages through a local MCP (Message Connector Process) server. Use it to automate Signal-based workflows, read conversations, deliver attachments, and manage group or contact messaging. It integrates with a locally running signal MCP process and exposes actions via MCP resource calls.

How this skill works

The skill communicates with a configured signal MCP server process running on the local machine. It issues MCP resource reads and writes (for example using read_mcp_resource with signal:// URIs) to list conversations, fetch messages, and send messages or attachments. The MCP server acts as the bridge to the Signal client account you have linked and must be started and registered beforehand.

When to use it

Automating notifications or alerts to individuals or groups on Signal.
Reading incoming Signal messages for bots, monitoring, or analytics.
Sending attachments (images, documents) programmatically via Signal.
Building integrations that require two-way messaging with Signal users.
Replacing manual messaging flows with reproducible, scriptable operations.

Best practices

Run and test the local signal MCP server before invoking the skill; confirm the account is registered and linked.
Use read_mcp_resource with explicit signal:// URIs to target conversations or actions.
Keep logs enabled at debug or info level when developing to capture protocol exchanges and errors.
Handle message and attachment size limits and retries gracefully in your automation.
Restart the host application after changing MCP configuration to ensure new settings load.

Example use cases

Send incident alerts to a Signal group when monitoring detects a problem.
Fetch recent conversation history to generate a summary or transcript for compliance.
Automate delivery of daily reports or receipts as Signal attachments to customers.
Build a chatbot that responds to incoming Signal messages and triggers backend workflows.

FAQ

What must be running locally for this skill to work?

A local signal MCP server process must be built, started, and linked to a Signal account. The skill communicates with that MCP server.

How do I send or read messages?

Use MCP resource calls such as read_mcp_resource with a signal:// URI to list conversations, read messages, or send messages and attachments.

How do I troubleshoot connectivity or failures?

Ensure the MCP server process is running, check logs with RUST_LOG set to debug or info, verify the account is registered, and restart the host app after config changes.