Plainly's Official

Model Context Protocol (MCP) server for video automation with Plainly Videos API (Adobe After Effects automation).

typescript

5

GitHub Stars

typescript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "plainly-videos-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@plainly-videos/mcp-server@latest"
      ],
      "env": {
        "PLAINLY_API_KEY": "<PLAINLY_API_KEY>"
      }
    }
  }
}

You can run the Plainly MCP Server to connect LLM clients with Plainly APIs. It lets clients issue requests to Plainly and receive renderable results, enabling integration with your preferred MCP client and workflow.

How to use

Start the MCP server using your preferred setup. The simplest method runs the MCP server through a package runner, fed with your API key. You can also run it in development mode after building the project for local testing.

How to install

Prerequisites you need before installing the MCP server are Node.js version 18 or higher, npm, and a Plainly account to obtain an API key.

{
  "servers": {
    "plainly": {
      "command": "npx",
      "args": ["-y", "@plainly-videos/mcp-server@latest"],
      "env": {
        "PLAINLY_API_KEY": "<PLAINLY_API_KEY>"
      }
    }
  }
}

Optionally, you can install and configure via the Smithery workflow. This installs the MCP server through the Smithery CLI by selecting your MCP client and supplying your Smithery API key.

npx -y @smithery/cli@latest install @plainly-videos/mcp-server --client claude --key <YOUR_SMITHERY_KEY>

For development builds and local testing, follow these steps to clone the project, install dependencies, and build the dist artifacts. After building, you can start the server from the generated dist/cli.js.

git clone git@github.com:plainly-videos/mcp-server.git
cd mcp-server

yarn install
yarn build

{
  "servers": {
    "plainly": {
      "command": "node",
      "args": ["<FULL PATH TO dist/cli.js>"],
      "env": {
        "PLAINLY_API_KEY": "<PLAINLY_API_KEY>"
      }
    }
  }
}

Start the MCP server from your editor’s MCP configuration or by running the start command defined in your setup after building. If you used the development flow, the command points to the built dist/cli.js file.

Additional notes

Environment variable requirements are shown for the MCP configs. Ensure you replace placeholders with your actual keys. Both the production and development paths require the same API key to authorize requests to Plainly.

Troubleshooting tips

If the server fails to start, verify that Node.js is at least v18, your API key is valid, and the dist/cli.js path exists after building. Check that the environment variable is correctly set in your MCP configuration.

Available tools

list_renderable_items

Returns a list of all criteria matching designs and custom projects for the authenticated user.

get_renderable_items_details

Returns detailed information about a single design or project, including required and optional parameters, previews, and aspect ratios.

render_item

Submits a render task with all needed parameters to produce the requested item.

check_render_status

Checks the status of a render and provides either an error, a preview link, or final results.