Signal Tools
Read-only access to a locally linked Signal account's chats and contacts for coding agents
- Pricing
- Open source
- Platforms
- CLI
- Runs
- Locally
- Version
- 0.7.0
- Listing updated
- today
Similar MCP servers
About Signal Tools
Signal Tools is an open-source MCP server for communication. It runs locally on your machine and is started by your AI client.
Signal Tools reads from a local mirror of a Signal account rather than a live connection. The account tool reports, for each label, whether it is linked, the sync service's state, the last receive and the next step, using local state only: no daemon, no network and no number, account ID or key in the result. The chat tool reads the same local mirror and has four methods: list finds chats, view reads one chat's messages, search finds messages by words, and around reads the messages next to a given one. History begins when the device was linked.
Results are shaped for safety. Times are local with their offset, a chat is always referred to by its ID, long results are paged with next, and the README stresses that everything returned is data written by other people. A contacts toolset lists local contacts, and the overview also mentions received files and sends, with a skill for each toolset.
It needs Node.js 24 or later. Delivery matches its sibling packages: plugins for OpenCode, Claude Code, Codex, Grok Build, Antigravity and Hermes, or an npm MCP server, installed from a release tag or commit, with an optional read-only flag.
Install
Run in a terminal
claude mcp add signal-tools -- npx -y @craftsamo/signal-toolsAdd to claude_desktop_config.json
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"signal-tools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (3)
Taken from the project documentation; the running server may differ.
- signal_account_read
- Show each label's link status, sync state, last receive and next step.
- signal_chat_read
- List chats, view messages, search by words or read messages around one.
- signal_contact_read
- List local contacts.
What it does
- Account health
- Shows whether each label is linked and the sync state, with no secrets in the output.
- Chat reading
- list, view, search and around methods over the local mirror.
- Contacts lookup
- List local contacts.
- Paged results
- Long results continue with a next cursor.
- Untrusted-data framing
- Message content is flagged as data written by others.
- Read-only flag
- Available to disable sends.
Good for
- Search past Signal messages for a detail
- Read the messages around a quoted line
- Check whether a linked device is syncing
- Find a contact by name from an agent
Pricing
Open source
Free npm package.
Signal Tools FAQ
Does it contact Signal's servers?
The account and chat tools read the local mirror only, with no daemon and no network.
How far back does history go?
From when the device was linked.
What does it need?
Node.js 24 or later and a linked Signal device.
How does it show chats?
Always by chat ID, with local times and paged results.
Is Signal Tools free?
Yes. Signal Tools is open source, so you can use and self-host it for free.
How do I add Signal Tools to Claude Code?
Run this command in your terminal: claude mcp add signal-tools -- npx -y @craftsamo/signal-tools
What are the best alternatives to Signal Tools?
The closest alternatives to Signal Tools are TrendRadar, Getmitra, Discord, Zoom and Email Spam Tester.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

