open-index/open-npm huggingface dataset:
npm package: @snuxoll/astro-picture
Description: ```sh npm create astro@latest -- --template minimal ```
Latest version: 0.0.1

# Astro Starter Kit: Minimal

```sh
npm create astro@latest -- --template minimal
```

[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/withastro/astro/tree/latest/examples/minimal)
[![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/sandbox/github/withastro/astro/tree/latest/examples/minimal)
[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/withastro/astro?devcontainer_path=.devcontainer/minimal/devcontainer.json)

> 🧑‍🚀 **Seasoned astronaut?** Delete this file. Have fun!

## 🚀 Project Structure

Inside of your Astro project, you'll see the following folders and files:

```text
/
├── public/
├── src/
│   └── pages/
│       └── index.astro
└── package.json
```

Astro looks for `.astro` or `.md` files in the `src/pages/` directory. Each page is exposed as a route based on its file name.

There's nothing special about `src/components/`, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.

Any static assets, like images, can be placed in the `public/` directory.

## 🧞 Commands

All commands are run from the root of the project, from a terminal:

| Command                   | Action                                           |
| :------------------------ | :----------------------------------------------- |
| `npm install`             | Installs dependencies                            |
| `npm run dev`             | Starts local dev server at `localhost:4321`      |
| `npm run build`           | Build your production site to `./dist/`          |
| `npm run preview`         | Preview your build locally, before deploying     |
| `npm run astro ...`       | Run CLI commands like `astro add`, `astro check` |
| `npm run astro -- --help` | Get help using the Astro CLI                     |

## 👀 Want to learn more?

Feel free to check [our documentation](https://docs.astro.build) or jump into our [Discord server](https://astro.build/chat).
npm package: @snvshal/sndo
Description: `sndo` is a **Model Context Protocol (MCP) server** that securely exposes a user’s personal context (areas, tasks, notes, achievements) via **API key–based access**, designed for AI agents and MCP-compatible clients.
Latest version: 1.0.1

# sndo

`sndo` is a **Model Context Protocol (MCP) server** that securely exposes a user’s personal context (areas, tasks, notes, achievements) via **API key–based access**, designed for AI agents and MCP-compatible clients.

---

## Requirements

- **Node.js 18+** or **Bun** (recommended)
- An API key generated from
  👉 [https://sndo.vercel.app](https://sndo.vercel.app)

---

## Installation

```bash
npm install -g @snvshal/sndo
# or
bun add -g @snvshal/sndo
```

---

## MCP Client Configuration

`sndo` communicates over **stdio**, as required by MCP-compatible clients.

### Option 1: Global installation (recommended)

If installed globally, use the `sndo` binary directly:

```json
{
  "mcpServers": {
    "sndo": {
      "name": "sndo",
      "command": "sndo",
      "args": [],
      "env": {
        "SNDO_API_KEY": "your_sndo_api_key_here"
      }
    }
  }
}
```

### Option 2: No global installation (via npx / bunx)

If you don’t want a global install, run via `npx` (Node) or `bunx` (Bun):

```json
{
  "mcpServers": {
    "sndo": {
      "name": "sndo",
      "command": "npx",
      "args": ["-y", "@snvshal/sndo"],
      "env": {
        "SNDO_API_KEY": "your_sndo_api_key_here"
      }
    }
  }
}
```

> **Recommendation:** Use **Option 1** when possible.
> Use **Option 2** for quick setup or sandbox environments.

---

## Authentication

`sndo` uses **Bearer API keys**.

Provide your API key via environment variable:

```bash
export SNDO_API_KEY=your_api_key_here
```

or directly inside your MCP client configuration.

---

## MCP Tools

### Context

- **`get_context`**

  - Returns:

    - Areas
    - Tasks
    - Notes
    - Last updated timestamps

### Achievements

- **`get_achievements`**

  - Fetch achievements
  - Defaults to **today**
  - Supports date filtering

- **`add_achievement`**

  - Add a new achievement
  - Optional note support (appends, not overwrites)

---

## API Scopes

API keys use **fine-grained scopes** for access control.

### Supported Scopes

- `mcp:areas:read`
- `mcp:achievements:read`
- `mcp:achievements:write`

Scopes are validated on every request.
Missing scopes result in **`403 Forbidden`**.

You can manage scopes per API key from the dashboard:
👉 [https://sndo.vercel.app/api-keys](https://sndo.vercel.app/api-keys)

---

## Security Notes

- API keys are **hashed at rest**
- API usage is **tracked per key and per endpoint**
- Keys can be **revoked instantly**
- **Never** commit API keys to source control

---

## License

MIT