PulseMCP Server

Name: PulseMCP Server
Author: orliesaurus

@orliesaurus

Repository

About PulseMCP Server

An MCP server that helps you find MCP servers that are listed on PulseMCP.com

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pulsemcp": {
      "command": "npx",
      "args": [
        "-y",
        "pulsemcp-server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is PulseMCP Server?

PulseMCP Server is a Model Context Protocol (MCP) server that provides tools for discovering and exploring MCP servers and integrations through the PulseMCP API.

How to use PulseMCP Server?

Install by adding the server configuration to your MCP client (e.g., using npx with the pulsemcp-server package), or clone the repository, install dependencies, build, and run. Use npm start to start the server, or npm run inspector to inspect the MCP implementation.

Key features of PulseMCP Server

List MCP servers with filtering and pagination
Search servers by name or functionality
Filter servers by integration types
List all available integrations
Full TypeScript support
Error handling for API and parameter issues

Use cases of PulseMCP Server

Discover new MCP servers for your projects
Filter servers by integration type (e.g., GitHub)
Search for servers by specific functionality or name
Paginate through large server listings
Retrieve a list of all available integrations

FAQ from PulseMCP Server

What tools does PulseMCP Server provide?

It provides two tools: list_servers (with optional search, integration filtering, and pagination) and list_integrations (which lists all integrations with no parameters).

What parameters does `list_servers` accept?

list_servers accepts query (search term), integrations (array of integration slugs), count_per_page (max 5000), and offset (pagination skip).

What runtime dependencies are required?

The server requires Node.js, TypeScript, and dependencies including @modelcontextprotocol/sdk (^0.6.0), axios (^1.7.9), and TypeScript (^5.3.3).

How does error handling work?

The server handles invalid parameters, API connection issues, rate limiting, and authentication errors, returning errors in a standardized format with appropriate codes and messages.