ai.pullpush/pullpush-mcp

Connect any two APIs and keep them in sync — 48 MCP tools with shadow previews and diagnostics.

ai.pullpush/pullpush-mcp · Repository · Website · version 2.2.1 · 0 stars · listed from registry

Install

The sweep installs into a clean prefix, but this is the command a user would run:

npx kaduno-pullpush-mcp

Needs credentials: PULLPUSH_API_KEY. The probe used placeholder values, so an amber needs credentials result below means the server asked for the real ones, not that it is broken. Maintainers: how to go green.

Results by platform

Linux

needs credentials2026-08-15 · probed over npm

4 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[kaduno-pullpush-mcp] Failed to connect to PullPush API at https://api.pullpush.ai/mcp
  Error: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Authentication required. Provide a valid Bearer token."},"id":null}

  Check that:
  - The API is running and reachable
  - Your PULLPUSH_API_KEY is valid
  - PULLPUSH_API_URL is correct (current: https://api.pullpush.ai)

  Common fixes:
  - Get a key from your PullPush admin panel → Settings → API Keys
  - For self-hosted: set PULLPUSH_API_URL=https://your-instance.com

macOS

needs credentials2026-08-15 · probed over npm

4 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[kaduno-pullpush-mcp] Failed to connect to PullPush API at https://api.pullpush.ai/mcp
  Error: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Authentication required. Provide a valid Bearer token."},"id":null}

  Check that:
  - The API is running and reachable
  - Your PULLPUSH_API_KEY is valid
  - PULLPUSH_API_URL is correct (current: https://api.pullpush.ai)

  Common fixes:
  - Get a key from your PullPush admin panel → Settings → API Keys
  - For self-hosted: set PULLPUSH_API_URL=https://your-instance.com

Windows

needs credentials2026-08-15 · probed over npm

4 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[kaduno-pullpush-mcp] Failed to connect to PullPush API at https://api.pullpush.ai/mcp
  Error: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Authentication required. Provide a valid Bearer token."},"id":null}

  Check that:
  - The API is running and reachable
  - Your PULLPUSH_API_KEY is valid
  - PULLPUSH_API_URL is correct (current: https://api.pullpush.ai)

  Common fixes:
  - Get a key from your PullPush admin panel → Settings → API Keys
  - For self-hosted: set PULLPUSH_API_URL=https://your-instance.com

Badge

Paste this into the project README to show the current result:

[![does it install](https://img.shields.io/endpoint?url=https://doesitinstall.com/badge/ai.pullpush__pullpush-mcp.json)](https://doesitinstall.com/s/ai.pullpush__pullpush-mcp.html)