Pushplus Mcp Server

Created By
pushplusa year ago
使用Java开发的pushplus MCP Server。 提供使用pushplus推送消息的能力。
Overview

what is pushplus MCP Server?

The pushplus MCP Server is a Java-based server that enables real-time message pushing capabilities using the pushplus platform, integrating various messaging services like WeChat, SMS, email, and more.

how to use pushplus MCP Server?

To use the pushplus MCP Server, you need to have JDK21 installed. Build the project using Maven with the command: mvn clean package. Then, start the server from the target directory using the command: java -Dpushplus.token=<your_token> -Dlogging.pattern.console= -jar pushplus-mcp-1.0.0.jar.

key features of pushplus MCP Server?

  • Integration with multiple messaging platforms (WeChat, SMS, email, etc.)
  • Simple API for message pushing
  • Easy setup and configuration

use cases of pushplus MCP Server?

  1. Sending notifications via multiple channels (e.g., SMS, email)
  2. Integrating with applications for real-time alerts
  3. Automating message delivery for various services

FAQ from pushplus MCP Server?

  • What is the main purpose of the pushplus MCP Server?

It is designed to facilitate real-time message pushing across various platforms using a simple API.

  • Do I need to pay to use pushplus MCP Server?

The server is free to use, but you may need to check the pricing for the pushplus service itself.

  • Can I customize the message token?

Yes, you can replace the message token in the startup command to use your own.

Server Config

{
  "mcpServers": {
    "pushplus": {
      "command": "npx",
      "args": [
        "-y",
        "@perk-net/pushplus-mcp-server"
      ],
      "env": {
        "PUSHPLUS_TOKEN": "your pushplus token"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
pushplus
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago