Xenonflare Mcp Server

Created By
Xenon-Flare3 months ago
A Model Context Protocol (MCP) server for interacting with the XenonFlare API. This server allows AI assistants (like Claude) to manage your social media content, list channels, and automate media publishing directly from your chat interface.
Overview

XenonFlare MCP Server

NPM Version License: MIT Build Status

A Model Context Protocol (MCP) server for interacting with the XenonFlare API. 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


📦 Installation

For Users (Claude Desktop)

  1. Get your XenonFlare API Key from the XenonFlare Dashboard.
  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:
{
  "mcpServers": {
    "xenonflare": {
      "command": "npx",
      "args": ["-y", "@xenonflare/mcp-server"],
      "env": {
        "XENONFLARE_API_KEY": "your_api_key_here"
      }
    }
  }
}

For Developers

  1. Clone the repository:
    git clone https://github.com/Xenon-Flare/mcp-server.git
    cd mcp-server
    
  2. Install dependencies:
    npm install
    
  3. Build the project:
    npm run build
    
  4. Run locally:
    • Create a .env file based on .env.example:
      cp .env.example .env
      
    • Add your XENONFLARE_API_KEY to the .env file.
    • Start the server:
      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

Server Config

{
  "mcpServers": {
    "xenonflare": {
      "command": "npx",
      "args": [
        "-y",
        "@xenonflare/mcp-server"
      ],
      "env": {
        "XENONFLARE_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Xenon-Flare
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago