Agent Push Kit

io.github.JustinBStrongPublished by GitHub account JustinBStrongv0.1.1Updated Oct 24, 2026

Send, search, and manage notifications, accounts, and push preferences

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Agent Push Kit MCP lets an assistant send, search and manage push notifications, accounts and notification preferences through Agent Push Kit.

What you can do
Send push notifications to recipients through Agent Push Kit agents and accounts, and search previously sent notifications. Manage accounts and push notification preferences. Connect either to the hosted remote endpoint or run the npm package locally over stdio.
When to use it
Use it when an assistant should deliver push notifications to people or devices, look up past notifications, or adjust account-level notification preferences as part of a workflow.
Requirements
A named Agent Push Kit agent token beginning with apt_, supplied as AGENT_PUSH_KIT_TOKEN or as an Authorization bearer header. The token is created on the Agent Push Kit site. Either the remote endpoint or Node.js with npx for the local package; an optional AGENT_PUSH_KIT_API_BASE override exists for development.
Before you install
The token is a credential granting access to the account; keep it out of logs and shared configs. The server can send notifications and change accounts and push preferences, so actions may reach real recipients or alter settings.

Installation

In SourceWeft

  1. Open Agent Push Kit in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.JustinBStrong%2Fagent-push-kit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-push-kit": {
      "type": "http",
      "url": "https://api.chatdna.co/agent-push-kit/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Agent Push Kit MCP

Complete Agent Push Kit access over MCP stdio.

bash
AGENT_PUSH_KIT_TOKEN=apt_YOUR_TOKEN npx -y agent-push-kit-mcp

Create a named token at https://agentpushkit.com/connect-agent. Full documentation is at https://agentpushkit.com/docs/mcp.

Source: README.md at commit d12e455

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts