Skip to content

Update zapier power: refresh POWER.md and add MCP transport type#155

Open
BenMcGit wants to merge 1 commit into
kirodotdev:mainfrom
BenMcGit:update-zapier-power-manifest
Open

Update zapier power: refresh POWER.md and add MCP transport type#155
BenMcGit wants to merge 1 commit into
kirodotdev:mainfrom
BenMcGit:update-zapier-power-manifest

Conversation

@BenMcGit

Copy link
Copy Markdown

Summary

Refreshes the existing zapier power manifest to match the source of truth at zapier/zapier-mcp. The local-to-Kiro steering/ files are already identical and are not touched.

POWER.md

  • Adds a When to Use This Power section with explicit user-intent triggers — sending messages, creating records, naming a specific app, auditing actions, or generating a tools profile. Gives Kiro a clearer signal for when to activate the power.
  • Reformats the Available Steering Files list as a table with file paths, so Kiro can resolve link destinations directly. The four existing steering files (zapier-setup, zapier-status, create-my-tools-profile, zapier-lifecycle) are all preserved.
  • Tightens Connection / Authorization formatting in the Onboarding and MCP Servers sections.
  • Promotes per-mode tool sections to #### sub-headings so they render in GitHub's outline.
  • Corrects the license note (the plugin distribution is MIT-licensed, not Apache-2.0).

mcp.json

  • Adds "type": "http" alongside the URL so the transport is explicit per the MCP spec. The hosted server (https://mcp.zapier.com/api/v1/connect) is unchanged.

Source

Generated from zapier/zapier-mcp/tree/main/zapier-power (the upstream repo for the Zapier MCP plugin distribution).

Testing

  • POWER.md frontmatter unchanged (name, displayName, description, keywords, author)
  • All steering file links resolve (zapier-setup.md, zapier-status.md, create-my-tools-profile.md, zapier-lifecycle.md)
  • mcp.json is valid JSON
  • No changes to steering files (verified identical to upstream)

POWER.md changes (synced from zapier/zapier-mcp source repo):

- Add "When to Use This Power" section with explicit user-intent
  triggers (sending messages, creating records, app names, audit/
  enable requests, tools-profile generation)
- Switch the Available Steering Files list to a table that names the
  file, its path, and its purpose — discoverable at a glance
- Tighten the Connection/Authorization formatting in the Onboarding
  and MCP Servers sections
- Promote per-mode tool sections to h4 sub-headings
- Correct license note (MIT, not Apache-2.0)

mcp.json:

- Add "type": "http" alongside the URL so the transport is explicit
  per the MCP spec, matching the format other powers in this repo
  use for HTTP-based MCP servers

Source of truth: https://github.com/zapier/zapier-mcp/tree/main/zapier-power
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