Kiwi

Kiwi for Vercel

Have the agent on a Kiwi step check a Vercel preview deployment and read its runtime logs, through Vercel's MCP server.

  • Your agent works in Vercel through its own connection. Kiwi does not call Vercel and never holds its credentials.
  • A workflow skill can list Vercel among the tools it requires. When you supply your agent's available tools to a skill check and Vercel is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Vercel, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Vercel connection, with report_configuration.
  • The agent submits links to its work in Vercel as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Vercel

  • List a project's deployments and read the details of one.
  • Fetch a deployment's URL to check the page it serves.
  • Read a deployment's runtime logs and runtime errors.
  • List the teams and projects the signed-in account can access.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

  2. Connect your agent to Vercel

    Add the Vercel MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.vercel.com
  3. Example skill

    Publish instructions like these as a workflow skill that lists Vercel among its required tools.

    Start from the pull request named in the step's inputs.
    Find its Vercel preview deployment and fetch the pages listed in the
    assignment to check that they load.
    Read the deployment's runtime errors for the same period.
    Submit the preview URL and any error messages as the step's outputs.
    Promoting to production is for the run's Owner.
    If the preview build failed, report a blocker.