open-index/open-npm huggingface dataset:
npm package: @iflow-mcp/d-zero-mcp-server
Description: D-Zero frontend coding MCP server
Author: D-ZERO Co., Ltd.
Latest version: 0.5.0

# ディーゼロ開発環境用 MCPサーバー

D-ZEROフロントエンド開発環境用のModel Context Protocol（MCP）サーバーです。
以下の機能を提供します：

- **Figmaデータの取得**: FigmaファイルやノードのデータをAPIを通じて取得
- **コーディングガイドラインの提供**: D-ZEROのフロントエンド開発規約の提供
- **CLINEとの統合**: CLINEのMCPサーバーとして動作し、AIアシスタントとの対話をサポート

このサーバーを使用することで、開発者はFigmaデザインの参照やコーディング規約の確認をAIアシスタントとの会話を通じて行うことができます。

## `cline_mcp_settings.json`

CLINEの「MCP Servers」設定から、「Installed」タブを選択し、Configure MCP Serversで`cline_mcp_settings.json`ファイルを編集します。

```json
{
	"mcpServers": {
		"coding_guidelines": {
			"command": "npx",
			"args": ["-y", "@d-zero/mcp-server"],
			"env": {
				"FIGMA_ACCESS_TOKEN": "abcd_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
			},
			"disabled": false,
			"autoApprove": []
		}
	}
}
```

`@d-zero/mcp-server`パッケージの実行に失敗する場合は、グローバルにインストールしてフルパスを指定してください（[参考Issue](https://github.com/cline/cline/issues/1247)）。

Figmaのアクセストークンは https://www.figma.com/developers/api#access-tokens から取得してください。

## Contribution

このMCPサーバー自体の開発には`.env`ファイルが必要です。

```env
# Figma API設定
FIGMA_ACCESS_TOKEN=abcd_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# テスト用のFigma URL
FIGMA_TEST_URL=https://www.figma.com/file/abcdef123456/FileName
```
npm package: @iflow-mcp/dablclub-polygon-mcp
Description: A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain
Author: Your Name
Latest version: 1.0.0

# Polygon MCP Server

A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain.

## Features

- Call contract functions on Polygon PoS
- Get ERC20 token balances
- Transfer ERC20 tokens
- Get current gas prices

## Installation

1. Clone this repository:
```bash
git clone https://github.com/your-username/polygon-mcp.git
cd polygon-mcp
```

2. Install dependencies:
```bash
npm install
```

3. Build the project:
```bash
npm run build
```

## Configuration

Create a `.env` file in the root directory with the following variables:

```
SEED_PHRASE="your twelve word seed phrase here"
```

## Usage

### Running the server

```bash
npm start
```

### Using with Claude

To use this MCP server with Claude, you need to add it to your MCP settings file:

For VSCode Claude extension:
```json
{
  "mcpServers": {
    "polygon": {
      "command": "node",
      "args": ["/path/to/polygon-mcp/build/index.js"],
      "env": {
        "SEED_PHRASE": "your twelve word seed phrase here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
```

For Claude desktop app:
```json
{
  "mcpServers": {
    "polygon": {
      "command": "node",
      "args": ["/path/to/polygon-mcp/build/index.js"],
      "env": {
        "SEED_PHRASE": "your twelve word seed phrase here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
```

## Available Tools

### call_contract

Call a contract function on Polygon PoS.

Parameters:
- `contractAddress`: The address of the contract to call
- `functionName`: The name of the function to call
- `functionArgs`: The arguments to pass to the function
- `abi`: The ABI of the contract
- `value` (optional): The value of MATIC to send with the transaction

### erc20_balance

Get the balance of an ERC20 token on Polygon PoS.

Parameters:
- `contractAddress`: The address of the contract to get the balance of

### erc20_transfer

Transfer an ERC20 token on Polygon PoS.

Parameters:
- `contractAddress`: The address of the contract to transfer the token from
- `toAddress`: The address of the recipient
- `amount`: The amount of tokens to transfer

### get_gas_price

Get the current gas price on Polygon PoS.

## License

MIT
npm package: @iflow-mcp/daipendency-mcp
Description: Model Context Protocol (MCP) server for Daipendency
Author: Gus Narea
Latest version: 0.9.4

# Daipendency MCP Server

Model Context Protocol (MCP) server for [Daipendency](https://github.com/daipendency/daipendency).

## Install

Use `npx -y @daipendency/mcp` to run this MCP server with stdio.

## API

### Tools

#### `get_dependency_docs`

Extract narrative and API documentation for a dependency of a local project.

This is equivalent to [`daipendency extract-dep`](https://github.com/daipendency/daipendency#daipendency-extract-dep-extract-the-documentation-of-a-dependency).

## Architectural Decisions

Although Daipendency itself is implemented in Rust,
this project is implemented in TypeScript so that we could use one of the official, feature-rich MCP SDKs.
This required implementing [JS bindings for Daipendency](https://github.com/daipendency/daipendency-js).
npm package: @iflow-mcp/damus-io_nostrdb-mcp
Description: A Model Context Protocol server for nostrdb enabling LLMs to query nostr via the nostrdb command line tool.
Author: William Casarin
Latest version: 1.2.1


# nostrdb-mcp

A Model Context Protocol server for nostrdb.

## What?

MCP is a protocol that enables LLMs to interface with tools and systems. This server enables LLMs to use the `ndb` nostrdb command line tool to make local nostr queries.

By default, it uses your [Notedeck](https://github.com/damus-io/notedeck) nostrdb directory so that it can search notes your notedeck has seen.

## Install

Make sure you have `ndb` on your path by [compiling it via the nostrdb repo](https://github.com/damus-io/nostrdb) by typing `make ndb` and copying it to your path.

### Goose

You can configure [goose](https://github.com/block/goose) to use this tool:

```
$ goose configure
```

When adding a provider, use: `npx -y nostrdb-mcp`

You can create a temporary session to try it out like so:

```
$ goose session --with-extension `npm -y nostrdb-mcp`
```

## Example

![](https://cdn.jb55.com/s/e2ed680f1de0e5e0.png)
npm package: @iflow-mcp/danny-avila-example-mcp-server
Description: A Model Context Protocol (MCP) server implementation in Node.js
Author: Danny Avila
Latest version: 1.0.1

# Simple Streamable HTTP MCP Server

A clean implementation of an MCP server using the Streamable HTTP transport, following the official MCP patterns.

## Features

- **Streamable HTTP Transport**: Supports both JSON responses and Server-Sent Events (SSE)
- **Session Management**: Proper session handling with unique session IDs
- **Progress Notifications**: Long-running tools send progress updates
- **Multiple Tools**:
  - `hello_world`: Simple greeting tool
  - `get_server_info`: Returns server information
  - `long_running_test`: Configurable duration test with progress (default: 30s)
  - `slow_test`: 10-minute test with progress updates

## Architecture

This server follows the MCP team's recommended patterns:

1. **Session-based Architecture**: Each client gets a unique session ID
2. **Transport Reuse**: Transports are stored and reused for subsequent requests
3. **Proper Initialization**: New sessions are created only on initialization requests
4. **Clean Shutdown**: All transports are properly closed on server shutdown

## Running the Server

```bash
# Install dependencies
npm ci

# Run the server (default port: 3001, DEBUG logging enabled by default)
npm run start

# Run without debug logging, or edit `.env` to set DEBUG=false
DEBUG=false npm run start

# Run in development mode (auto-reload)
npm run dev
```

## Testing

Use the provided test script to verify the server is working correctly:

```bash
npm run test:http
```

This will test:
- Session initialization
- Tool listing and calling
- Session ID management
- SSE streaming
- Session termination

## Progress Notifications

The `long_running_test` and `slow_test` tools demonstrate progress notifications:

```javascript
// Example tool call with progress
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "long_running_test",
    "arguments": {
      "duration": 60,
      "steps": 12,
      "message": "Testing progress notifications"
    },
    "_meta": {
      "progressToken": "unique-progress-token"
    }
  },
  "id": 1
}
```

The server will send progress notifications:
```javascript
{
  "method": "notifications/progress",
  "params": {
    "progress": 1,
    "total": 12,
    "progressToken": "unique-progress-token"
  }
}
```

## Key Differences from Basic Examples

1. **Proper Session Management**: Sessions are created per client, not per request
2. **Transport Lifecycle**: Transports persist across requests within a session
3. **Error Handling**: Comprehensive error handling for all edge cases
4. **Progress Support**: Long-running operations can report progress
5. **Clean Architecture**: Clear separation between server creation and request handling

## Environment Variables

- `PORT`: Server port (default: 3001)
- `DEBUG`: Enable debug logging (`true` by default)

## Endpoints

- `POST /mcp`: Handle JSON-RPC requests
- `GET /mcp`: Handle SSE streaming
- `DELETE /mcp`: Terminate sessions
- `GET /health`: Health check endpoint