GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Signal Tools
Overview
Description from the maker (original English)
Signal tools for coding agents: chats, messages, contacts, received files and sends.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Run this in your terminal
claude mcp add signal-tools -- npx -y @craftsamo/signal-toolsOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"signal-tools": {
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"signal-tools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@craftsamo/signal-tools"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account craft-agent, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 4926 servers in this category
- Published to the registry more recently than 98% of the other 4926 servers in this category
- Basic checks equal to or better than 100% of the other 4926 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Signal Tools safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
signal-tools
Signal tools for coding agents: chats, messages, contacts, received files and sends.
| Harness | Delivery | Pinned by |
|---|---|---|
| OpenCode V2 | native plugin (npm package, with skills) | the version in the package |
| OpenCode V1 | native plugin (npm package, no skills) | the version in the package |
| Claude Code | plugin: MCP server and skills | the release tag, as the ref |
| Codex | plugin: MCP server and skills | the release tag, as the ref |
| Grok Build | plugin: MCP server and skills | the release tag, as @ref |
| Antigravity | plugin: MCP server and skills | the release tag's tree URL |
| Hermes Agent | native plugin (Python, calls the command line) | the release commit, as the SHA |
| other MCP host | MCP server from npm | the version in the package |
The tools need Node.js 24 or later. docs/conventions.md describes how the tools are named and how they behave.
Install
Install from a release, never from the default branch: a release is a tag whose commit carries the built dist/, and the default branch does not. In the commands below, is a release's version (1.2.3) and is the commit its tag names:
gh api repos/craft-agent/signal-tools/commits/v<version> --jq .shaOpenCode
OpenCode V2 takes the package and its options in opencode.json:
{"plugins": [{ "package": "@craftsamo/signal-tools@ ", "options": { "read_only": false } }], "permissions": [{ "action": "signal_*", "resource": "*", "effect": "ask" }] }
OpenCode V1 takes the package as a string, or as a pair with its options:
{"plugin": [["@craftsamo/signal-tools@ ", { "read_only": false }]], "permission": { "signal_*": "ask" } }
OpenCode allows any action no rule names, so the plugin's request is granted silently unless a rule says ask. Read tools never ask, so the signal_* glob is safe.
V1 registers no skills. Unpack the package and copy its skills/* folders into ~/.config/opencode/skills/:
npm pack @craftsamo/signal-tools@<version>tar -xzf craftsamo-signal-tools- .tgz mkdir -p ~/.config/opencode/skills cp -r package/skills/* ~/.config/opencode/skills/ rm -rf package craftsamo-signal-tools- .tgz
Claude Code
claude plugin marketplace add craft-agent/signal-tools#v<version>claude plugin install signal-tools@craft-agent
Codex
codex plugin marketplace add craft-agent/signal-tools --ref v<version>codex plugin add signal-tools@craft-agent
Codex turns - into _ in server names, so it shows the tools as mcp__signal_tools__signal_*. It starts the MCP server in the plugin's install directory, which is never the caller's working tree.
Grok Build
grok plugin install craft-agent/signal-tools@v<version> --trustGrok starts the MCP server in the session's working directory.
Antigravity
Install from the tree of the release tag, never from the default branch, which has no built dist/; Antigravity clones the tag into ~/.gemini/config/plugins/signal-tools.
agy plugin install https://github.com/craft-agent/signal-tools/tree/v<version>Hermes Agent
Hermes installs a commit, not a tag, and the plugin installs disabled:
hermes plugins install craft-agent/signal-tools --ref <sha>hermes plugins enable signal-tools
If a Hermes gateway is already running, restart it (hermes gateway restart) to load the plugin.
Any other MCP host
Add the server to the host's MCP configuration. Flags go in args:
{"mcpServers": { "signal-tools": { "command": "npx", "args": ["-y", "@craftsamo/signal-tools@ ", "--read-only"] } } }
Tools and skills
Each toolset comes with a skill that tells an agent how to use its tools.
Account (account)
| Tool | What it does | Class |
|---|---|---|
signal_account_read | each label: linked or not, the sync service's state, the last receive and next step | read |
It reads local state only: no daemon, no network, and no number, account id or key in its result. The skill is signal-account, shown as signal-tools:signal-account in Claude Code and signal-tools:account in Hermes.
Chats (chats)
| Tool | What it does | Class |
|---|---|---|
signal_chat_read | by method: list finds chats, view reads one chat's messages, search finds messages by words, around reads the messages next to a message | read |
It reads the account's local mirror only: no daemon, no network, and no number of the account's own, attachment id or key in its result. History starts when the device was linked. Times are local with their offset, a chat is always its id, a long result is paged with next, and everything it returns is data written by other people. The skill is signal-chats, shown as signal-tools:signal-chats in Claude Code and signal-tools:chats in Hermes.
Contacts (contacts)
| Tool | What it does | Class |
|---|---|---|
signal_contact_read | lists local contacts or checks up to three numbers with Signal | read |
Listing needs no daemon; checking numbers needs the running sync service. Neither writes the mirror. The skill is signal-contacts, shown as signal-tools:signal-contacts in Claude Code and signal-tools:contacts in Hermes.
Files (files)
| Tool | What it does | Class |
|---|---|---|
signal_file_save | saves one message's files, and unpacks its archives when asked for | add |
signal_file_send | sends 1 to 10 files (100 MiB together), with a caption, to a chat | add |
The toolset is off by default: it writes to disk, opens archives and sends files. Turn it on with toolsets or tools. Files are sent only from the working directory (not when that is the home directory or a file system root) and the directories the send_dirs setting names; keys, secrets, programs and installers are refused, archives are checked entry by entry, and a file's sha256 can be given to be sure the file sent is the one approved. Sending needs the sync service running. Received files go to the download_dir setting, in a folder per message, private to the user (mode 700 and 600) and never executable; nothing is overwritten. Programs and installers are never saved, and an archive (zip, tar, gzipped tar) is saved only after its contents pass inspection, then listed; unpack: true unpacks it into .unpacked/ beside it. A view-once message's files are not saved. On macOS every saved file carries the quarantine flag. Saving needs no daemon. The skill is signal-files, shown as signal-tools:signal-files in Claude Code and signal-tools:files in Hermes.
Sends (sends)
| Tool | What it does | Class |
|---|---|---|
signal_message_send | sends one text of at most 4,000 characters to a chat, optionally quoting a message | add |
A chat is always its id; the user's own account id is Note to Self, and a group the user left is refused. A result means Signal accepted the message, with reached and not_reached for a group; any other failure after the request went out is uncertain: check the phone before sending again. The message is recorded in the mirror, and a record that fails is listed under errors without undoing the send. It needs the running sync service. The skill is signal-sends, shown as signal-tools:signal-sends in Claude Code and signal-tools:sends in Hermes.
Actions (actions)
| Tool | What it does | Class |
|---|---|---|
signal_message_edit | replaces the text of one of the user's own messages | overwrite |
signal_message_delete | deletes one of the user's own messages for everyone; it cannot be undone | administrative |
signal_message_react | sets, replaces or removes the user's emoji reaction on a message | overwrite |
The toolset is off by default: the actions change what others have already read. Turn it on with toolsets or tools. Editing and deleting take only the user's own messages, within 24 hours of sending, and a message is edited at most 10 times; only a text message can be edited. A reaction goes to any message, one per person, so a new one replaces the user's earlier one. Outcomes follow the sends': a result means Signal accepted it, with reached and not_reached for a group, and any other failure after the request went out is uncertain: check the phone before repeating it. Each is recorded in the mirror as the sync service would record it from another device, and a record that fails is listed under errors. No tool sends read receipts or typing indicators. It needs the running sync service. The skill is signal-actions, shown as signal-tools:signal-actions in Claude Code and signal-tools:actions in Hermes.
Adding a tool
- Write the spec in
src/core/ / .tswithdefineTool: an ID_ _, a title and description, the Zod argument and output schemas, its toolset and write class, andexecute(args, context). A write tool also givestargets(args, context): what the call writes to, as a permission rule should name it. - Test it beside the spec (
.test.ts), calling it throughinvokeas the entry points do. A tool that runs a program is tested against a fake of that program onPATH; no test reaches a real service. - List it in
src/tools.ts. A new toolset goes intotoolsetsinsrc/project.ts(anddefaultToolsetswhen it is on by default). - Add or update the toolset's skill,
skills/ - /SKILL.md. - Run
pnpm run build && pnpm run manifeststo list the tool inplugin.yaml, then describe it under "Tools and skills".
docs/conventions.md has the rules each step follows.
Reads and writes
Every read tool is named _ _read. Reads can run unasked; writes are confirmed by the harness.
| Harness | Reads without asking |
|---|
| OpenCode | always; the plugin ask
Only the beginning is shown; read the rest in the repo