open-index/open-npm huggingface dataset:
npm package: @mscopp/client-angular
Description: 🚀 Fetch API client for `@hey-api/openapi-ts` codegen.
Author: Hey API
Latest version: 0.7.2-angular-client-poc

<div align="center">
  <img alt="Hey API logo" height="150" src="https://heyapi.dev/images/logo-300w.png" width="150">
  <h1 align="center"><b>Fetch API Client</b></h1>
  <p align="center">🚀 Fetch API client for `@hey-api/openapi-ts` codegen.</p>
</div>

[Live demo](https://stackblitz.com/edit/hey-api-client-angular-example?file=openapi-ts.config.ts,src%2Fclient%2Fschemas.gen.ts,src%2Fclient%2Fsdk.gen.ts,src%2Fclient%2Ftypes.gen.ts,src%2FApp.tsx)

## Features

- seamless integration with `@hey-api/openapi-ts` ecosystem
- type-safe response data and errors
- response data validation and transformation
- access to the original request and response
- granular request and response customization options
- minimal learning curve thanks to extending the underlying technology
- support bundling inside the generated output
- [platform](https://heyapi.dev/openapi-ts/integrations) for automating codegen builds

## Platform

Our platform for OpenAPI specifications is now available. Automatically update your code when the APIs it depends on change. [Find out more](https://heyapi.dev/openapi-ts/integrations).

## Documentation

Please visit our [website](https://heyapi.dev/) for documentation, guides, migrating, and more.

## Sponsors

Love Hey API? Become our [sponsor](https://github.com/sponsors/hey-api).

<p>
  <a href="https://kutt.it/pkEZyc" target="_blank">
    <img alt="Stainless logo" height="50" src="https://heyapi.dev/images/stainless-logo-wordmark-480w.jpeg" />
  </a>
</p>

## Migration Guides

[OpenAPI Typescript Codegen](https://heyapi.dev/openapi-ts/migrating#openapi-typescript-codegen)
npm package: @mscottnelson/json-literal-typer
Description: generates literal typescript iterfaces from JSON
Author: Patrick Braune
Latest version: 0.0.5

# JSON literal typer

There are some tools out there that will produce TypeScript Interfaces from a
given JSON structure for you. But they only give you the basic types (`sting`,
`number`, etc.). What if there is an API where you want to get its literal
values/types?

# Demo

There is a live demo at [https://json-literal-typer.peppnet.de](https://json-literal-typer.peppnet.de)

# Example

Let's assume there is an API for gas stations. It will respond with data like
this:

```json
{
  "stations": [
    { "id": 1, "name": "station A", "status": "OPEN", "attributes": ["fast"] },
    {
      "id": 2,
      "name": "station B",
      "status": "OPEN",
      "attributes": ["fast", "24/7"],
      "operator": "Station Corp."
    },
    {
      "id": 3,
      "name": "station C",
      "status": "CLOSED",
      "attributes": [],
      "operator": "ACME Inc."
    }
  ]
}
```

What you would get from other tools is:

```typescript
interface Station {
  id: number;
  name: string;
  status: string;
  attributes: string[];
  operator?: string;
}
interface RootObject {
  stations: Station[];
}
```

Nice. But what if you could get:

```typescript
interface Stations {
  attributes: ('24/7' | 'fast')[];
  id: 1 | 2 | 3;
  name: 'station A' | 'station B' | 'station C';
  operator?: 'ACME Inc.' | 'Station Corp.';
  status: 'CLOSED' | 'OPEN';
}

interface Root {
  stations: Stations[];
}
```

# related or inspiring projects

- [json-to-ts] - Convert jsons to typescript interfaces
- [json2ts] - generate TypeScript interfaces from JSON
- [quicktype] - Generate types and converters from JSON, Schema, and GraphQL
- [ts-ast-viewer] - TypeScript AST viewer

[json-to-ts]: https://github.com/MariusAlch/json-to-ts
[json2ts]: http://www.json2ts.com/
[quicktype]: https://github.com/quicktype/quicktype
[ts-ast-viewer]: https://github.com/dsherret/ts-ast-viewer
npm package: @mscpo/vitepress
Description: Vite & Vue powered static site generator
Author: Evan You
Latest version: 2.0.0-alpha.3

# VitePress 📝💨

[![test](https://github.com/vuejs/vitepress/workflows/Test/badge.svg)](https://github.com/vuejs/vitepress/actions)
[![npm](https://img.shields.io/npm/v/vitepress)](https://www.npmjs.com/package/vitepress)
[![nightly releases](https://img.shields.io/badge/nightly-releases-orange)](https://nightly.akryum.dev/vuejs/vitepress)
[![chat](https://img.shields.io/badge/chat-discord-blue?logo=discord)](https://chat.vuejs.org)

---

VitePress is a Vue-powered static site generator and a spiritual successor to [VuePress](https://vuepress.vuejs.org), built on top of [Vite](https://github.com/vitejs/vite).

## Documentation

To check out docs, visit [vitepress.dev](https://vitepress.dev).

## Changelog

Detailed changes for each release are documented in the [CHANGELOG](https://github.com/vuejs/vitepress/blob/main/CHANGELOG.md).

## Contribution

Please make sure to read the [Contributing Guide](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md) before making a pull request.

## License

[MIT](https://github.com/vuejs/vitepress/blob/main/LICENSE)

Copyright (c) 2019-present, Yuxi (Evan) You
npm package: @mscrivo/outline-mcp-server
Description: MCP server for connecting to Outline wikis
Author: Cline
Latest version: 0.1.0

# @mscrivo/outline-mcp-server

An MCP server for connecting to Outline wikis. This server provides tools to search and access documents from your Outline knowledge base through the Model Context Protocol (MCP).

## Features

### Tools
- `search_documents` - Search for documents in your Outline wiki instance
  - Takes a search query and optional parameters for number of results and max characters
  - Returns relevant document matches with context

## Installation & Usage

This MCP server requires two environment variables to be set:
- `OUTLINE_API_KEY`: Your Outline API token
- `OUTLINE_INSTANCE_URL`: The URL of your Outline instance (e.g., https://your-company.outline.dev)

You can run this MCP server directly using npx with the environment variables:

```bash
OUTLINE_API_KEY=your_api_key OUTLINE_INSTANCE_URL=your_instance_url npx @mscrivo/outline-mcp-server
```

### Configuration

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "outline": {
      "command": "npx",
      "args": ["@mscrivo/outline-mcp-server"],
      "env": {
        "OUTLINE_API_KEY": "your_api_key",
        "OUTLINE_INSTANCE_URL": "your_instance_url"
      }
    }
  }
}
```

### Development

Clone the repository and install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

## License

MIT
npm package: @mscs/console
Description: NodeJS console library
Author: Jason Schilling
Latest version: 0.1.2


# @mscs/console

This is a library to write console applications in typescript for node.

## Installation

```shell script
$ yarn add @mscs/console
```

## Usage

Short example:

```typescript
import { Application, ArgumentMode } from "@mscs/console";

const application = new Application("Demo", "0.1.0-DEV");

application.register("commandName")
           .setDescription("command description")
           .addArgument("argumentName", ArgumentMode.REQUIRED, "argument description")
           .setCode(async (input, output) => {
               output.writeln("<info>Demo - 0.1.0-DEV</info>");
               output.writeln("<info>Argument:</info> " + input.getArgument("argumentName"));

               return 0;
           });

async function runtime() {
    await application.run();
}

runtime()
    .catch(error => {
        console.log(error);
        process.exit(1);
    });
```

# Important note

Since *Symfony* is, for good reason, a registered trademark, please take note that we are in no way associated with [the Symfony brand](https://symfony.com/) or the [SensioLabs](https://sensiolabs.com/) organization.
Therefore, we don't represent or speak for any of them.

## Difference between symfony/console

First of all not all features are included.

Currently, you won't have:

- The Kernel
- The Container
    - CommandLoader
- Auto-Complete
- Progressbar (planned)
- MultiByte support
- Alternative commands suggestions (planned)

There also might be changes between the API.
npm package: @mscs/deprecation
Description: A function to trigger deprecations.
Author: Jason Schilling
Latest version: 0.1.1


# Deprecation

A function to trigger deprecations.

## Install

Just run `yarn install @mscs/deprecation`

## Usage

There a several usages:

Trigger with custom message:
```typescript
import { deprecate } from "@mscs/deprecation"; 

function deprecatedMethod(){
    deprecate("deprecatedMethod is deprecated. Use something else instead.");
}
```

Trigger with the conventional message:
```typescript
import { deprecate } from "@mscs/deprecation"; 

function deprecatedMethod(){
    deprecate(3, 4, 6);
}
```

You can change behaviour by set the `triggerHandler` method.
```typescript
import { deprecate, defaultDeprecationTriggerHandler } from "@mscs/deprecation"; 

deprecate.triggerHandler = (message: string, error: Error) => {
    // Perform the default behaviour.
    defaultDeprecationTriggerHandler(message, error)
    
    // Send deprecation to an endpoint
    fetch("https://my-server.tld/api/deprecation", {
        method: 'POST',
        body: JSON.stringify({ message, error }),
    })
    .catch(console.error);
}

function deprecatedMethod(){
    deprecate(3, 4, 6);
}
```
npm package: @mscs/environment
Description: A library to load .env files and interact with the environment
Author: Jason Schilling
Latest version: 0.1.2


# @mscs/environment

A library to load and interact with the environment.

## Installation

```shell script
$ yarn add @mscs/environment
```

## Usage

Short example:

```typescript
import { EnvironmentLoader, ProcessEnvironment } from "@mscs/environment";

async function runtime(){
    const environment = new ProcessEnvironment();
    const environmentLoader = new EnvironmentLoader(environment);

    await environmentLoader.loadEnvironment(__dirname + '/../.env');

    if(environment.has('FOO')){
        const foo = environment.get("FOO");
        // ...
    }
}

runtime()
    .catch(console.error);
```

*This example expect that you are in a root file of the `src` directory in your project.*

## Documentation

Currently, you have to build the documentation on your own.

```shell script
$ git clone git@github.com:media-service-dev/environment.git
$ cd environment
$ yarn
$ yarn run docs
```

# Important note

The parser for `.env`-files and the environment file loading order logic was ported from [Symfony](https://symfony.com/).

Since *Symfony* is, for good reason, a registered trademark, please take note that we are in no way associated with [the Symfony brand](https://symfony.com/) or the [SensioLabs](https://sensiolabs.com/) organization.
Therefore, we don't represent or speak for any of them.
npm package: @mscs/eslint-config
Description: The mscs eslint configurations
Author: Jason Schilling
Latest version: 0.2.2


# @mscs/eslint-config

The eslint configuration used in all mscs projects.

# Installation

Install ESLint, this package and peer dependencies locally.

```shell script
$ yarn add eslint @mscs/eslint-config --dev
```

If you are using React in your project also install the React plugin.

```shell script
$ yarn add eslint-plugin-react --dev
```

# Configuration

Use our preset to get reasonable defaults:

```json
{
  "extends": ["@mscs/eslint-config"]
}
```

You can also use the specific configuration for NodeJS, browser or browser with React.

- `"extends": ["@mscs/eslint-config/node"]`
- `"extends": ["@mscs/eslint-config/browser"]`
- `"extends": ["@mscs/eslint-config/browser-react"]`
npm package: @mscs/git
Description: Interact programmatically with git
Latest version: 0.1.0


# @mscs/git

This is a library to interact programmatically with git in typescript for node.

## Installation

```shell script
$ yarn add @mscs/git
```

## Usage

Short example:

```typescript
import { open, RepositoryInterface, BranchInterface } from "@mscs/git";

async function runtime() {
    const repository: RepositoryInterface = open("/path/to/repo");
    const branches: BranchInterface[] = await repository.getBranches();

    for (const branch of branches){
        console.log(branch.getName());
    }
}

runtime().catch(error => {
    console.log(error);
    process.exit(1);
});
```
npm package: @mscs/process
Description: Run processes easier
Latest version: 0.4.2


# @mscs/process

This is a library to handle child processes in typescript for node.

## Installation

```shell script
$ yarn add @mscs/process
```

## Usage

Short example:

```typescript
import { Process } from "@mscs/process";

async function runtime() {
    const listDirectoryProcess = new Process(["ls", "-lar"]);
    const exitCode = await listDirectoryProcess.run();

    if(listDirectoryProcess.isSuccessful()){
        const output = listDirectoryProcess.getOutput();
        // ...
    } else {
        const output = listDirectoryProcess.getErrorOutput();
        // ...    
    }
}

runtime().catch(error => {
    console.log(error);
    process.exit(1);
});
```

# Important note 

Since *Symfony* is, for good reason, a registered trademark, please take note that we are in no way associated with [the Symfony brand](https://symfony.com/) or the [SensioLabs](https://sensiolabs.com/) organization.
Therefore, we don't represent or speak for any of them.
npm package: @mscststs/screenshot
Description: Template project for writing node package with napi-rs
Latest version: 1.0.0

# `@napi-rs/package-template`

![https://github.com/napi-rs/package-template/actions](https://github.com/napi-rs/package-template/workflows/CI/badge.svg)

> Template project for writing node packages with napi-rs.

# Usage

1. Click **Use this template**.
2. **Clone** your project.
3. Run `yarn install` to install dependencies.
4. Run `yarn napi rename -n [@your-scope/package-name] -b [binary-name]` command under the project folder to rename your package.

## Install this test package

```
yarn add @napi-rs/package-template
```

## Ability

### Build

After `yarn build/npm run build` command, you can see `package-template.[darwin|win32|linux].node` file in project root. This is the native addon built from [lib.rs](./src/lib.rs).

### Test

With [ava](https://github.com/avajs/ava), run `yarn test/npm run test` to testing native addon. You can also switch to another testing framework if you want.

### CI

With GitHub Actions, each commit and pull request will be built and tested automatically in [`node@20`, `@node22`] x [`macOS`, `Linux`, `Windows`] matrix. You will never be afraid of the native addon broken in these platforms.

### Release

Release native package is very difficult in old days. Native packages may ask developers who use it to install `build toolchain` like `gcc/llvm`, `node-gyp` or something more.

With `GitHub actions`, we can easily prebuild a `binary` for major platforms. And with `N-API`, we should never be afraid of **ABI Compatible**.

The other problem is how to deliver prebuild `binary` to users. Downloading it in `postinstall` script is a common way that most packages do it right now. The problem with this solution is it introduced many other packages to download binary that has not been used by `runtime codes`. The other problem is some users may not easily download the binary from `GitHub/CDN` if they are behind a private network (But in most cases, they have a private NPM mirror).

In this package, we choose a better way to solve this problem. We release different `npm packages` for different platforms. And add it to `optionalDependencies` before releasing the `Major` package to npm.

`NPM` will choose which native package should download from `registry` automatically. You can see [npm](./npm) dir for details. And you can also run `yarn add @napi-rs/package-template` to see how it works.

## Develop requirements

- Install the latest `Rust`
- Install `Node.js@10+` which fully supported `Node-API`
- Install `yarn@1.x`

## Test in local

- yarn
- yarn build
- yarn test

And you will see:

```bash
$ ava --verbose

  ✔ sync function from native code
  ✔ sleep function from native code (201ms)
  ─

  2 tests passed
✨  Done in 1.12s.
```

## Release package

Ensure you have set your **NPM_TOKEN** in the `GitHub` project setting.

In `Settings -> Secrets`, add **NPM_TOKEN** into it.

When you want to release the package:

```
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git]

git push
```
npm package: @mscswap/sdk
Description: 🛠 An SDK for building applications on top of mindchainswap.
Latest version: 1.0.1


```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @mseeley/export-from
Description: A convenience utility to roll-up a subsdirectory into named exports
Latest version: 0.1.1

# @mseeley/export-from

`export-from` is a convenience utility to roll-up a subdirectory into named
exports.

# Installation

```
npm install -D @mseeley/export-from
```

# Usage

Require `mseeley/export-from in an`index.js` file in the directory of files that
you want to roll-up.

> Example directory structure:

```bash
directory\
  index.js
  file-a.js
  file-b\
    index.js
```

> Example `index.js`:

```js
module.exports = require("@mseeley/export-from")(__dirname);
```

Later you can require the named exports.

> Example usage

```
const { fileA, fileB } = require("./directory");
```

Files with hyphens in their name are automatically converted to camelCase. All
other filenames are untouched.

These specific JavaScript files and directories are ignored by default:

- `*.spec.js`
- `__tests__/*`
- `__fixtures__/*`
- `node_modules`

_Additional_ exclude patterns can be provided. The patterns are evaluated by
[`minimatch`](https://www.npmjs.com/package/minimatch).

```js
module.exports = require("@mseeley/export-from")(__dirname, {
  excludes: ["foo/bar.js"]
});
```
npm package: @mseeley/jest-cases
Description: Jest utility for varying input provided to a test function
Latest version: 0.1.0

# jest-cases

[![status: CircleCI](https://circleci.com/gh/mseeley/jest-cases.svg?style=svg)](https://circleci.com/gh/mseeley/jest-cases) [![status: dependencies](https://david-dm.org/mseeley/jest-cases.svg)](https://david-dm.org/mseeley/jest-cases.svg)

## Installation

```
npm install -D @mseeley/jest-cases
```

## Usage

It would be time well spent to first learn about Jest's [`test.each`](https://jestjs.io/docs/en/api#testeachtable-name-fn-timeout) before adding a dependency to this utility.

If you're undeterred then please enjoy the [API Documentation](docs/index.md). The [specs](lib/index.spec.js) also provide good insight into operations and usage.

## Contributing

Contributions are welcome. Please see ensure that your code and commit message
pass linting requirements. See the `scripts` member of this repo's
`package.json` and `husky.config.js` for more information.

## History

Releases follow standard version. Please see our [`CHANGELOG.md`](CHANGELOG.md).

This utility is inspired, but entirely independent, of [`jest-in-case`](https://github.com/atlassian/jest-in-case).
npm package: @mseeley/jsdoc-to-markdown
Description: Convenience batch-operation wrapper around jsdoc-to-markdown
Latest version: 0.1.1

This is a package created for personal use. It wraps the [`jsdoc-to-markdown`](https://www.npmjs.com/package/jsdoc-to-markdown)
package with platform-agnostic batch handling and concurrency.

The package is written in a platform agnostic way yet has only been tested on
macOS. Testing feedback is welcome.

Simplifying assumptions:

- There should be a reusable external configuration file.
- The name of the JavaScript file becomes the name of the Markdown file.
- Each JavaScript file has a single semantic purpose.
- Vanilla Markdown output is good enough.

## Installation

```
npm install -D mseeley@jsdoc-to-markdown
```

## Configuration

You can use different ways to configure it:

- See [cosmiconfig](https://github.com/davidtheclark/cosmiconfig) for more
  details on what formats are supported.
- Or, pass a configuration file using the `--config` or `-c` flag

Example `ms-jsdoc2md.config.js`:

```
module.exports = {
  // These are the files from which to extract JSDoc comments. This is a glob
  // expression parsed by https://www.npmjs.com/package/glob-promise. The
  // pattern below will examine all JavaScript files in the `lib/` directory
  // which do not include `.spec` in their filename.
  inputPattern: "lib/**/!(*.spec).js",

  // The directory to store the generated markdown docs. It can be an absolute
  // path or resolve relative to `process.cwd()`.
  outputDirectory: "docs/",

  // Optional, maximum number of threads to spawn. Defaults to the number of
  // physical CPUs detected.
  concurrency: Number,

  // Optional, the extension of the files parsed for JSDoc comments. Defaults to
  // ".js".
  inputFileExtension: String,

  // Optional, verbose CLI output. Defaults to false.
  verbose: Boolean
};
```

## Usage

The package intentionally fails immediately when an error is encountered. The
package doesn't expose an API; best to use it as an NPM script:

Add the script to your `package.json`.

```
"scripts": {
  "doc": "ms-jsdoc2md"
}
```

Invoke it from the command line:

```
npm run doc
```

## Contributing

Contributions are welcome. Please see ensure that your code and commit message
pass linting requirements. See the `scripts` member of this repo's
`package.json` and `husky.config.js` for more information.
npm package: @mseep/1panel-mcp
Description: 1Panel MCP server for automatic website deployment
Author: Ryan Wang
Latest version: 1.0.1

# 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>"
      }
    }
  }
}
```

### 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: @mseep/ableton-copilot-mcp
Description: Ableton Live MCP depend on Ableton JS
Author: xiaolaa2
Latest version: 0.3.1

# ableton-copilot-mcp

<div align="center">
  <img src="https://img.shields.io/badge/Ableton%20Live-12-9cf" alt="Ableton Live 版本">
  <img src="https://img.shields.io/badge/Node.js-20%2B-green" alt="Node.js 版本">
  <img src="https://img.shields.io/badge/TypeScript-5.8.2-blue" alt="TypeScript 版本">
  <img src="https://img.shields.io/badge/License-MIT-yellow" alt="许可证">
</div>

> 一个基于 [ableton-js](https://github.com/leolabs/ableton-js) 搭建的 MCP（Model Context Protocol）服务器，用于与 Ableton Live 进行实时交互和控制，致力于辅助音乐制作人进行音乐制作。

## 🚀 功能特性

### 🎵 歌曲控制（Song）
- 获取歌曲基本信息（根音、音阶名称、速度、歌曲长度等）
- 获取所有音轨列表
- 创建 MIDI、音频和返送音轨
- 删除、复制音轨

### 🎹 音轨管理（Track）
- 获取音轨中的所有片段
- 在轨道中创建空白 MIDI 片段
- 设置音轨属性（静音、颜色、名称等）
- 复制 MIDI 片段到指定音轨

### 🎼 片段操作（Clip）
- 获取钢琴卷帘视图中的片段
- 获取、添加、删除和替换片段中的音符
- 设置片段属性（名称、颜色等）

### 🎧 其它操作（Audio）
- 支持对轨道内容进行录制

## 📥 安装准备
1. 安装 **Node.js**：确保 npx 命令可以正常运行，建议前往 [Node.js 官网](https://nodejs.org/) 安装最新的稳定版本
2. 安装 **MIDI Remote Scripts**：按照 [ableton-js](https://github.com/leolabs/ableton-js) 项目说明将 AbletonJS 的 MIDI Remote Scripts 安装到您的 Ableton Live 中

## 🔧 使用方法

1. 确保 Ableton Live 已经启动并运行
2. 确保在配置中启用 AbletonJS 控制界面：
   > **路径**：Settings -> Link, Tempo & MIDI -> MIDI -> Control Surface

   <div align="center">
     <img src="./assets/images/setting.jpg" alt="Ableton Live MIDI Remote Scripts 配置" width="80%" style="border-radius: 8px; box-shadow: 0 4px 8px rgba(0,0,0,0.1);">
     <p><em>图1：Ableton Live 中启用 AbletonJS 控制界面</em></p>
   </div>

3. 使用 MCP 客户端连接，支持的客户端包括但不限于：
   - [Cursor](https://www.cursor.com)
   - [Cherry Studio](https://github.com/CherryHQ/cherry-studio)
   - Claude Desktop

### Cursor 配置示例

在 Cursor 中配置 ableton-copilot-mcp：

```json
"ableton-js-mcp": {
    "command": "npx",
    "args": [
        "-y",
        "ableton-copilot-mcp"
    ]
}
```

## ✅ 兼容性测试

兼容性主要取决于 ableton-js 库的版本支持情况

| Ableton Live 版本 | 测试状态 |
| ----------------- | ------- |
| 12.1.10           | ✅ 已测试可用 |
| 11.x              | ⚠️ 待测试 |
| 10.x              | ⚠️ 待测试 |

## 🤝 贡献

欢迎提交问题和贡献代码，请通过 [GitHub Issues](https://github.com/xiaolaa2/ableton-copilot-mcp/issues) 提交问题或建议。

## 📄 许可证

本项目采用 [MIT 许可证](./LICENSE)。
npm package: @mseep/agentmail-mcp
Description: AgentMail MCP Server
Author: AgentMail
Latest version: 0.1.3

# AgentMail MCP Server

The AgentMail MCP Server provides tools for the AgentMail API.

## Setup

### Credentials

Get your API key from [AgentMail](https://agentmail.to)

### Configuration

```json
{
    "mcpServers": {
        "AgentMail": {
            "command": "npx",
            "args": ["-y", "agentmail-mcp"],
            "env": {
                "AGENTMAIL_API_KEY": "YOUR_API_KEY"
            }
        }
    }
}
```
npm package: @mseep/aligo-sms-mcp-server
Description: Model Context Protocol (MCP) server for Aligo SMS API integration
Author: hongsw
Latest version: 1.0.0

# Aligo SMS MCP 서버

Model Context Protocol(MCP)를 사용하여 Aligo SMS API에 접근할 수 있는 서버입니다. Claude AI와 같은 MCP 호환 AI 에이전트가 SMS 메시지를 보내거나 관련 정보를 조회할 수 있습니다.

## 설치

```json
{
  "mcpServers": {
    "aligo-sms-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "github:hongsw/aligo-sms-mcp-server",
        "mcp-server"
      ]
    }
  }
}
```

## 설정

API 키 설정은 `.garakrc` 파일에 저장됩니다. 홈 디렉토리에 다음과 같은 파일을 만듭니다:

https://smartsms.aligo.in/admin/api/auth.html

```
ALIGO_API_KEY=발급받은_API_키
ALIGO_USER_ID=발급받은_사용자_아이디
ALIGO_TEST_MODE=Y  # 테스트 모드 (Y/N)
```

## 사용 방법

도구 목록 아이콘을 찾아서 누르면

![](2025-03-22-16-53-35.png)


위의 설정을 완료하면 다음과 같은 화면을 볼 수 있습니다.


![Aligo SMS MCP 서버 화면](./image.png)

```

010xxxxyyyy 에서 010xxxxyyyy 로 문자를 보내줘 "안녕하세요 MCP 22222입니다." 라는 내용으로

```
위의 프롬프트를 사용하여 보내면 

![Aligo SMS MCP 서버 화면](./image2.png)


## 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.

## Acknowledgments

- Aligo for providing the SMS API
- Model Context Protocol for standardizing tool and resource access
npm package: @mseep/asset-price-mcp
Description: An MCP-compatible service that provides real-time asset prices including precious metals, cryptocurrencies, and more
Author: mk965
Latest version: 1.0.3

# 资产价格 MCP 服务器 (asset-price-mcp)

[English](./README.md) | [中文](#资产价格-mcp-服务器-asset-price-mcp) | [日本語](./README.ja.md)

## 概述

一个用于检索和展示当前资产价格信息的 MCP 服务器。此服务器提供工具来检索各种资产（包括贵金属和加密货币）的实时价格信息，便于大型语言模型访问和显示这些数据。

请注意，asset-price-mcp 目前处于早期开发阶段。功能和可用工具可能会随着我们继续开发和改进服务器而变化和扩展。

## 入门

许多代码编辑器和其他 AI 客户端使用配置文件来管理 MCP 服务器。

可以通过在配置文件中添加以下内容来配置 `asset-price-mcp` 服务器。

### MacOS/Linux

```json
{
  "mcpServers": {
    "Asset Price MCP": {
      "command": "npx",
      "args": ["-y", "asset-price-mcp"]
    }
  }
}
```

### Windows

```json
{
  "mcpServers": {
    "Asset Price MCP": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "asset-price-mcp"]
    }
  }
}
```

## 构建

```bash
npm run build
```

## 测试

```bash
npm test
```

## 许可证

此 MCP 服务器根据 MIT 许可证授权。这意味着您可以自由使用、修改和分发此软件，但需遵守 MIT 许可证的条款和条件。有关更多详细信息，请参阅项目仓库中的 LICENSE 文件。