open-index/open-npm huggingface dataset:
npm package: @iflow-mcp/gulbaki-swagger-mcp-server
Description: MCP Server for exploring Swagger/OpenAPI specifications
Author: Your Name
Latest version: 1.0.0

# Swagger/OpenAPI MCP Server

A Model Context Protocol (MCP) server that allows LLMs to explore and interact with Swagger/OpenAPI specifications. This server provides tools and resources for loading API specifications, browsing endpoints, and getting detailed information about API operations.

## Installation

1. Clone or create the project directory
2. Install dependencies:

```bash
npm install
```

3. Build the TypeScript code:

```bash
npm run build
```

## Usage


### Available Tools

#### `load_api`
Load an OpenAPI/Swagger specification into the server.

**Parameters:**
- `apiId` (string): Unique identifier for this API
- `source` (string): URL or file path to the OpenAPI/Swagger specification

**Example:**
```json
{
  "name": "load_api",
  "arguments": {
    "apiId": "petstore",
    "source": "https://petstore.swagger.io/v2/swagger.json"
  }
}
```

#### `get_endpoint_details`
Get detailed information about a specific API endpoint.

**Parameters:**
- `apiId` (string): ID of the loaded API
- `method` (string): HTTP method (GET, POST, etc.)
- `path` (string): API endpoint path
- `natural` (boolean, optional): If true, returns a human-readable summary

**Example:**
```json
{
  "name": "get_endpoint_details",
  "arguments": {
    "apiId": "petstore",
    "method": "GET",
    "path": "/pet/{petId}",
    "natural": true
  }
}
```

#### `list_apis`
List all currently loaded API specifications.

**Parameters:** None

#### `search_endpoints`
Search for endpoints matching a specific pattern.

**Parameters:**
- `apiId` (string): ID of the loaded API
- `pattern` (string): Search pattern for endpoint paths or descriptions

**Example:**
```json
{
  "name": "search_endpoints",
  "arguments": {
    "apiId": "petstore",
    "pattern": "pet"
  }
}
```

### Available Resources

#### `swagger://{apiId}/load`
Get overview information about a loaded API specification.

#### `swagger://{apiId}/endpoints`
Get a list of all available endpoints for an API.

#### `swagger://{apiId}/endpoint/{method}/{path}`
Get detailed information about a specific endpoint.

## Configuration with Claude Desktop

To use this server with Claude Desktop, add the following to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "swagger-explorer": {
      "command": "node",
      "args": ["/path/to/your/swagger-mcp-server/build/index.js"]
    }
  }
}
```

Replace `/path/to/your/swagger-mcp-server` with the actual path to your project directory.


## License

MIT License
npm package: @iflow-mcp/gustycube-discord-mcp
Description: Discord MCP server: route-generated tools + Gateway events for Model Context Protocol clients.
Latest version: 0.1.0

# Discord MCP Server

A **Model Context Protocol** server that provides AI agents with secure access to Discord's REST API and Gateway events.

<a href="https://glama.ai/mcp/servers/@GustyCube/discord-mcp">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/@GustyCube/discord-mcp/badge" alt="Discord Server MCP server" />
</a>

## Features

🔧 **120+ Discord API Tools** - Complete coverage of Discord's REST API  
🔒 **Security First** - Guild/channel allowlists, safe defaults, no accidental mentions  
⚡ **Real-time Events** - Gateway integration for live Discord activity  
🎯 **Smart Routing** - Auto-generated tools from declarative API catalog  
📦 **Modular Packs** - Enable only the functionality you need  

## Quick Start

```bash
# Clone and install
git clone https://github.com/GustyCube/discord-mcp
cd discord-mcp
npm install

# Configure your bot
cp .env.example .env
# Add your DISCORD_BOT_TOKEN and other settings

# Build and run
npm run build
npm start
```

## Documentation

📖 **Complete documentation available at [discord-mcp.gustycube.com](https://discord-mcp.gustycube.com/)**

### Quick Links
- [Getting Started](https://discord-mcp.gustycube.com/getting-started)
- [Configuration](https://discord-mcp.gustycube.com/configuration) 
- [Available Tools](https://discord-mcp.gustycube.com/tools)
- [Security Model](https://discord-mcp.gustycube.com/security)
- [Examples](https://discord-mcp.gustycube.com/examples)

## Example: Claude Desktop Integration

Add to your `mcp.json`:

```json
{
  "mcpServers": {
    "discord": {
      "command": "node",
      "args": ["/path/to/discord-mcp/dist/index.js"],
      "env": {
        "DISCORD_BOT_TOKEN": "your_bot_token_here",
        "ALLOW_GUILD_IDS": "123456789,987654321",
        "ALLOW_CHANNEL_IDS": "111111111,222222222"
      }
    }
  }
}
```

## What You Can Do

- **📝 Message Management** - Send, edit, delete messages and reactions
- **👥 User & Guild Info** - Get user profiles, guild details, member lists  
- **🔊 Channel Operations** - List channels, manage permissions, create threads
- **🎭 Rich Content** - Send embeds, manage webhooks, upload files
- **⚡ Live Events** - Subscribe to message events, member joins, etc.
- **🛡️ Moderation** - Manage bans, kicks, roles (with appropriate permissions)

## Contributing

See the [full documentation](https://discord-mcp.gustycube.com/) for development setup, API reference, and contribution guidelines.

## License

MIT License - see [LICENSE](LICENSE) file for details.
npm package: @iflow-mcp/h30190-taiwan-tender-mcp
Description: 台灣標案查詢 MCP 伺服器 - 對接政府開放平台資料
Latest version: 1.0.0

# Taiwan Tender MCP

![Version](https://img.shields.io/badge/version-v1.0.0-blue.svg)

基於 MCP 協定的台灣標案自動化查詢工具，串接 PCC-API 提供精確、合規且高效的標案情報。

---

## 核心特色 (Key Features)
- **合規資料源**: 串接 [PCC-API](https://pcc-api.openfun.app/) 取得政府公開標案資料，確保資料來源合法且穩定。
- **程式端預篩選**: 在 Node.js 端即時過濾「招標公告」與「更正公告」，確保資料活標性質並節省 AI Token。
- **智慧去重技術**: 自動識別並過濾重複案號，優先保留最新資訊，提供最準確的標案列表。
- **AI 整合**: 作為 Model Context Protocol (MCP) 伺服器，讓 AI (如 Claude, Gemini) 能直接理解並分析台灣標案趨勢。

## 技術架構 (Technical Architecture)
- **Runtime**: Node.js (v20+)
- **Protocol**: Model Context Protocol (MCP)
- **Data Source**: 
  - 主要介面：[pcc-api.openfun.app](https://pcc-api.openfun.app/)
  - 資料基礎：政府電子採購網「招標公告」
- **篩選邏輯**:
  1. **公告類別過濾**：僅保留 `招標公告` 與 `更正公告`。
  2. **關鍵字比對**：於標案名稱中搜尋使用者指定關鍵字。
  3. **資料去重**：針對搜尋結果中相同案號，優先保留日期較新之紀錄。
  4. **欄位精簡**：僅回傳案名、機關、金額、截止日與直接連結。

## 部署與安裝 (Deployment & Setup)

### 1. 環境準備
- 安裝 [Node.js](https://nodejs.org/) (v20 或以上版本)。
- 確認已安裝 `npm` 與 `git`。

### 2. 下載與編譯 (Build)
```bash
git clone [本專案 Git 網址]
cd SearchProcurementTenders/taiwan-tender-mcp
npm install
npm run build
```

### 3. 設定 AI 客戶端 (Configure Client)
本服務設計為本機運行的 MCP Server，請將其加入 AI 客戶端（以 Claude Desktop 為例）。

找到 Claude Desktop 的設定檔 `claude_desktop_config.json`：
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`

將以下內容加入 `mcpServers` 區塊（請將路徑修改為您本機的**絕對路徑**）：

```json
{
  "mcpServers": {
    "taiwan_tenders": {
      "command": "node",
      "args": [
        "C:/Users/[使用者名稱]/.../SearchProcurementTenders/taiwan-tender-mcp/build/index.js"
      ]
    }
  }
}
```
*注意：Windows 路徑建議使用正斜線 `/` (例如 `C:/Projects/...`) 或是雙反斜線 `\` 以避免 JSON 格式錯誤。*

## 使用範例 (Usage Examples)
您可以對 AI 說：
- 「搜尋近期與 新建工程 相關的標案」
- 「幫我找台北市的 裝修 標案」

## 資料來源與特別感謝 (Acknowledgements)
本工具的核心資料串接採用了由 [Openfun 團隊](https://github.com/openfunltd) 開發與維護的 **[PCC-API](https://pcc-api.openfun.app/)**。

我們由衷感謝 Openfun 團隊在台灣政府電子採購開放資料處理上的辛勤付出。他們將龐大且複雜的政府標案資料，整理為結構清晰且高效的 API 介面，才使得本 MCP 工具的開發成為可能。

## 關於作者 (About the Author)
- **作者**: 加號設計數位工程有限公司 HAO.H
- **網站**: [加號設計數位工程有限公司](https://hjplus.design)
- **粉絲專頁**: [加號設計數位工程有限公司](https://www.facebook.com/hjplus.design)
- **電子郵件**: [info@hjplusdesign.com](mailto:info@hjplusdesign.com)

我們是設計、建築與製造產業的外部研發夥伴，專門協助缺乏內部技術團隊的公司導入數位工作流程、工具與 AI，自動化你的知識與作業流程，以補足團隊技能升級的能量。 我們專門解決以下情況：

- **數位落差**：公司有設計與製造能量，但缺乏技術整合的工具與流程。
- **技術缺口**：團隊中沒技術人員或團隊，卻需要自動化或資料串接。
- **整合困難**：專案複雜、資料格式多，但缺乏整合經驗。
- **轉型迷惘**：想導入 AI 或 BIM，但不知道從哪開始。
- **研發支援**：需要專案型的數位顧問或工具開發支援。
- **專業顧問**：需要處理複雜幾何分析建模或 BIM 專案顧問。

更多數位轉型諮詢與服務內容歡迎與我們聯絡。

## 授權與宣告 (License & Disclaimer)
- **免責聲明**：本工具僅供參考，資料內容以「政府電子採購網」官方公告為準。使用者在進行投標決定前，應自行核實資料的準確性與時效性，開發者不對因使用本工具資料而產生的任何損失負責。
- **授權條款**：本專案採用 [MIT License](./LICENSE) 開源授權。
- **版權所有**：Copyright (c) 2026 加號設計數位工程有限公司 (HJPLUS.DESIGN Ltd.)。

---
*最後更新: 2026-01-29*
npm package: @iflow-mcp/hacienda-shared
Description: Shared types, constants, and enums for Hacienda CR electronic invoicing
Author: Dojo Coding Labs
Latest version: 0.2.1

# @dojocoding/hacienda-shared

Shared types, constants, enums, and Zod validation schemas for Costa Rica electronic invoicing (Hacienda API v4.4).

This package is used internally by `@dojocoding/hacienda-sdk`, `@dojocoding/hacienda-cli`, and `@dojocoding/hacienda-mcp`. It is not typically imported directly by end users.

## Contents

### Constants

- **Document type codes** -- All electronic document types (`01`-`09`) with human-readable names
- **Identification types** -- Cedula Fisica, Juridica, DIMEX, NITE
- **Tax codes** -- IVA codes and rate codes
- **Sale conditions** -- Contado, Credito, etc.
- **Payment methods** -- Efectivo, Tarjeta, Cheque, Transferencia, etc.
- **Currency codes** -- CRC, USD, EUR, etc.
- **Province codes** -- Costa Rica provinces and cantons
- **XAdES policy** -- Policy URI and SHA-1 hash for XAdES-EPES signing
- **Environment URLs** -- Sandbox and production API/IDP endpoints

### Types

- `FacturaElectronica` -- Full invoice type
- `Emisor` / `Receptor` -- Issuer and receiver types
- `LineaDetalle` -- Invoice line item
- `Impuesto` / `Descuento` / `Exoneracion` -- Tax, discount, exoneration
- `SubmissionRequest` / `SubmissionResponse` / `StatusResponse` -- API request/response types
- `ComprobantesListResponse` / `ComprobanteDetail` -- Document listing and detail types

### Schemas (Zod)

- `FacturaElectronicaSchema` -- Validates invoice input
- `EmisorSchema` / `ReceptorSchema` -- Validates issuer/receiver
- `LineaDetalleSchema` -- Validates line items
- `IdentificacionSchema` -- Validates identification fields
- `ClaveSchema` -- Validates 50-digit clave format
- `EnvironmentSchema` -- Validates environment strings

## Installation

```bash
npm install @dojocoding/hacienda-shared
```

This package is typically consumed as a workspace dependency via `workspace:*`.