Skip to main content

Check out Port for yourself 

Prompts


Port allows you to centrally manage reusable prompts and expose them to your users via the MCP Server. Once defined, prompts become available in supported MCP clients (for example, Cursor or Claude) where developers and AI agents can discover and run them with the required inputs.

Common use cases​

  • Automate on-call runbooks and incident-triage guidance
  • Standardize code review or deployment checklists
  • Generate structured updates and communications (e.g., incident status, release notes)

Set up the data model​

  1. Go to the Builder page in your portal.

  2. Click + Blueprint.

  3. Click the {...} button in the top-right corner and choose Edit JSON.

  4. Paste the following JSON schema into the editor:

    Prompt blueprint JSON (click to expand)
    {
        "identifier": "prompt",
        "title": "Prompt",
        "icon": "Microservice",
        "ownership": {
            "type": "Direct",
            "title": "Owning Teams"
        },
        "schema": {
            "properties": {
                "description": {
                    "type": "string",
                    "title": "Description"
                },
                "arguments": {
                    "items": {
                        "type": "object",
                        "properties": {
                            "name": {
                                "type": "string",
                                "description": "The name of the argument parameter"
                            },
                            "description": {
                                "type": "string",
                                "description": "A description of what this argument is for"
                            },
                            "required": {
                                "type": "boolean",
                                "description": "Whether this argument is required or optional",
                                "default": false
                            }
                        },
                        "required": [
                            "name",
                            "description"
                        ]
                    },
                    "type": "array",
                    "title": "Arguments"
                },
                "template": {
                    "icon": "DefaultProperty",
                    "type": "string",
                    "title": "Prompt Template",
                    "format": "markdown"
                }
            },
            "required": [
                "description",
                "template"
            ]
        },
        "mirrorProperties": {},
        "calculationProperties": {},
        "aggregationProperties": {},
        "relations": {}
    }
Where prompts appear

After this blueprint exists and you create entities for it, prompts will show up in supported MCP clients connected to your Port organization. In clients that surface MCP prompts, you’ll see them listed and ready to run with arguments.

Create prompts​

Create entities of the prompt blueprint for each prompt you want to expose. At minimum, provide description and template. Optionally add arguments to parameterize the prompt.

  1. Go to the Prompts page in your portal.
  2. Click Create prompt.
  3. Fill out the form:
    • Provide a title and description.
    • Write the prompt template (supports markdown).
    • Define any arguments (optional) with name, description, and whether they are required.

Create prompt form in Port

Template and placeholders

The template supports markdown and variable placeholders. Each argument defined in arguments is exposed by its name and can be referenced as {{name}} inside the template. When you run the prompt, the MCP Server collects values for required arguments and substitutes them into the matching placeholders before execution.

Examples​

A prompt to assists on-call engineers by summarizing recent alerts and deploys related to an incident, then suggesting next steps and linking relevant runbooks.

Example prompt execution:

You are assisting with an incident in the payment-service service (production).
Incident ID: INC-2024-001

For the last 24 hours:
- Summarize critical alerts and recent deploys
- Suggest next steps and owners
- Link relevant dashboards/runbooks
Incident triage prompt entity JSON (Click to expand)
{
  "identifier": "incident_response_assistant",
  "title": "Incident Response Assistant",
  "team": [],
  "properties": {
    "description": "Assists with incident response by summarizing critical alerts, recent deploys, and suggesting next steps with relevant dashboards and runbooks",
    "arguments": [
      {
        "name": "service_name",
        "required": true,
        "description": "The name of the service experiencing the incident"
      },
      {
        "name": "environment",
        "required": false,
        "description": "The environment where the incident is occurring (e.g., production, staging)"
      },
      {
        "name": "incident_id",
        "required": true,
        "description": "The unique identifier for the incident"
      },
      {
        "name": "timeframe",
        "required": false,
        "description": "The time period to analyze (e.g., '24 hours', '1 week')"
      }
    ],
    "template": "You are assisting with an incident in the {{service_name}} service ({{environment}}).\nIncident ID: {{incident_id}}\n\nFor the last {{timeframe}}:\n- Summarize critical alerts and recent deploys\n- Suggest next steps and owners\n- Link relevant dashboards/runbooks"
  },
  "relations": {},
  "icon": "Microservice"
}

After creating entities, reconnect or refresh your MCP client; your prompts will be available and will prompt for any defined arguments.

See prompts in your client​

In Cursor, type / to open the prompts list. Selecting a prompt opens an input form for its arguments.

Prompt list in Cursor

When you select a prompt, Cursor renders fields for the defined arguments. Required ones are marked and must be provided.

Prompt argument input in Cursor