Claude Code 2.1.289 plugin loading fix: recheck Sume MCP after upgrade

After upgrading Claude Code, confirm Sume with mcp_health and tools_list before any paid call. Version 2.1.289 (Oct 3, 2026) fixed plugin loading after an upgrade, according to the Claude Code changelog, but a read-only check costs nothing and tells you the real state.

This is the short sequence Sume's docs recommend for verifying a new connection.

Reconnect if needed

If the server is missing after the upgrade, add it again and sign in. These are the two commands from the Sume quickstart.

claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sume

The four-call check

Ask the agent to call mcp_health first and confirm that authenticated.auth_source is mcp_oauth when you connected with OAuth.

Read the tool list as a scope test

The tool list is also the quickest way to see which scope you hold. Default hosted OAuth grants mcp:read only, so mutating and paid tools stay hidden. If you expect to run generate_image or jobs_cancel and they are missing, the session probably lacks mcp:write.

With read-only scope, calling a write or paid tool by name returns insufficient_scope instead of running. Grant Write on the consent page, use an API-key session, or use the Developer API or CLI for those calls.

Before the first paid call

Once the connection is verified, do one more free step before real spend.

• Call tools_schema with name set to the tool you plan to use, such as generate_image.
• Call the tool with dry_run=true, or call generation_admission_preview, and read the estimate.
• Submit with a fresh idempotency_key. Add max_spend_usd if you want a cap.
• Wait with jobs_wait in slices of at most 55 seconds, then read jobs_result.

If jobs were running during the upgrade

Restarting a client does not stop a job that Sume has accepted. Jobs are durable, and reading jobs_list or jobs_status with the ids you stored shows where each one stands. Do not resubmit a paid request because your session was interrupted.