XenonFlare MCP Server
by Xenon-Flare
README.md
# XenonFlare MCP Server
[](https://www.npmjs.com/package/@xenonflare/mcp-server)
[](https://opensource.org/licenses/MIT)
[](https://github.com/Xenon-Flare/mcp-server/actions)
A Model Context Protocol (MCP) server for interacting with the **[XenonFlare API](https://xenonflare.com)**. This server allows AI assistants (like Claude) to manage your social media content, list channels, and automate media publishing directly from your chat interface.
---
## ๐ Features
- **Channel Management**: List connected social media accounts (Instagram, YouTube, TikTok, etc.).
- **Profile Management**: Manage account profiles (groups of accounts for focused posting).
- **Media Uploads**: Upload videos and images via URL with granular platform configurations.
- **Status Tracking**: Monitor the progress of your media uploads in real-time.
- **Content Management**: List and delete recent uploads directly through your AI assistant.
---
## ๐ Resources
- **Main Website**: [xenonflare.com](https://xenonflare.com)
- **Documentation**: [docs.xenonflare.com](https://docs.xenonflare.com)
- **API Reference**: [docs.xenonflare.com/api-reference](https://docs.xenonflare.com/api-reference)
- **Developer Dashboard**: [xenonflare.com/developer/api-keys](https://xenonflare.com/developer/api-keys)
---
## ๐ฆ Installation
### For Users (Claude Desktop)
1. Get your **XenonFlare API Key** from the [XenonFlare Dashboard](https://xenonflare.com/developer/api-keys).
2. Open your Claude Desktop configuration file:
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
3. Add the XenonFlare MCP server to the `mcpServers` object:
```json
{
"mcpServers": {
"xenonflare": {
"command": "npx",
"args": ["-y", "@xenonflare/mcp-server"],
"env": {
"XENONFLARE_API_KEY": "your_api_key_here"
}
}
}
}
```
### For Developers
1. **Clone the repository**:
```bash
git clone https://github.com/Xenon-Flare/mcp-server.git
cd mcp-server
```
2. **Install dependencies**:
```bash
npm install
```
3. **Build the project**:
```bash
npm run build
```
4. **Run locally**:
- Create a `.env` file based on `.env.example`:
```bash
cp .env.example .env
```
- Add your `XENONFLARE_API_KEY` to the `.env` file.
- Start the server:
```bash
npm start
```
---
## ๐ Available Tools
- `list_channels`: List connected social accounts.
- `list_profiles`: List account profiles.
- `upload_video`: Upload a video via URL.
- `upload_image`: Upload an image via URL.
- `get_video_status`: Get status for a specific video.
- `get_image_status`: Get status for a specific image.
- `list_videos`: List recent video uploads.
- `list_images`: List recent image uploads.
- `delete_video`: Delete a video upload.
- `delete_image`: Delete an image upload.
---
## โ๏ธ Configuration
The server expects the following environment variables:
- `XENONFLARE_API_KEY`: Your XenonFlare API key (**Required**).
- `XENONFLARE_API_URL`: The XenonFlare API base URL (Optional, defaults to `https://api.xenonflare.com`).
---
## ๐ License
MIT ยฉ [XenonFlare](https://xenonflare.com)
TDQS
B3.3/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct resource (image, video, channel, profile) and action (delete, get status, list, upload), with no overlapping purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with underscores (e.g., delete_image, list_channels, upload_video).
Tool Count5/5
10 tools cover the core upload, delete, status, and list operations for images and videos, plus listing channels and profilesโwell-scoped for the server's purpose.
Completeness4/5
Covers all major operations for image/video management (CRUD except update, which is typical for immutable uploads), but lacks individual get for channels and profiles (only list provided).