open-index/open-npm huggingface dataset:
npm package: @mseep/hedera-mcp-server
Description: an MCP (model-context-protocol) server for Hedera
Author: bguiz
Latest version: 0.0.0

# Hedera Testnet Mirror Node MCP Server

This repository contains a Model Context Protocol (MCP) server that interfaces with the Hedera Testnet Mirror Node API.
The server is built using [FastMCP](https://www.npmjs.com/package/fastmcp), a TypeScript framework for creating MCP servers.
It utilises [Zod](https://zod.dev/) schemas for input validation.

## Features

- **Endpoint Integration**: Automatically converts Hedera Mirror Node APIs, defined in OpenAPI specification format, into MCP-compatible tools.
- **Server-Sent Events (SSE) Support**: Clients cannot connect to this MCP server over the SSE transport.
- **Schema Validation**: Ensures request parameters adhere to defined schemas using Zod.

## Prerequisites

Before running the server, ensure you have the following installed:

- [Bun](https://bun.sh/), or any other environment capable of running Typescript directly.

## Installation

(1) Clone the repository

```bash
git clone https://github.com/hedera-dev/mirrornode-mcp-server
```

(2) Navigate to the project directory

```bash
cd mirrornode-mcp-server
```

(3) Install dependencies

```bash
npm install
```

## Usage

To start the MCP server:

```bash
bun mcpServer.ts
```

Upon successful startup, you should see:

```
MCP server started
```

The server will be accessible via the configured SSE endpoint.

`http://localhost:3333/hedera-testnet-mirror-node-api/sse`

## Project Structure

- `mcpServer.ts`: The entry point that initializes and starts the MCP server.
- `openApiZod.ts`: Contains Mirror Node API endpoint definitions and an API client using `zodios` (like `axios` augmented with `zod` schema definitions).
  - Note that this file has been programmatically generated using `openapi-zod-client` plus some manual modifications.

## How It Works

(1) API Client Creation

An API client is created for the Hedera Testnet Mirror Node using the `createApiClient` function.
The MCP server proxies between this HTTP API client and its own SSE transport.

(2) Endpoint Conversion:

Each endpoint definition from `endpointDefinitions` is processed by the `convertZodiosToMcp` function, which:
   - Validates that the endpoint uses the `GET` method.
   - Maps parameters to Zod schemas.
   - Defines an execution function that makes the corresponding API call and returns the result.
   - Registers the tool with the MCP server.

(3) Server Initialization:

The MCP server is started with SSE transport.

## Dependencies

- [FastMCP](https://www.npmjs.com/package/fastmcp): Framework for building MCP servers.
- [Zod](https://zod.dev/): TypeScript-first schema declaration and validation library.
- [openapi-zod-client](https://github.com/astahmer/openapi-zod-client): Generates Zodios code from an OpenAPI specification file.

## Author

[Brendan Graetz](https://blog.bguiz.com/)

## Licence

MIT
npm package: @mseep/hello-world-mcp-server
Description: A simple Hello World MCP server example
Latest version: 1.0.0

# Hello World MCP Server

A simple MCP (Multi-Cloud Protocol) server example that responds with "Hello, World!" to any request.

## Installation

```bash
npm install
```

## Usage

```bash
npm start
```

## Using with Cursor's MPC Server

To use this MCP server with Cursor's MPC server:

1. Clone this repository
2. Install dependencies with `npm install`
3. Start the server with `npm start`
4. Configure Cursor to use this MCP server

## API

This server provides a simple "Hello World" response to any request.

## License

MIT
npm package: @mseep/holaspirit-mcp-server
Description: A MCP(Model Context Protocol) server that accesses to Holaspirit API
Author: syucream
Latest version: 0.1.2

# holaspirit-mcp-server
[![smithery badge](https://smithery.ai/badge/holaspirit-mcp-server)](https://smithery.ai/server/holaspirit-mcp-server)
[![npm version](https://badge.fury.io/js/holaspirit-mcp-server.svg)](https://badge.fury.io/js/holaspirit-mcp-server)

A [MCP(Model Context Protocol)](https://www.anthropic.com/news/model-context-protocol) server that accesses to [Holaspirit API](https://www.holaspirit.com/).

This server provides MCP-compatible access to Holaspirit's API, allowing AI assistants to interact with your Holaspirit data through a standardized interface.

<a href="https://glama.ai/mcp/servers/7tn35lri9w"><img width="380" height="200" src="https://glama.ai/mcp/servers/7tn35lri9w/badge" alt="Holaspirit Server MCP server" /></a>

## Features

Available tools:

- `list_tasks` - List all tasks in the organization
- `list_metrics` - List all metrics in the organization
- `list_circles` - List all circles in the organization
- `get_circle` - Get details of a specific circle
- `list_roles` - List all roles in the organization
- `get_role` - Get details of a specific role
- `list_domains` - List all domains in the organization
- `list_policies` - List all policies in the organization
- `list_meetings` - List all meetings in the organization
- `get_meeting` - Get details of a specific meeting

## Quick Start

### Installation

#### Installing via Smithery

To install holaspirit-mcp-server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/holaspirit-mcp-server):

```bash
npx -y @smithery/cli install holaspirit-mcp-server --client claude
```

#### Manual Installation

```bash
npm install holaspirit-mcp-server
```

### Configuration

- `HOLASPIRIT_API_TOKEN`: Your Holaspirit API token

### Usage

#### Start the MCP server

Directly:
```bash
npx holaspirit-mcp-server
```

Or, run the installed module with node.

#### Edit MCP configuration json for your client:

```json
...
    "lightdash": {
      "command": "npx",
      "args": [
        "-y",
        "holaspirit-mcp-server"
      ],
      "env": {
        "HOLASPIRIT_API_TOKEN": "<your token>"
      }
    },
...
```

## Development

### Available Scripts

- `npm run dev` - Start the server in development mode with hot reloading
- `npm run build` - Build the project for production
- `npm run start` - Start the production server
- `npm run lint` - Run linting checks (ESLint and Prettier)
- `npm run fix` - Automatically fix linting issues
- `npm run examples` - Run the example scripts

### Contributing

1. Fork the repository
2. Create your feature branch
3. Run tests and linting: `npm run lint`
4. Commit your changes
5. Push to the branch
6. Create a Pull Request
npm package: @mseep/honeycomb-mcp
Description: Model Context Protocol server for Honeycomb
Author: Austin Parker
Latest version: 0.0.1

# Honeycomb MCP Server

A [Model Context Protocol](https://modelcontextprotocol.io) server for interacting with Honeycomb observability data. This server enables LLMs like Claude to directly analyze and query your Honeycomb datasets across multiple environments.

## Features

- Query Honeycomb datasets across multiple environments
- Analyze columns and data patterns
- Run basic analytics queries
- Monitor SLOs and their status
- View and analyze Triggers
- Access dataset metadata and schema information

## Installation

```bash
npm install
npm run build
```

## Configuration

Create a configuration file at `~/.hny/config.json` with your Honeycomb environments and API keys:

```json
{
  "environments": [
    {
      "name": "production",
      "apiKey": "your_prod_api_key"
    },
    {
      "name": "staging",
      "apiKey": "your_staging_api_key"
    }
  ]
}
```

Each environment entry can also optionally include a `baseUrl` if you're using a different API endpoint.

## Usage

### With Claude Desktop

Add this to your Claude Desktop configuration (`claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "honeycomb": {
      "command": "node",
      "args": ["/path/to/build/index.mjs"]
    }
  }
}
```

### Available Tools

- `list-datasets`: List all datasets in an environment
- `get-columns`: List all columns in a dataset
- `run-query`: Run basic analytics queries with aggregations
- `analyze-column`: Get detailed analysis of specific columns
- `list-slos`: View all SLOs for a dataset
- `get-slo`: Get detailed SLO status including compliance
- `list-triggers`: View all triggers for a dataset
- `get-trigger`: Get detailed trigger information

### Resources

The server exposes Honeycomb datasets as resources with the URI format:
`honeycomb://{environment}/{dataset-slug}`

For example:
- `honeycomb://production/api-requests`
- `honeycomb://staging/backend-services`

## Development

```bash
pnpm install
pnpm run build
```

## Requirements

- Node.js 16+
- Honeycomb API keys with appropriate permissions:
  - Query access for analytics
  - Read access for SLOs and Triggers
  - Environment-level access for dataset operations

## Example Queries

Ask Claude things like:

- "What datasets are available in the production environment?"
- "Show me the SLO compliance for the API availability in production"
- "Are there any active triggers in the staging environment?"
- "What's the error rate in the production API dataset over the last hour?"

## License

MIT