open-index/open-npm huggingface dataset:
npm package: @jayshah123/mcp-doctor
Description: Discover MCP server configurations across Claude, VS Code, Copilot CLI, and Codex.
Author: Jay Shah
Latest version: 0.1.0

# mcp-doctor

`mcp-doctor` discovers MCP server configurations across dev tools and prints a consolidated view.

## What it scans

- Claude Code user config: `~/.claude.json`
- Claude Code managed config (platform specific)
- Claude Desktop user config
- VS Code user config (`mcp.json`, including user profiles when present)
- GitHub Copilot CLI user config: `~/.copilot/mcp-config.json` (or `$XDG_CONFIG_HOME/copilot/mcp-config.json`)
- Codex user config: `~/.codex/config.toml`
- Optional project-level configs with `--repo`:
  - `<repo>/.mcp.json`
  - `<repo>/.vscode/mcp.json`
  - `<repo>/.codex/config.toml`

## Useful commands

- Show help:
  - `npx @jayshah123/mcp-doctor --help`
- List user-level MCP servers:
  - `npx @jayshah123/mcp-doctor list`
- Include project-level configs:
  - `npx @jayshah123/mcp-doctor list --repo .`
  - `npx @jayshah123/mcp-doctor list --repo /path/to/repo`
- JSON output (for scripts/automation):
  - `npx @jayshah123/mcp-doctor list --json`
  - `npx @jayshah123/mcp-doctor list --repo . --json`

## Common use cases

- Audit all MCP servers currently reachable by your local tooling.
- Verify project onboarding (`.mcp.json`, `.vscode/mcp.json`, copilot config).
- Quickly detect missing files or malformed configs without crashing the CLI.
- Export machine-readable inventory for CI checks or reporting.
- Cross-check Codex/Copilot/Claude MCP setup from one command.

## Local development

- Build:
  - `pnpm --filter mcp-doctor build`
- Run from source:
  - `pnpm --filter mcp-doctor dev list`
- Run built CLI directly:
  - `node apps/mcp-doctor/dist/cli.js list`

## Testing

- Run tests:
  - `pnpm --filter mcp-doctor test`
- The test suite builds the CLI and validates key behaviors (argument handling, Codex parsing, Copilot CLI discovery, VS Code profile discovery).

## Publish (npmjs + GitHub Packages)

- A workflow is included at `.github/workflows/publish-mcp-doctor.yml`.
- It publishes `@jayshah123/mcp-doctor` to npmjs and GitHub Packages.
- Required repository secrets:
  - `NPM_TOKEN` (npm automation token with publish access for `@jayshah123/mcp-doctor`; if missing, npmjs publish is skipped)
  - `GITHUB_TOKEN` (provided automatically by GitHub Actions for GitHub Packages publish)
- Trigger options:
  - Run manually from GitHub Actions (`workflow_dispatch`).
  - Push a tag matching `mcp-doctor-v*`.

## Notes

- Missing config files are skipped.
- Malformed JSON files emit warnings and are skipped.
- Malformed Codex TOML sections are skipped.
- Invalid individual server entries emit warnings and are skipped.
- `--repo` requires a path value (for example `--repo .`).
- GitHub Copilot coding agent MCP is configured in GitHub repository settings UI, not from a repo-local config file.
npm package: @jayson991/react-iconfont
Description: A Project For React To Use Iconfont Intelligently
Author: jayson991
Latest version: 1.0.2
Deprecated: This package has been deprecated and is no longer maintained. Please migrate to @jayson991/react-ui which includes an Icon component with better features and full TypeScript support. Visit https://github.com/jaysonwu991/react-ui for documentation.

# react-iconfont

> A Library Project For React To Use Iconfont Intelligently

## Installation

```bash
$ npm i -S @jayson991/react-iconfont
```

```javascript
import IconFont from '@jayson991/react-iconfont';
```

## Iconfont

### Source Support

- [Icomoon](https://icomoon.io/)
- [Iconfont](https://www.iconfont.cn/)

### Method Support

- FontClass
  - type: icon
- Symbol, SVG
  - type: svg

## Usage

```javascript
import React from 'react';
import IconFont from '@jayson991/react-iconfont';

// import for IconFont usage
import './iconfont.css';
import './iconfont.js';

const App = () => (
  <>
    <div>
      Hello
      <IconFont type='icon' name='circle-checked' color='f00' size='30' />
      FontIcon
    </div>

    <div>
      Hello
      <IconFont type='svg' name='circle-checked' color='f00' size='30' />
      SvgIcon
    </div>
  </>
);

export default App;
```

### Property Support

| Property | Description                                                    |
| -------- | :------------------------------------------------------------- |
| name     | IconFont Name, String, default: ''                             |
| type     | Icon or SVG, String, default: 'icon'                           |
| size     | IconFont Size, String, default: '' (Browser Setting)           |
| color    | IconFont Color, String, default: '' (Only Support `#${color}`) |
npm package: @jayson991/react-modal
Description: A React Component To Use Modal Like Bootstrap Intelligently
Author: jayson991
Latest version: 1.1.10
Deprecated: This package has been deprecated and is no longer maintained. Please migrate to @jayson991/react-ui which includes a Modal component with better features and full TypeScript support. Visit https://github.com/jaysonwu991/react-ui for documentation.

# react-modal

> A React Component To Use Modal Like Bootstrap Intelligently

## Background

> [Bootstrap](https://getbootstrap.com/) Modal is beautiful, it is still attractive to be used by React, Modal is displayed in the center of the browser window，it uses `margin-top` to make it center instead of `flex` box (CSS3), so it is also fit for the browser of lower versions.

## Installation

```bash
$ npm i -S @jayson991/react-modal
```

## Usage With React

```javascript
import React from 'react'
import Modal from '@jayson991/react-modal'

const App = () => {
  const [showModal, setShowModal] = useState(false)

  return (
    <div className='App'>
      <span onClick={() => setShowModal(true)}>Click Me!</span>
      <Modal
        title='Hello'
        showModal={showModal}
        onHideModal={() => setShowModal(false)}
      >
        <h1>Hello World!</h1>
      </Modal>
    </div>
  )
}

export default App
```
npm package: @jaysonder/tts-validation
Description: Shared Zod validation schemas for TTS
Latest version: 0.1.0

# @jaysonder/tts-validation

Shared Zod schemas and inferred types for the Tone TTS server and UI.

## Install

```bash
npm install @jaysonder/tts-validation zod
```

## Usage

```ts
import { CreateRoomSchema } from '@jaysonder/tts-validation';

const result = CreateRoomSchema.safeParse(formValues);

if (!result.success) {
  console.log(result.error.flatten());
}
```

## Publishing

This package is published from the main server repo via the `Publish Validation Package` GitHub Actions workflow.
npm package: @jaythegeek/crmtoolkit
Description: ## How to use: 1. Just use `npm install --save @jaythegeek/crmtoolkit` 2. Use the components in your file directly.
Author: Jay the Geek
Latest version: 1.4.3

# Flock Components for VueJS

## Installation and Usage:
1. Just use `npm install --save @jaythegeek/crmtoolkit`
2. Now you can include the scripts by using following snippet:
```
import Components from '@jaythegeek/crmtoolkit';

// Global registration in your main.js/App.vue file
Object.entries(Components).forEach((name, component) => {
    Vue.component(name, component);
});
```
npm package: @jayvdb/react-native-lightning-experimental
Description: :warning: This is pre-alpha software. Please use as your own risk.
Author: Corey Phillips
Latest version: 0.0.9

# react-native-lightning

:warning: This is pre-alpha software. Please use as your own risk.

### Description
This library hopes to simplify the process of adding Lightning via LND's Neutrino to any React-Native app. 

### Android Installation:

Video Walkthrough: [TODO]

If you have any trouble, please use [this commit](https://github.com/coreyphillips/photon/commit/925510f3515f6bac812d41a49a43d3a0c0981dfe) as a reference to what needs to be changed/added to your project to get everything working.

1. Install Dependencies:
   ```
    yarn add react-native-lightning buffer
    yarn add -D rn-nodeify
    yarn install
    ```
2. Start the project:
    
    `react-native run-android`
    
#### Example Usage
```
import lnd from 'react-native-lightning';
const lndConf = new LndConf(Networks.regtest);

...

const res = await lnd.start(lndConf);
if (res.isOk()) {
  //Lnd started
}
```
    
### iOS Installation (In Progress)

### Manual (Android/iOS):
1. `yarn add react-native-lightning buffer react-native-randombytes`

2. Add the following to the end of your postinstall script in yourproject/package.json:
 
3. Copy necessary files over for Android & iOS respectively (Note: Create the directories if they do not exist):
    - Android - Copy LndNativeModule.java & LndNativePackage.java to `android/app/src/main/java/com/yourproject/` and be sure to replace "com.rnlightning" at the top of each file with the name of your own project.
    - iOS - Copy LndReactModule.h & LndReactModule.m to `ios/lightning/`.
     
4. Generate the Lndmobile.aar & Lndmobile.framework files.
    - Option 1 - Generate them locally with lnd v0.9:
        - To generate these files, please follow the instructions detailed in the README of Lightning Lab's Lightning App [here.](https://github.com/lightninglabs/lightning-app/tree/master/mobile)
    - Option 2 - Download pre-generated files:
        - If you do not wish to generate these files locally you can download them [here](https://github.com/coreyphillips/photon/releases/tag/v0.0.1) instead. However, I highly recommend you opt for option 1.

5. Add the Lndmobile.aar & Lndmobile.framework files to the project:
    - Add the Lndmobile.aar file to `android/Lndmobile`
    - Add the Lndmobile.framework file to `ios/lightning`

6. Add `packages.add(new LndNativePackage());` to "getPackages" in MainApplication.java just above `return packages`"

7. For Android you'll need these additional dependencies in `YourProject/android/app/build.gradle`:
 - `implementation 'com.google.protobuf:protobuf-java:3.13.0'`
 - `implementation 'com.android.support:multidex:1.0.3'` 
 - Then Add `multiDexEnabled true` under `defaultConfig` in the same gradle file.

8. Start the project:
    - iOS: `react-native run-ios`
    - Android: `react-native run-android`
npm package: @jayvee-digital-labs/scripts
Description: Helper Scripts that help deploy to other random stuff
Author: Joshua J Villahermosa
Latest version: 1.2.7

# JVDL Scripts

This repository contains a collection of useful scripts to automate various tasks.

## Installation

To install the `@jayvee-digital-labs/scripts` package, run the following command:

```bash
npm install -g @jayvee-digital-labs/scripts
```

## Scripts

### `jvdl-local-publish`

The `jvdl-local-publish` script is designed to streamline the process of publishing your project locally. It performs the following tasks:

1. Runs tests.
2. Updates the version based on the commit message.
3. Creates a git tag.
4. Pushes changes to the main branch.
5. Builds the Storybook static files.
6. Deploys to Firebase hosting.
7. Publishes to NPM.

This script is intended to be used locally as a temporary CI/CD process or if your CI/CD pipeline is broken.

For more detailed information on how to use the `local-publish` script, please refer to the [local-publish README](./bin/local-publish/README.md).

### `jvdl-standardize-repo`

The `jvdl-standardize-repo` script helps to standardize a repository by installing required packages, setting up Husky hooks, copying configuration files, merging JSON files, building a Docker image, and more. It performs the following tasks:

1. Installs necessary npm packages such as `rimraf`, `husky`, `cypress`, `commitizen`, `prettier`, and others.
2. Creates a `.husky` directory and adds pre-commit and pre-push hooks.
3. Copies various configuration files and directories to the root of the repository.
4. Merges `package.json` and `tsconfig.json` with the existing ones in the repository.
5. Builds a Docker image for Cypress visual regression tests.

This script should only be used on web applications with TypeScript enabled. If any step fails, the script will automatically rollback the changes.

For more detailed information on how to use the `standardize-repo` script, please refer to the [standardize-repo README](./bin/standardize-repo/README.md).

## License

This project is licensed under the MIT License.
npm package: @jayvogt/n8n-nodes-klaviyo
Description: Nodes and credentials for connecting the Klaviyo CRM to n8n
Author: Jay Vogt
Latest version: 0.4.1

# n8n-nodes-klaviyo

This is an n8n community node. It lets you use the Klaviyo CRM service in your n8n workflows.

Klaviyo is a unified customer platform that empowers businesses to build smarter digital relationships through personalized email and SMS marketing, leveraging their own data to drive engagement and growth. It offers tools for automation, segmentation, and analytics, specifically designed for e-commerce and direct-to-consumer brands.

This project is a work in progress. Please feel free to submit feedback and requests for additional operations and I will add them as I have time.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/reference/license/) workflow automation platform.

[Installation](#installation)  
[Operations](#operations)  
[Credentials](#credentials)  <!-- delete if no auth needed -->  
[Compatibility](#compatibility)  
[Usage](#usage)  <!-- delete if not using this section -->  
[Resources](#resources)  
[Version history](#version-history)  <!-- delete if not using this section -->  

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

### Custom Metrics
- Get All
- Get One

### Events
- Get All
- Get One
- Create

### Metrics
- Get All
- Get One

### Profiles
- Get All
- Get One
- Create
- Update

### Templates
- Create
- Delete
- Get All
- Get One
- Update

## Credentials

If you don't already have a Klaviyo account, you can [sign up here](https://www.klaviyo.com/sign-up).

This node authenticates to the Klaviyo API and your account using a private key. Steps for obtaining this private key can be found in the [Klaviyo documentation](https://help.klaviyo.com/hc/en-us/articles/7423954176283).

Klaviyo API private key must have minimum permissions of Read Access to the Events resource to pass the authentication test.

## Compatibility

Tested on version 1.75.2, but likely will work on lower versions.

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/community-nodes/)
* [Klaviyo Account Sign-up](https://www.klaviyo.com/sign-up)
* [Klaviyo API documentation](https://developers.klaviyo.com/en/reference/api_overview)

## Version history

### v1

- Main release