Skip to content

Add Cloudinary power for Kiro#1

Open
eitanp461 wants to merge 5 commits into
mainfrom
add-cloudinary-power
Open

Add Cloudinary power for Kiro#1
eitanp461 wants to merge 5 commits into
mainfrom
add-cloudinary-power

Conversation

@eitanp461

Copy link
Copy Markdown
Collaborator

Initial release of the Cloudinary power for Kiro — connects Kiro to Cloudinary for uploading, transforming, optimizing, managing, and AI-analyzing images and videos.

What's here

cloudinary/            <- import this folder in Kiro
|-- POWER.md           <- manifest: keywords, onboarding, MCP server + tool tables, troubleshooting
|-- mcp.json           <- four remote Cloudinary MCP servers (OAuth, bare url entries)
`-- steering/
    |-- upload.md
    |-- transformations.md
    |-- asset-management.md
    |-- analysis.md
    `-- account-provisioning.md

Highlights

  • Four remote MCP servers over OAuth — asset-management, environment-config, structured-metadata, analysis. No API keys pasted into config; the user signs in via browser and selects a product environment.
  • Steering files distilled from Cloudinary docs: upload strategy, transformation/optimization URL rules, search & asset management, and AI media analysis.
  • Agentic account provisioning — users without a Cloudinary account can have one created from their email and claim it via email verification, then connect via OAuth. Root credentials are redacted at the tool boundary so they never enter the transcript.
  • Convention-aligned with the official kirodotdev/powers set: power lives in a folder named after it, 5-field frontmatter, Overview / Available MCP Servers (with exact tool names) / Troubleshooting / License & Support sections, onboarding written as tool-availability detection with a read-only connectivity check.

Testing

  • Verified all four servers connect via OAuth in Kiro locally (after the MCP servers' WWW-Authenticate 401 fix shipped).
  • Exercised upload, transformation, and search workflows end-to-end.

Notes for review

  • Ready for submission to https://kiro.dev/powers/submit once merged.
  • Please confirm the four MCP servers are GA (not beta/preview) — submission criteria reject preview-status dependencies.

🤖 Generated with Claude Code

eitanp461 and others added 5 commits July 7, 2026 14:21
OAuth-connected remote MCP servers (asset management, environment config,
structured metadata, analysis), steering files for upload, transformations,
asset management, analysis, and agentic account provisioning per AUTH.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Power files now live in cloudinary/ so the imported folder name matches
  the power name (Kiro labels local imports by directory name)
- mcp.json: bare url entries (Kiro handles OAuth/DCR; oauthScopes is not
  part of the powers schema — no official power uses it)
- POWER.md: add Overview, Available MCP Servers with exact tool names,
  MCP Configuration, Troubleshooting, and License/Support sections;
  rewrite onboarding as tool-availability detection with a read-only
  connectivity check; trim keywords to 7 per power-builder spec
- account-provisioning: redact root credentials at the tool boundary
- analysis: correct task-polling tool name (tasks-get-status)
- add MIT LICENSE

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Cross-checked steering/manifest against current Cloudinary docs and corrected:

- transformations.md: remove non-existent c_lfit crop mode; fold its
  behavior into c_limit (fit-but-only-scales-down)
- upload.md: correct overwrite default (signed uploads default to true,
  not "don't clobber"); add missing '+' to public_id forbidden chars
- POWER.md/README.md: soften "Cloudinary's four MCP servers" phrasing
  (more servers exist); this power wires up four of them
- POWER.md/account-provisioning.md: drop undocumented token-lifecycle and
  "MCP-only" claims; note non-Analysis servers also support API-key auth
- account-provisioning.md: replace fabricated provisioning error
  codes/messages with the three documented cases (400/403/429), correct
  the error envelope, add disposable-email restriction

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Replace the fabricated `mcp_auth` agent action (onboarding + troubleshooting)
  with Kiro's real OAuth flow: browser auth opened automatically on connect
  (DCR), with the MCP-panel connect/Re-authenticate button or `/mcp auth`
  command as the user-driven fallback. There is no agent-invocable mcp_auth
  tool in Kiro.
- Correct the environment-config tool description: the create/list/update/delete
  pattern is uniform, but read tools are not — get-transformation-details,
  get-upload-preset-details, get-streaming-profile, and no get for
  upload-mappings or triggers.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@eitanp461 eitanp461 requested a review from njb90 July 8, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant