open-index/open-npm huggingface dataset:
npm package: @rogerchi/cdk-sns-digest
Description: This AWS CDK Construct creates a digest version of an existing SNS topic. The digest infrastructure aggregates noficiations from an SNS topic over a period of time (using an intermediary SQS queue and a scheduled Lambda function) into .csv or .json format
Author: Roger Chi
Latest version: 0.5.2

# cdk-sns-digest: Create a digest version of an SNS topic

This AWS CDK Construct creates a digest version of an existing SNS topic. The digest infrastructure aggregates noficiations from an SNS topic over a period of time (using an intermediary SQS queue and a scheduled Lambda function) into .csv or .json format, stores it in a new S3 bucket, and sends notifications to the digest SNS topic with a presigned link to download the aggregate file.

## Motivation

I had a project where I created a small ETL process to parse Excel files upon upload to S3. Upon completion of the parsing, a notification was sent to an SNS topic with e-mail subscriptions. These uploads could either happen sporatically or as a bulk process. The bulk processes tended to overrun the e-mail endpoints with hundreds of notifications, and the original suggestion was to unsubscribe prior to the bulk submissions and resubscribe after. I created this digest process so that bulk notifications do not overrun e-mail endpoints.

## Installation

```
npm i @rogerchi/cdk-sns-digest
```

## Example Usage

### Use default aggregation Lambda function

Included in the package is a simple Python lambda function which aggregates the notifications using the pandas library. The latest pandas layer is retrieved from [KLayers](https://github.com/keithrozario/Klayers).

```typescript
import { createSnsDigest, SnsDigestFormat } from "@rogerchi/cdk-sns-digest";

// Within a stack
const snsDigest = createSnsDigest(this, "snsDigest", {
  snsTopic: Topic, // Existing SNS Topic
  format: SnsDigestFormat.CSV, // SnsDigestFormat.CSV or SnsDigestFormat.JSON
  schedule: Schedule.expression("rate(5 minutes)"), // Digest rate
});
```

### Supply your own Lambda function

Use your own lambda function to aggregate the notifications. Environment variables passed to the lambda function are:

- SQS_QUEUE_URL
- SQS_QUEUE_NAME
- SQS_QUEUE_ARN
- DIGEST_TOPIC_ARN
- DIGEST_TOPIC_NAME
- DIGEST_BUCKET_NAME
- DIGEST_BUCKET_ARN

```typescript
import { SnsDigest, SnsDigestFormat } from '@rogerchi/cdk-sns-digest';

// Within a stack
  const snsDigest = new SnsDigest(this, "snsDigest", {
    snsTopic: sns.Topic, // Required
    format: SnsDigestFormat.CSV, // Optional, defaults to SnsDigestFormat.CSV
    schedule: events.Schedule, // Optional, defaults to 5 minutes
    aggregatorLambda: lambda.Function; // Required
  });
```

## Limitations

This was created to handle "human-scale" notifications and tested with digests of around 1000 notifications over a five minute period.
npm package: @rogeriolembo/mcp-api
Description: MCP server for SysAuto API integration
Author: Model Context Protocol
Latest version: 0.1.4

# sysauto Ask MCP Server

An MCP server implementation that integrates the Sonar API to provide Claude with unparalleled real-time, web-wide research.

![Demo](sysauto-ask/assets/demo_screenshot.png)


## Tools

- **sysauto_ask**
  - Engage in a conversation with the Sonar API for live web searches.
  - **Inputs:**
    - `messages` (array): An array of conversation messages.
      - Each message must include:
        - `role` (string): The role of the message (e.g., `system`, `user`, `assistant`).
        - `content` (string): The content of the message.

## Configuration

### Step 1: 

Clone this repository:

```bash
git clone git@github.com:rogeriolembo/mcp-api.git
```

Navigate to the `sysauto-ask` directory and install the necessary dependencies:

```bash
cd mcp-api/sysauto-ask && npm install
```

### Step 2: Get a Sonar API Key

1. Sign up for a [Sonar API account](https://docs.sysauto.ai/guides/getting-started).
2. Follow the account setup instructions and generate your API key from the developer dashboard.
3. Set the API key in your environment as `sysauto_API_KEY`.

### Step 3: Configure Claude Desktop

1. Download Claude desktop [here](https://claude.ai/download). 

2. Add this to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "sysauto-ask": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SYSAUTO_API_KEY",
        "mcp/sysauto-ask"
      ],
      "env": {
        "SYSAUTO_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
```

### NPX

```json
{
  "mcpServers": {
    "sysauto-ask": {
      "command": "npx",
      "args": [
        "-y",
        "@rogeriolembo/server-sysauto-ask"
      ],
      "env": {
        "SYSAUTO_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
```

npm publish --access public
npm publish
npm package: @rogerioteixeira/uilibrary
Description: This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 1.6.0.
Latest version: 0.0.0

# UILibrary

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 1.6.0.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.

## Running unit tests

Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @rogerrogerio/n8n-nodes-rogerroger
Description: Interact with RogerRoger API for Person, Organization and Task resources
Author: RogerRoger
Latest version: 1.10.0

# n8n-nodes-rogerroger

This is an n8n community node. It lets you use RogerRoger in your n8n workflows.

RogerRoger is a collaborative task and communication platform designed to streamline workflows by turning emails and chats into actionable tasks for teams.

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

[Installation](#installation)  
[Operations](#operations)  
[Credentials](#credentials)  
[Compatibility](#compatibility)  
[Usage](#usage)  
[Resources](#resources)  
[Version history](#version-history)  

## Installation

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

## Operations

The node supports the following operations:

- Person
  - Get
  - Get many
  - Create
  - Update
  - Delete
- Organization
  - Get
  - Get many
  - Create
  - Update
  - Delete
- Task
  - Get
  - Get many
  - Create
  - Update
  - Delete

## Credentials

The node supports the API Key authentication method that is required to authenticate with the RogerRoger API.

## Compatibility

Tested against n8n version 1.95.3.

## Usage

1. **Generate an API Key**: Visit the [RogerRoger API Admin](https://app.rogerroger.io/admin/api) to create your API key.

2. **Set Up Credentials in n8n**:
   - Navigate to the RogerRoger node in your n8n workflow.
   - Create a new credential and enter the API key you generated.

3. **Select a Resource**:
   - Choose one of the available resources you want to interact with: Person, Organization, or Task.

4. **Choose an Operation**:
   - Select the operation you wish to perform (e.g., Get, Create, Update, Delete).
   - Provide the necessary data for the selected operation.

5. **Execute the Node**:
   - Run the node to perform the selected operations on the RogerRoger platform.

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/community-nodes/)
* [RogerRoger documentation](https://developer.rogerroger.io)

## Version history

- 1.0.0: Initial release
- 1.0.1: README updated
- 1.0.2:
	- Updated README
	- Chore: Moved repository to public Github
	- Text changes to improve consistancy between RogerRoger and N8N
	- Add fields "dueDate" and "organizations" to task resource
- 1.0.3:
	- Wrong path specified for node in package.json
- 1.0.4:
	- Wrong path to credentials file specified in package.json 
- 1.0.5:
	- Add credential test code
- 1.0.6:
	- Fix X-API-KEY header
- 1.0.7:
	- Update test endpoint
- 1.0.8:
	- Provide rules for credential test
- 1.0.9
	- Bump version
- 1.10.0
    - Added a resource locator to more easily find individual people, organizations, or tasks
    - Improved error reporting by using not only toast notifications but also the output window of n8n
    - Restructured and modularized the code to improve maintainability
    - Get many will now use "return all" and "limit" to provide a list of items