Can Google Jules use Sume's MCP server? Not yet: use the REST API

Based on Jules's own changelog, you cannot point Google Jules at Sume's hosted MCP server today. Jules added MCP on 2 February 2026 with a fixed list of six servers (Linear, Stitch, Neon, Tinybird, Context7 and Supabase), authenticated by API key, and the entry says the list is limited on purpose. Sume is not on it. If a Jules task needs a Sume video, image or voice, have the task call the Sume REST API at https://api.sume.com/v1 with a key kept in the environment.

This note is a snapshot from the Jules changelog read on 2026-10-13. The newest entry on the changelog index is dated 9 March 2026, and none of the entries after the MCP one mention adding servers. If Jules later opens a custom-server field, the Sume side is ready: hosted MCP lives at https://mcp.sume.com/mcp.

What does Jules say about MCP servers?

The 2 February 2026 entry describes a five-step setup: get the service's API key, open Jules Settings, find the MCP section, enter the key, and start a new session. Jules then calls the server's tools when it decides a task needs them.

The same entry explains that servers are hand-selected. Jules validates data flow, audits tool permissions and checks stability, because it runs in a cloud environment connected to your GitHub repositories. It also says people can ask for more integrations from the settings panel.

Why does Sume's hosted MCP not fit that model?

Sume's hosted MCP accepts OAuth tokens or Sume API keys. OAuth tokens and API keys are not interchangeable, and an OAuth session sees only read-only tools unless the user turns on the write scope at consent. An API key sees the full tool set, and every paid or write call must carry an idempotency key.

Because a Jules entry is a plain API key for a listed service, a Sume connection would need Jules to list Sume first. Nothing on the Jules page lets you type a server URL yourself, so do not rely on a workaround.

What should a Jules task do instead?

Sume's Developer API is key-authenticated and workspace-scoped. Create a key in the dashboard, store it as a secret in the environment your task runs in, and let the task submit work and read the job. Generation endpoints create durable jobs, so a task should store the job id and poll status rather than hold one long connection.

A first smoke test confirms the key and workspace before any paid call:

For shell-based agents, the Sume CLI is also a supported path besides direct HTTP calls.

• Do not write the key into the repository or the task prompt; keep it in the secret store the environment provides.
• Send the same idempotency key when you retry a submit, so a retried task does not pay twice.
• Read job status until it is completed, failed or canceled, then fetch the result; media URLs come back on media.sume.com.

export SUME_API_KEY="sume_live_..."

curl https://api.sume.com/v1/me \
  -H "Authorization: Bearer $SUME_API_KEY"

When would MCP be the better route?

If your assistant is Cursor, Claude Code, Codex or another client that accepts a remote MCP URL with a header or OAuth, use hosted MCP: the client discovers the tools itself and you write no HTTP code. For Jules, the REST API is the route that works with what its changelog documents today.