Quark Auto-Save MCP Server
by tnnevol
README.md
# Quark Auto-Save MCP Server
An MCP (Model Context Protocol) server that integrates with quark-auto-save service to automate file saving from Quark Cloud Drive shares.
## Features
- Add auto-save tasks to quark-auto-save service
- Get and update configuration
- Run tasks immediately
- Secure authentication via token
## Installation
```bash
npm install
```
## Usage
```bash
npm start
```
### Environment Variables
- `QAS_BASE_URL`: Base URL of the quark-auto-save service (optional, can be passed to each tool)
- `QAS_TOKEN`: Authentication token for the quark-auto-save service (optional, can be passed to each tool)
## Available Tools
### `add_task`
Add a new auto-save task to quark-auto-save service.
Parameters:
- `baseUrl`: Base URL of the quark-auto-save service
- `token`: Authentication token
- `taskname`: Name of the task
- `shareurl`: Quark share URL
- `savepath`: Path to save in the cloud drive
- `pattern`: File matching regex pattern (optional)
- `replace`: Rename replacement rule (optional)
### `get_config`
Get the overall configuration from quark-auto-save service.
Parameters:
- `baseUrl`: Base URL of the quark-auto-save service
- `token`: Authentication token
### `update_config`
Update the overall configuration of quark-auto-save service.
Parameters:
- `baseUrl`: Base URL of the quark-auto-save service
- `token`: Authentication token
- `config`: Configuration object to update
### `run_tasks`
Run auto-save tasks immediately.
Parameters:
- `baseUrl`: Base URL of the quark-auto-save service
- `token`: Authentication token
- `taskData`: Task data to run (if null/undefined, runs all tasks)
## Security Notice
Never hardcode credentials in configuration files. Always use environment variables or secure credential management systems.