open-index/open-npm huggingface dataset:
npm package: @ifjkt/typeorm-revisions
Description: Revisions History for [TypeORM](https://typeorm.io) Entities 
Author: ifjkt@ifjkt.com
Latest version: 1.0.3

# @ifjkt/typeorm-revisions

![npm](https://img.shields.io/npm/v/@ifjkt/typeorm-revisions.svg)
![NPM](https://img.shields.io/npm/l/@ifjkt/typeorm-revisions.svg)

## Description

Provides a Revision History Subscriber for [TypeORM](http://typeorm.io) Entities

Tested: MySQL 8, MariaDB and Postgres

## Installation

```bash
$ npm i --save typeorm @ifjkt/typeorm-revisions
```

## Quick Start

### 1. Create your own Entity

```ts
@Entity()
class MyModel extends BaseEntity {
  @PrimaryGeneratedColumn()
  public id!: number;
  
  @Column()
  public name!: string;
  
  @Column()
  public email!: string;
}
```

### 2. Create an Entity for your Audit table

```ts
@Entity()
class MyModelHistory extends MyModel implements HistoryEntityInterface {
  @Column({
    name: 'record_id',
    type: 'int',
  })
  recordId: number;

  @Column({
    name: 'revision_timestamp',
  })
  revisionTime: Date;

  @Column({
    name: 'revision_type',
  })
  revisionType: RevisionActionType;
}
```

### 3. Annotate your Audit table with the @AuditTable decorator and specify your audit fields

```ts
@Entity()
@AuditTable({
  recordIdProperty: 'recordId',
  revisionTypeProperty: 'revisionType',
  revisionTimestampProperty: 'revisionTime',
})
class MyModelHistory extends MyModel implements HistoryEntityInterface {
  @Column({
    name: 'record_id',
    type: 'int',
  })
  recordId: number;

  @Column({
    name: 'revision_timestamp',
  })
  revisionTime: Date;

  @Column({
    name: 'revision_type',
  })
  revisionType: RevisionActionType;
}
```

### 4. Create an Entity Subscriber for your entity to process Audit events

```ts
@EventSubscriber()
class MyModelHistorySubscriber extends HistorySubscriber<MyModel, MyModelHistory> {
  public entity = MyModel;
  public historyEntity = MyModelHistory;
}
```

## License

[MIT](LICENSE)


Forked from https://github.com/ephillipe/typeorm-revisions
npm package: @ifkz/design-system
Description: ifkz.org design system
Latest version: 2.0.8

# IFKZ Design System

Components pack used for IFKZ.org frontend

## Installation

Use the package manager [yarn](https://yarnpkg.com/) to install the package.

```bash
$ yarn add @ifkz/design-system
```

## Package Usage
Just import our components and use them.
```javascript 1.8
import { MockBackground } from '@ifkz/design-system'
<MockBackground />
```

For documentation or contribution just clone our github repository and run Storybook UI.
```bash
$ git clone https://gitlab.com/ifkz/design-system.git
$ yarn
$ yarn start
```


## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @ifloren/demo
Description: 基于 Vue3.x + ElementPlus 的组件库
Author: ltt
Latest version: 1.0.0

# @sum-ui/demo

## Install

```bash
npm i @sum-ui/demo
# or
yarn add @sum-ui/demo
```

## Usage

```vue
<template>
 <sum-demo/>
</template>

<script lang="ts">
import { defineComponent, toRefs } from 'vue'
import SumDemo from '@sum-ui/demo'

export default defineComponent({
  components: { SumDemo },
  setup() {}
})
</script>
```

## Docs

[@sum-ui/demo](https://leitingting08.github.io/sum-ui/components/demo.html)
npm package: @iflow-mcp/0xdaef0f-job-searchoor
Description: A tool to search for jobs
Author: alex t.
Latest version: 0.1.5

# Job Searchoor MCP Server
[![Twitter Follow](https://img.shields.io/twitter/follow/Alex?style=social)](https://x.com/0xdaef0f)

An MCP server implementation that provides job search functionality.

![mc-demo](https://github.com/user-attachments/assets/87159634-5e4c-41af-ad54-4c5ef19bf9d0)

## Tools

get_jobs

Get available jobs with filtering options
Inputs:

sinceWhen (string): Since when to get available jobs. e.g., '1d' or '1w' (only days and weeks are supported)
keywords (string[], optional): Keywords to filter jobs by
excludeKeywords (string[], optional): Keywords to exclude from the jobs
isRemote (boolean, optional): Whether to filter jobs by remote work

## Usage with Claude Desktop

Add this to your claude_desktop_config.json:

```json{
"mcpServers": {
    "job-search": {
        "command": "npx",
        "args": ["-y", "job-searchoor"]
    }
}
```

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
npm package: @iflow-mcp/0xkoda-mcp-rust-docs
Description: MCP server for fetching Rust crate documentation
Latest version: 1.0.1

# MCP Rust Documentation Server

This is a Model Context Protocol (MCP) server that fetches and returns documentation for Rust crates providing essential context for LLM's when working with Rust code.

## Features

- Fetches documentation for any Rust crate available on docs.rs
- Strips HTML and formats the content for readability
- Limits response size to prevent overwhelming the client
- Uses the latest MCP SDK (v1.6.1)

## Installation

```bash
# Clone the repository
git https://github.com/0xKoda/mcp-rust-docs.git
cd mcp-rust-docs

# Install dependencies
npm install
```

### Prerequisites

- Node.js 
- npm 

## Usage

```bash
# Start the server directly
npm start
```

## Integrating with AI Assistants

### Claude Desktop

Add the following to your Claude Desktop configuration file (`claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "rust-docs": {
      "command": "node",
      "args": ["/absolute/path/to/index.js"]
    }
  }
}
```

Replace `/absolute/path/to/index.js` with the absolute path to the index.js file in this repository.

## Example Usage

Once the server is running and configured with your AI assistant, you can ask questions like:

- "Look up the documentation for the 'tokio' crate"
- "What features does the 'serde' crate provide?"
- "Show me the documentation for 'ratatui'"
- "Can you explain the main modules in the 'axum' crate?"

The AI will use the `lookup_crate_docs` tool to fetch and display the relevant documentation.

## Testing with MCP Inspector

You can test this server using the MCP Inspector:

```bash
npx @modelcontextprotocol/inspector
```

Then select the "Connect to a local server" option and follow the prompts.

## How It Works

This server implements a single MCP tool called `lookup_crate_docs` that:

1. Takes a Rust crate name as input (optional, defaults to 'tokio' if not provided)
2. Fetches the documentation from docs.rs
3. Converts the HTML to plain text using the html-to-text library
4. Truncates the content if it exceeds 8000 characters
5. Returns the formatted documentation in the proper MCP response format

## SDK Implementation Notes

This server uses the MCP SDK with carefully structured import paths. If you're modifying the code, be aware that:

1. The SDK requires importing from specific paths (e.g., `@modelcontextprotocol/sdk/server/mcp.js`)
2. We use the high-level McpServer API rather than the low-level tools
3. The tool definition uses Zod for parameter validation
4. Console output is redirected to stderr to avoid breaking the MCP protocol
5. The tool returns properly formatted MCP response objects

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

MIT
npm package: @iflow-mcp/0xkoda-rust-docs
Description: MCP server for fetching Rust crate documentation
Latest version: 1.0.0

# MCP Rust Documentation Server

This is a Model Context Protocol (MCP) server that fetches and returns documentation for Rust crates providing essential context for LLM's when working with Rust code.

## Features

- Fetches documentation for any Rust crate available on docs.rs
- Strips HTML and formats the content for readability
- Limits response size to prevent overwhelming the client
- Uses the latest MCP SDK (v1.6.1)

## Installation

```bash
# Clone the repository
git https://github.com/0xKoda/mcp-rust-docs.git
cd mcp-rust-docs

# Install dependencies
npm install
```

### Prerequisites

- Node.js 
- npm 

## Usage

```bash
# Start the server directly
npm start
```

## Integrating with AI Assistants

### Claude Desktop

Add the following to your Claude Desktop configuration file (`claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "rust-docs": {
      "command": "node",
      "args": ["/absolute/path/to/index.js"]
    }
  }
}
```

Replace `/absolute/path/to/index.js` with the absolute path to the index.js file in this repository.

## Example Usage

Once the server is running and configured with your AI assistant, you can ask questions like:

- "Look up the documentation for the 'tokio' crate"
- "What features does the 'serde' crate provide?"
- "Show me the documentation for 'ratatui'"
- "Can you explain the main modules in the 'axum' crate?"

The AI will use the `lookup_crate_docs` tool to fetch and display the relevant documentation.

## Testing with MCP Inspector

You can test this server using the MCP Inspector:

```bash
npx @modelcontextprotocol/inspector
```

Then select the "Connect to a local server" option and follow the prompts.

## How It Works

This server implements a single MCP tool called `lookup_crate_docs` that:

1. Takes a Rust crate name as input (optional, defaults to 'tokio' if not provided)
2. Fetches the documentation from docs.rs
3. Converts the HTML to plain text using the html-to-text library
4. Truncates the content if it exceeds 8000 characters
5. Returns the formatted documentation in the proper MCP response format

## SDK Implementation Notes

This server uses the MCP SDK with carefully structured import paths. If you're modifying the code, be aware that:

1. The SDK requires importing from specific paths (e.g., `@modelcontextprotocol/sdk/server/mcp.js`)
2. We use the high-level McpServer API rather than the low-level tools
3. The tool definition uses Zod for parameter validation
4. Console output is redirected to stderr to avoid breaking the MCP protocol
5. The tool returns properly formatted MCP response objects

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

MIT
npm package: @iflow-mcp/1panel-mcp
Description: 1Panel MCP server for automatic website deployment
Author: Ryan Wang
Latest version: 1.0.2

# 1Panel MCP Server

A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for automated website deployment to 1Panel.

> [!IMPORTANT]
> Currently, this project is an experimental project and does not mean that it can be used directly.

## Video demo

<https://www.bilibili.com/video/BV1SjQRY3EmM/>

## Features

- Automates website deployment to 1Panel servers
- Creates websites if they don't already exist
- Uploads static website files to 1Panel
- Fully compatible with the MCP standard protocol

## Usage

### Configure MCP in Cursor IDE

To use this server with Cursor IDE, add the following MCP configuration:

1. Open Cursor
2. Create `.cursor/mcp.json`

```json
{
  "mcpServers": {
    "1panel-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "1panel-mcp"
      ],
      "env": {
        "ONEPANEL_BASE_URL": "<your 1Panel base URL>",
        "ONEPANEL_API_KEY": "<your 1Panel API key>",
        "ONEPANEL_API_VERSION": "v2" // optional, default is v2
      }
    }
  }
}
```

### Use MCP to Deploy Websites

In Cursor, you can deploy websites using the following command in the AI chat:

```plaintext
Deploy to 1Panel with domain=yourdomain.com
```

Or you can use the following format:

```plaintext
Deploy website to 1Panel server, domain: yourdomain.com
```

## API Reference

### MCP Tool: deploy_website

Deploys a website to 1Panel.

**Parameters:**

- `domain` (required): Website domain
- `buildDir` (optional): Build directory path

**Response:**

```plaintext
Successfully deployed to 1Panel!
Domain: yourdomain.com
URL: http://yourdomain.com
Upload statistics:
- Total files: 25
- Successfully uploaded: 25
- Failed to upload: 0
```

## Implementation Details

### Deployment Process

1. **Check Build Directory**: Verifies if the specified build directory exists
2. **Website Creation**: Creates a new static website through 1Panel API if it doesn't exist
3. **File Upload**: Uploads all files from the build directory to the website
4. **Statistics**: Returns detailed statistics about the upload process

## Troubleshooting

If you encounter deployment issues, check the following:

1. Ensure your API Key is valid and has sufficient permissions
2. Verify that the website directory exists and has write permissions
3. Check the 1Panel server logs for more detailed error information
4. If file uploads fail, it may be due to file permission or format issues
npm package: @iflow-mcp/2bo-qiita-mcp-server
Description: MCP server for Qiita
Author: @2bo
Latest version: 0.1.0

# Qiita MCP Server

A Model Context Protocol (MCP) server for interacting with Qiita, the knowledge-sharing platform for engineers.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Overview

This package provides a Model Context Protocol (MCP) server that enables AI agents to interact with the Qiita API. It allows for creating, reading, and updating articles on Qiita through standardized MCP tools.

MCP is an open protocol for building AI agents that can use external tools and services. This server implements the MCP specification to provide tools for working with Qiita content.

## Provided Tools

The server provides the following MCP tools:

| Tool Name | Description |
|-----------|-------------|
| `get_my_qiita_articles` | Get current authenticated user's Qiita articles |
| `get_qiita_item` | Get a specific Qiita article by its ID |
| `post_qiita_article` | Create a new article on Qiita |
| `update_qiita_article` | Update an existing Qiita article |
| `get_qiita_markdown_rules` | Get Qiita markdown syntax rules and cheat sheet |

## Usage

### Prerequisites

- Node.js (>=20.0.0)
- A Qiita account with API access token
  - You can generate a Qiita API token by visiting: https://qiita.com/settings/tokens/new

### Usage with VS Code

1. Create a `.vscode/mcp.json` file in your project with the following content:

```json
{
  "inputs": [
    {
      "type": "promptString",
      "id": "qiita-api-token",
      "description": "Qiita API Token",
      "password": true
    }
  ],
  "servers": {
    "qiita-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["@2bo/qiita-mcp-server"],
      "env": {
        "QIITA_API_TOKEN": "${input:qiita-api-token}"
      }
    }
  }
}
```

## Development

### Setup

1. Clone the repository:

```bash
git clone https://github.com/2bo/qiita-mcp-server.git
cd qiita-mcp-server
```

2. Install dependencies:

```bash
npm install
```

3. Set up your environment:

- `npm run dev` - Run TypeScript in watch mode for development
- `npm run build` - Build the project
- `npm run prepare` - Prepare the package for publishing

### Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

This project is licensed under the MIT License - see the LICENSE file for details.
npm package: @iflow-mcp/2slides-mcp
Description: MCP server exposing 2slides.com tools (slides generate, jobs get, themes search)
Latest version: 0.2.1

## 2slides MCP Server

![2slides](https://www.2slides.com/images/og_2slides.webp)

Expose [2slides.com](https://www.2slides.com) tools for MCP clients (e.g., Claude Desktop).

### Get Your API Key
Before using this MCP server, you need to obtain an API key from [2slides.com/api](https://www.2slides.com/api).

### Configure in Claude Desktop
Edit `~/Library/Application Support/Claude/claude_desktop_config.json` and add:
```json
{
  "mcpServers": {
    "2slides": {
      "command": "npx",
      "args": ["2slides-mcp"],
      "env": {
        "API_KEY": "YOUR_2SLIDES_API_KEY"
      }
    }
  }
}
```
Then fully restart Claude Desktop. In a chat, open the tools panel and you should see the tools below.

### Available Tools
- `slides_generate` (POST /api/v1/slides/generate)
  - Args: `themeId` (string), `userInput` (string), `responseLanguage` (string), `mode` (optional: `sync` | `async`, default `sync`)
  - Example:
    ```json
    {
      "themeId": "st-1756528793701-fcg5fblt2",
      "userInput": "generate sample content",
      "responseLanguage": "English",
      "mode": "async"
    }
    ```
  - Notes:
    - `mode: "sync"` waits for generation to complete and returns the result directly (default).
    - `mode: "async"` submits the job and returns a `jobId`; poll with `jobs_get`.

- `jobs_get` (GET /api/v1/jobs/{jobId})
  - Args: `jobId` (string)
  - Example:
    ```json
    { "jobId": "D8h9VYDGdTlZ6wWSEoctF" }
    ```

- `themes_search` (GET /api/v1/themes/search)
  - Args: `query` (string), `limit` (number, optional, max 100)
  - Example:
    ```json
    { "query": "8 stages", "limit": 10 }
    ```

All tools return the 2slides API JSON as formatted text. Use `jobs_get` with the `jobId` from `slides_generate` to poll status or get the `downloadUrl` when available.

### Troubleshooting (Claude Desktop)
- If tools don’t appear in Claude, verify the config path is absolute and restart the app.
- Check Claude MCP logs:
```bash
tail -n 50 -f ~/Library/Logs/Claude/mcp*.log
```
- For stdio MCP servers, avoid logging to stdout; this server only logs errors to stderr. See the official guidance below.

### References
- Build an MCP server (official docs): https://modelcontextprotocol.io/docs/develop/build-server
- 2slides: https://www.2slides.com
- 2slides Templates: https://www.2slides.com/templates