Skip to main content
Pulumi logo Pulumi logo
  1. Docs
  2. Infrastructure AI
  3. Reference
  4. MCP server tools

Pulumi MCP server tools and prompts

    The Pulumi MCP server exposes the following tools and prompts to your agent. For what each tool needs from your organization and what it can cost, see Costs and edition requirements.

    Tools

    You don’t call these tools directly: describe what you want and your agent picks the tool. The names matter when your agent asks you to approve a tool call and when you allow or deny tools in its settings.

    Pulumi Cloud

    ToolDescription
    get-stacksList the stacks in your organization.
    resource-searchSearch resources across all stacks using resource search queries, such as package:aws or -.tags: (resources without tags).
    get-policy-violationsList policy as code violations for your stacks.
    get-usersList the members of your organization and their roles.

    Neo

    ToolDescription
    neo-bridgeStart a Neo task, send it follow-up messages, and approve or reject its requests. Returns a link to the task in the Pulumi Cloud console.
    neo-get-tasksList your organization’s Neo tasks and their status.
    neo-continue-taskCheck the status of an existing task and read its latest events.
    neo-reset-conversationClear the server’s tracked state for a task, or for all tasks.

    Pulumi Registry

    ToolDescription
    list-resourcesList the resource types in a provider or module.
    list-functionsList the functions in a provider or module.
    get-resourceGet a resource’s properties and documentation.
    get-functionGet a function’s inputs, outputs, and documentation.
    get-typeGet the JSON schema for a type reference.

    Code generation

    ToolDescription
    deploy-to-awsReturn step-by-step instructions the agent follows to analyze your application and write Pulumi code that deploys it to AWS.

    Prompts

    Prompts are reusable instructions your agent can load, usually from a slash-command or prompt menu:

    • deploy-to-aws: deploy application code to AWS by generating a Pulumi program.
    • convert-terraform-to-typescript: convert Terraform HCL to a Pulumi TypeScript program.
    • cdk-migration-plan: plan a migration from the AWS CDK to Pulumi.
    • cdk-migration-automated: migrate a CDK app to Pulumi with automated conversion.
    • cdk-migration-manual: migrate a CDK app to Pulumi by hand.
    • cdk-migration-troubleshoot: troubleshoot a CDK-to-Pulumi migration.

      The infrastructure as code platform for any cloud.