sh.simplepu/mcp

@simplepush/mcp

Send tasks and notifications to people's phones. Answers build a queryable knowledge base.

GitHub npm

No known CVEs

No license

Actively maintained

Last commit 10d ago

Works with most clients

Transport: http, stdio

0 tools

Grade F

MCPpedia last refreshed this data 23h ago

Edit this pageView history

sh.simplepu/mcp is an MCP server that send tasks and notifications to people's phones. Answers build a queryable knowledge base. Its tool list has not been published yet over http and stdio, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.

Education

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktophttp, stdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "simplepush": {
      "env": {
        "SP_API_TOKEN": "your-token"
      },
      "args": [
        "-y",
        "@simplepush/mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/sh-simplepu-mcp)](https://mcppedia.org/s/sh-simplepu-mcp)

Read me

What sh.simplepu/mcp does

Send tasks and notifications to people's phones. Answers build a queryable knowledge base.

Test This Server

This server supports HTTP transport. Be the first to test it - help the community know if it works.

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

59/100across 5 weighted dimensions

How we score →

0255075100

−41

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @simplepush/mcp against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is sh.simplepu/mcp safe to use?: sh.simplepu/mcp has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment.
How do I install sh.simplepu/mcp?: sh.simplepu/mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with sh.simplepu/mcp?: sh.simplepu/mcp is compatible with claude-desktop, cursor, claude-code. It uses http and stdio transport.
Is sh.simplepu/mcp actively maintained?: sh.simplepu/mcp is actively maintained - last commit was 10 days ago.

Similar servers

Others in education

View all →

io.github.mims-harvard/tooluniverse91

2,700+ scientific tools for AI scientists: life science, research, literature, and more.

1.8k 4

Auto Claude Code Research In Sleep91

ARIS ⚔️ (Auto-Research-In-Sleep) — Lightweight Markdown-only skills for autonomous ML research: cross-model review loops, idea discovery, and experiment automation. No framework, no lock-in — works with Claude Code, Codex, OpenClaw, or any LLM agent.

19.2k 5

Daofy90

Daofy for Delphi — MCP Server that compiles Delphi projects and queries knowledge base for AI assistants.

108 10

ai.achromat/mcp-server89

Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool.

1 6

MCP Security Weekly

Get CVE alerts and security updates for sh.simplepu/mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

{ "mcpServers": { "simplepush": { "env": { "SP_API_TOKEN": "your-token" }, "args": [ "-y", "@simplepush/mcp" ], "command": "npx" } } }

@simplepush/mcp

MCP server for Simplepush. An agent sends tasks and notifications to people's phones and waits for the answers, appends follow-ups, cancels mistakes, and queries the record of everything that came back. Tasks, answers, replies, declines, and ad-hoc submissions stay queryable, so the stream doubles as a knowledge base of the work: what was asked, who answered what, and what is still open.

Tools

Tool	What it does
`send_notification`	Push for alerts and heads-ups. Can carry one `input` (a text input, a choice, or action buttons); returns right after sending unless `wait_seconds` is set. A copy per recipient by default — the result lists one `notification_id` per person; `shared: true` sends one all recipients see.
`send_task`	Sends a task and waits for the answers. Takes the full input set (text, choice, actions, slider, photo, voice recording, file, location), a `tag`, a `reply` mode, `expires_at`, Markdown and links. A copy per recipient by default: waits for everyone, reports per-recipient results with the rest pending at the deadline. `shared: true` sends one task all recipients answer together, first answer wins. Every result carries the `append_token`.
`append_subtask`	Appends a follow-up question or checklist item to a task or group, using the `append_token` from `send_task`. Never waits.
`cancel_task`	Withdraws a task (`tsk_`), subtask (`sub_`) or whole group (`grptsk_`) by id, with an optional reason and note.
`get_task_answer`	Resolves a `task_id` from an earlier `send_task`, or a `subtask_id` from `append_subtask`.
`get_notification_answer`	Resolves what came back on a `notification_id` from an earlier `send_notification` with an input.
`query_tasks`	One page of tasks as summaries: tag, topic, status, recipients, input kinds, attachment kinds, reply mode, sent time, subtask counts. Filters: status, time window, topic, member, group.
`get_task`	One task with all its subtasks: questions, answers, replies, declines, file ids.
`get_group_status`	Per-recipient status of a task group (`grptsk_`): who has answered, who has not.
`query_events`	The org's activity history: answers, replies, submissions, declines, cancellations, expiries, with who and when. Last 7 days by default.
`query_submissions`	Ad-hoc reports from the field (text, photo, file, voice, location), with who and when. Last 7 days by default.
`search_knowledge`	Full-text and location search over everything: tasks and notifications, what people answered and replied, and ad-hoc submissions, across all time. Literal word matching, plus stemming in up to three languages; or a coordinate plus radius (or a polygon of corner points), returning the locations recorded within it, nearest first. Each hit carries the id to read in full (a group send hits once, as its `grptsk_` id) and a snippet or a point with its distance. Plaintext records only.
`get_activity`	Everything going on for one member or the whole org in one call: open/declined/expired tasks plus the window's answers, replies, declines, cancellations and submissions. The tool for "any problems with X?" and "catch me up".
`download_attachment`	Fetches a photo, voice recording or file by `scope_id` (the tsk_/sub_/sbm_ id it belongs to) and `file_id` (an answer's inputId, a reply or submission file's id). Images are returned inline.

Tool

What it does

send_notification

Push for alerts and heads-ups. Can carry one input (a text input, a choice, or action buttons); returns right after sending unless wait_seconds is set. A copy per recipient by default — the result lists one notification_id per person; shared: true sends one all recipients see.

send_task

Sends a task and waits for the answers. Takes the full input set (text, choice, actions, slider, photo, voice recording, file, location), a tag, a reply mode, expires_at, Markdown and links. A copy per recipient by default: waits for everyone, reports per-recipient results with the rest pending at the deadline. shared: true sends one task all recipients answer together, first answer wins. Every result carries the append_token.

append_subtask

Appends a follow-up question or checklist item to a task or group, using the append_token from send_task. Never waits.

cancel_task

Withdraws a task (tsk_), subtask (sub_) or whole group (grptsk_) by id, with an optional reason and note.

get_task_answer

Resolves a task_id from an earlier send_task, or a subtask_id from append_subtask.

get_notification_answer

Resolves what came back on a notification_id from an earlier send_notification with an input.

query_tasks

One page of tasks as summaries: tag, topic, status, recipients, input kinds, attachment kinds, reply mode, sent time, subtask counts. Filters: status, time window, topic, member, group.

get_task

One task with all its subtasks: questions, answers, replies, declines, file ids.

get_group_status

Per-recipient status of a task group (grptsk_): who has answered, who has not.

query_events

The org's activity history: answers, replies, submissions, declines, cancellations, expiries, with who and when. Last 7 days by default.

query_submissions

Ad-hoc reports from the field (text, photo, file, voice, location), with who and when. Last 7 days by default.

search_knowledge

Full-text and location search over everything: tasks and notifications, what people answered and replied, and ad-hoc submissions, across all time. Literal word matching, plus stemming in up to three languages; or a coordinate plus radius (or a polygon of corner points), returning the locations recorded within it, nearest first. Each hit carries the id to read in full (a group send hits once, as its grptsk_ id) and a snippet or a point with its distance. Plaintext records only.

get_activity

Everything going on for one member or the whole org in one call: open/declined/expired tasks plus the window's answers, replies, declines, cancellations and submissions. The tool for "any problems with X?" and "catch me up".

download_attachment

Fetches a photo, voice recording or file by scope_id (the tsk_/sub_/sbm_ id it belongs to) and file_id (an answer's inputId, a reply or submission file's id). Images are returned inline.

The query tools work in both modes: an organization credential (an integration token, or the hosted connector signed in as an organization admin) reads the whole organization, a personal one (an API token, or the hosted connector with a personal API token) reads your personal stream (subscription required on personal accounts). On the hosted transport they need the read scope; download_attachment additionally needs files:read. Encrypted content is decrypted with the keys the server holds; anything it cannot open is left as ciphertext and reported.

A timeout

Frequently Asked Questions

Is sh.simplepu/mcp safe to use?

sh.simplepu/mcp has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment.

How do I install sh.simplepu/mcp?

sh.simplepu/mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with sh.simplepu/mcp?

sh.simplepu/mcp is compatible with claude-desktop, cursor, claude-code. It uses http and stdio transport.

Is sh.simplepu/mcp actively maintained?

sh.simplepu/mcp is actively maintained - last commit was 10 days ago.

@simplepush/mcp

Tools

Tool	What it does
`send_notification`	Push for alerts and heads-ups. Can carry one `input` (a text input, a choice, or action buttons); returns right after sending unless `wait_seconds` is set. A copy per recipient by default — the result lists one `notification_id` per person; `shared: true` sends one all recipients see.
`send_task`	Sends a task and waits for the answers. Takes the full input set (text, choice, actions, slider, photo, voice recording, file, location), a `tag`, a `reply` mode, `expires_at`, Markdown and links. A copy per recipient by default: waits for everyone, reports per-recipient results with the rest pending at the deadline. `shared: true` sends one task all recipients answer together, first answer wins. Every result carries the `append_token`.
`append_subtask`	Appends a follow-up question or checklist item to a task or group, using the `append_token` from `send_task`. Never waits.
`cancel_task`	Withdraws a task (`tsk_`), subtask (`sub_`) or whole group (`grptsk_`) by id, with an optional reason and note.
`get_task_answer`	Resolves a `task_id` from an earlier `send_task`, or a `subtask_id` from `append_subtask`.
`get_notification_answer`	Resolves what came back on a `notification_id` from an earlier `send_notification` with an input.
`query_tasks`	One page of tasks as summaries: tag, topic, status, recipients, input kinds, attachment kinds, reply mode, sent time, subtask counts. Filters: status, time window, topic, member, group.
`get_task`	One task with all its subtasks: questions, answers, replies, declines, file ids.
`get_group_status`	Per-recipient status of a task group (`grptsk_`): who has answered, who has not.
`query_events`	The org's activity history: answers, replies, submissions, declines, cancellations, expiries, with who and when. Last 7 days by default.
`query_submissions`	Ad-hoc reports from the field (text, photo, file, voice, location), with who and when. Last 7 days by default.
`search_knowledge`	Full-text and location search over everything: tasks and notifications, what people answered and replied, and ad-hoc submissions, across all time. Literal word matching, plus stemming in up to three languages; or a coordinate plus radius (or a polygon of corner points), returning the locations recorded within it, nearest first. Each hit carries the id to read in full (a group send hits once, as its `grptsk_` id) and a snippet or a point with its distance. Plaintext records only.
`get_activity`	Everything going on for one member or the whole org in one call: open/declined/expired tasks plus the window's answers, replies, declines, cancellations and submissions. The tool for "any problems with X?" and "catch me up".
`download_attachment`	Fetches a photo, voice recording or file by `scope_id` (the tsk_/sub_/sbm_ id it belongs to) and `file_id` (an answer's inputId, a reply or submission file's id). Images are returned inline.

Tool

What it does

send_notification

send_task

append_subtask

Appends a follow-up question or checklist item to a task or group, using the append_token from send_task. Never waits.

cancel_task

Withdraws a task (tsk_), subtask (sub_) or whole group (grptsk_) by id, with an optional reason and note.

get_task_answer

Resolves a task_id from an earlier send_task, or a subtask_id from append_subtask.

get_notification_answer

Resolves what came back on a notification_id from an earlier send_notification with an input.

query_tasks

One page of tasks as summaries: tag, topic, status, recipients, input kinds, attachment kinds, reply mode, sent time, subtask counts. Filters: status, time window, topic, member, group.

get_task

One task with all its subtasks: questions, answers, replies, declines, file ids.

get_group_status

Per-recipient status of a task group (grptsk_): who has answered, who has not.

query_events

The org's activity history: answers, replies, submissions, declines, cancellations, expiries, with who and when. Last 7 days by default.

query_submissions

Ad-hoc reports from the field (text, photo, file, voice, location), with who and when. Last 7 days by default.

search_knowledge

get_activity

download_attachment

Fetches a photo, voice recording or file by scope_id (the tsk_/sub_/sbm_ id it belongs to) and file_id (an answer's inputId, a reply or submission file's id). Images are returned inline.

A timeout