Scenext

You can run Scenext as an MCP server to automatically generate educational explanation videos based on topics. It supports a local UVX-based integration and a remote streamable HTTP endpoint, letting you choose the setup that fits your environment and access needs.

How to use

You connect an MCP client to Scenext in one of two ways. First, run a local UVX-based server that reads your configuration and starts the Scenext MCP runtime. Second, expose a remote HTTP endpoint that your MCP client can reach directly. In either case you provide an API key to authorize requests. If your client cannot set headers, you can configure the Authorization header manually on the client side.

How to install

Prerequisites you need before installing Scenext MCP Server: Node.js and npm (or other runtime tooling if you choose a non-Node path). You also need access to an API key for Scenext.

Step 1: Install the UVX tool globally so you can run local MCP servers.

Step 2: Create a local configuration file using the UVX mode shown below. This config enables the local MVP using the UVX runtime and sets your Scenext API key.

{
  "mcpServers": {
    "scenext": {
      "command": "uvx", 
      "args": ["scenext-mcp"],
      "env": {
        "SCENEXT_API_KEY": "your_actual_api_key_here"
      }
    }
  }
}

Additional setup and remote access

If you prefer remote access, you can expose a streamable HTTP endpoint. The configuration below enables a remote HTTP connection to Scenext MCP Server. Use your actual API key in place of the placeholder.

{
  "mcpServers": {
    "scenext": {
      "type": "streamable-http",
      "url": "https://mcp.scenext.cn/mcp/",
      "headers": {
        "Authorization": "Bearer your_actual_api_key_here"
      }
    }
  }
}

Notes on headers and security

Some MCP clients do not support the headers field. In that case, you can manually configure and add the request header Authorization=Bearer your_actual_api_key_here on the client side.

Configuration details and tips

The local UVX approach runs a self-contained MCP server on your machine, while the HTTP approach exposes a remote endpoint you can call from your MCP client. Choose the method that best fits your deployment, then supply your actual API key in the configuration.

Troubleshooting and notes

If you encounter issues connecting, verify that the API key is correct and that network access to the endpoint (for HTTP) or to the local UVX process (for local) is not blocked by a firewall or network policy. Ensure that the chosen method aligns with your client's capabilities regarding headers.