open-index/open-npm huggingface dataset:
npm package: @fullon/flonjs
Description: flonjs
Latest version: 1.0.0

### FLON JS

#### Client
-----
Transaction
```
import { Client } from "@fullon/flonjs";
const client = new Client();
await client.transact(actions);
```
Signature

```
import { Client } from "@fullon/flonjs";
const client = new Client();
await client.signMessage(
  "这里是签名内容！" + new Date()
);
```
RPC Request
```
import { Client } from "@fullon/flonjs";
const client = new Client();
await client.rpc.get_abi('flon');
```
Get an account, get a FullOn login account
```
import { Client } from "@fullon/flonjs";
const client = new Client();
await client.getAccount();
```
Listen for push account, FullOn web will push the account to dapp, push it when initializing, and push it when the FullOn account changes.
```
import { Client, Account, ServerEventType } from "@fullon/flonjs";
const client = new Client();
client.on(ServerEventType.ACCOUNTS_CHANGED, (account: Account) => {
  // ...
})
```

Other
```
import { Client } from "@fullon/flonjs";
const client = new Client();
client.isInIframe();
```
npm package: @fullqueso/mcp-googleanalytics
Description: Google Analytics 4 MCP for Full Queso digital channel intelligence
Author: Francisco Padilla
Latest version: 1.0.1

# @fullqueso/mcp-googleanalytics

Google Analytics 4 MCP server for Full Queso — digital channel intelligence for fullqueso.com and somos.fullqueso.com.

## Tools

| Tool | Description |
|------|-------------|
| `get_traffic_overview` | Sessions, users, bounce rate by channel |
| `get_delivery_app_funnel` | Conversion funnel: session > menu > cart > checkout > purchase |
| `get_top_pages` | Top / landing / exit pages with engagement metrics |
| `get_traffic_sources` | Channel breakdown with Instagram attribution |
| `get_device_breakdown` | Mobile vs desktop vs tablet |
| `get_unified_marketing_dashboard` | GA4 + Meta Ads combined view |
| `get_realtime_overview` | Live active users and active pages |

## Quick Start

### 1. Install

```bash
npm install -g @fullqueso/mcp-googleanalytics
```

### 2. Set up credentials

Place the GA4 service account JSON key file somewhere secure on your machine (e.g. `~/.secrets/fullqueso-ga-service-account.json`). The service account must have **Viewer** access on the GA4 property.

### 3. Add to Claude Desktop

Add the following to your `claude_desktop_config.json`:

**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
**Windows:** `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "fullqueso-googleanalytics": {
      "command": "npx",
      "args": ["-y", "@fullqueso/mcp-googleanalytics"],
      "env": {
        "GA_PROPERTY_ID": "350429084",
        "GA_STREAM_ID_MAIN": "4443190758",
        "GA_STREAM_ID_LANDING": "11236115740",
        "GA_KEY_FILE": "/path/to/fullqueso-ga-service-account.json"
      }
    }
  }
}
```

Replace `/path/to/fullqueso-ga-service-account.json` with the actual path to the service account key on your machine.

### 4. Optional: Meta Ads integration

To enable `get_unified_marketing_dashboard` with blended GA4 + Meta Ads metrics, add these env vars:

```json
"META_ACCESS_TOKEN": "your-meta-access-token",
"META_AD_ACCOUNT_ID": "act_your_account_id"
```

Without Meta credentials, Tool 6 will return GA4 data only (Meta section returns null).

## Properties

- **fullqueso.com** — Delivery web app (stream ID: `4443190758`)
- **somos.fullqueso.com** — Brand landing page (stream ID: `11236115740`)
- **GA4 Property ID:** `350429084`

## Version History

See [CHANGELOG.md](CHANGELOG.md)
npm package: @fullrun/mcp
Description: Fullrun MCP server — Google Ads management for Claude Desktop, Cursor, and AI agents
Latest version: 0.1.1

# @fullrun/mcp

MCP server for managing Google Ads campaigns from Claude Desktop, Cursor, Windsurf, and other AI agents.

## Install

```bash
npm install -g @fullrun/mcp
```

## Setup

1. Get your API key at [fullrun.app](https://www.fullrun.app)
2. Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "fullrun": {
      "command": "npx",
      "args": ["-y", "@fullrun/mcp"],
      "env": {
        "FULLRUN_API_KEY": "frun_your_key_here"
      }
    }
  }
}
```

For Cursor, add to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "fullrun": {
      "command": "npx",
      "args": ["-y", "@fullrun/mcp"],
      "env": {
        "FULLRUN_API_KEY": "frun_your_key_here"
      }
    }
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `triage` | Diagnose account health. Returns prioritized issues. Always call this first. |
| `list_campaigns` | List all campaigns with status, budget, and metrics. |
| `get_performance` | Get account metrics (clicks, impressions, conversions, CPA) for 1-90 days. |
| `list_keywords` | List keywords with performance data. Optionally filter by campaign. |
| `run_optimization` | Trigger AI-powered optimization. Rate limited to 1 per hour. |

## Workflow

1. Call `triage` to see prioritized issues
2. Use `list_campaigns`, `get_performance`, `list_keywords` to investigate
3. Call `run_optimization` to fix the highest-priority issues automatically

## CLI

There's also a CLI for non-MCP usage:

```bash
npm install -g fullrun
fullrun triage
```

See [fullrun on npm](https://www.npmjs.com/package/fullrun) for CLI docs.

## License

MIT
npm package: @fullscript/fullscript-js
Description: Embeddable fullscript components
Latest version: 3.2.0

# Fullscript Embed Documentation

Please visit [the Fullscript Embed docs](https://fullscript.dev/docs/how-to-guides/fullscript-embed/what-is-fullscript-embed) to get started.

## Demo

In the project directory, we have two demo apps - React demo and UMD demo that you can experiment with.

### create-react-app demo

The `create-react-app` demo app will use the npm package version of the Fullscript Embed library. Compared to the CDN version, the npm package version will contain typing information for your IDE and requires a bundler for packaging.

To get things started, please run the following from the root of the project:

1. `yarn link`
2. `yarn install`
3. `yarn build`

Next run the following from the react-demo directory `cd demo/react-demo`:

1. `yarn link @fullscript/fullscript-js`
2. `yarn install`

Next you can run the React app using one of the options below:

- `yarn start` (from inside demo/react-demo)
- `yarn demo:npm` (from the root of the project)

### UMD demo

The UMD version of the Fullscript Embed library is pre-packaged for consumption by browsers. This does not rely on a bundler such as webpack and can be included via a single script tag in any html file. The downside of this version is that you do no benefit from typing information.

To run the demo, you need simply run the following from the root of the project:

- `yarn install` (from inside demo/javascript-demo/server)
- `yarn demo:umd` (from the root of the project)
npm package: @fullsnacker/create-express-ts-starter
Description: **Create Express TS Starter** is a tool for quickly setting up a server project with Node.js, Express, and TypeScript. This starter includes configurations for **Nodemon** and **ESLint**, allowing you to start developing immediately with automatic reload 
Author: fullsnacker
Latest version: 1.0.6

# Create Express TS Starter

**Create Express TS Starter** is a tool for quickly setting up a server project with Node.js, Express, and TypeScript. This starter includes configurations for **Nodemon** and **ESLint**, allowing you to start developing immediately with automatic reload and code linting.

## Installation

To create a new project using **Create Express TS Starter**, simply run the following command, replacing 'my-ex-ts' with your project name:

```bash
npx @fullsnacker/create-express-ts-starter my-ex-ts
```

This will generate a new folder named 'my-ex-ts' with a fully configured starter project.

It will also initialize a GIT repository and a README file for your project.

## Features

- **Node.js and Express**: Server setup with the Express framework.
- **TypeScript**: Ready-to-use setup for writing scalable, typed code.
- **Nodemon**: Automatic server reload on file changes.
- **ESLint**: Configured linter to maintain code quality and consistency.

## Project Structure

The generated project structure is as follows:

```
my-ex-ts/
├── src/
│   ├── server.ts           # Main server file
│   └── ...                # Additional configuration files
├── eslint.config.mjs           # ESLint configuration
├── tsconfig.json          # TypeScript configuration
├── nodemon.json          # Nodemon configuration
└── package.json           # Dependencies and scripts
```

## Available Scripts

Inside your new project directory, you can run the following commands:

- 'npm run dev': Starts the server in development mode with **Nodemon** for automatic reloading.
- 'npm run build': Compiles TypeScript to JavaScript in the 'dist' folder.
- 'npm start': Starts the server from the compiled code in 'dist'.
- 'npm run lint': Runs ESLint to analyze code and detect style or syntax issues.

## Customization

After creating your project, you can adjust the ESLint and TypeScript configurations to your liking. The 'eslint.config.mjs' and 'tsconfig.json' files are ready for you to tailor to your specific project needs.

## Contributing

Contributions are welcome! If you have suggestions for improving this starter or find any issues, feel free to open a pull request or report an issue.

## License

This project is licensed under the MIT License. See the 'LICENSE' file for more information.