Runway MCP for Grok Bot: what shipped and what Sume lists

Runway's changelog lists "Runway MCP for Grok Bot" on Sep 17, 2026 as a plugin in Grok Bot, marked Paid. Sume's docs name Cursor, Claude Code and Codex as clients of its hosted MCP endpoint and do not mention Grok Bot, so whether that bot can connect to Sume is not something the docs promise.

What exactly did Runway announce?

One line on Runway's changelog, read 2026-09-29: dated Sep 17, 2026, tagged Paid, describing a plugin in Grok Bot. The entry gives no tool list, credit costs or setup steps, so none appear here. Runway's own pages remain the place to check what the plugin can generate.

Can Grok Bot use Sume's MCP for video?

Sume's docs say to use its endpoint, https://mcp.sume.com/mcp, "in Cursor, Claude Code, Codex, and other remote MCP clients". Grok Bot is not named, and the docs describe no Grok Bot setup. Treat it as untested rather than as supported or unsupported.

What the docs do define is what a client must do. Test a client against that list before you spend time on a video prompt.

How do I test a client without generating anything?

First, check the public discovery document that OAuth clients read. It is documented and needs no login:

• If the client can add a remote HTTP MCP server and finish the OAuth sign-in, ask it to call mcp_health or tools_list. Both are read-only.
• Keep the default read-only consent. Paid tools such as generate_video stay blocked with insufficient_scope until you opt in to write.
• If the client cannot do OAuth, the docs describe an API-key path with the full tool set. Keep that key out of chat.

curl https://mcp.sume.com/.well-known/oauth-protected-resource/mcp

What if the bot has no MCP support I can use?

Skip MCP and call the REST API from your own code. POST /v1/videos returns a job id and a polling URL, and GET /v1/videos/{jobId}/content downloads the file once the job is completed; see video generation for the request fields. A bot that can run a shell command or make an HTTP call can drive that flow, and your own script owns the key.

What should I not assume between two MCP servers?

Do not assume the tools match. Runway's changelog entry says nothing about tools, and Sume's own hosted MCP is described as not full parity with the HTTP API: Sume Image 1.0 and Video 1.0 (images_create and videos_create) are REST-only, and the live tool list is whatever tools_list returns in your session. Ask the bot to list tools on each server before you write a prompt that depends on one.

Also do not assume that a paid Runway plan covers anything on Sume. The two are separate accounts, sign-ins and bills; Sume's paid calls are gated by wallet admission, not by an OAuth scope.