Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

2.7 KB
Raw Blame
# MCP tool definitions. Tools are opt-in: an operation is exposed only when it has an entry here.
# List operations without an entry: pnpm --filter=@posthog/mcp run scaffold-yaml -- --candidates --product field_notes
# Add one: pnpm --filter=@posthog/mcp run scaffold-yaml -- --add <operationId> --product field_notes
# To keep an operation off on purpose, set enabled: false and give a disabled_reason.
category: Field notes
feature: field_notes
url_prefix: /
ui_apps: {}
tools:
    field-notes-get:
        operation: field_notes_retrieve
        enabled: true
        scopes:
            - field_note:read
        annotations:
            readOnly: true
            destructive: false
            idempotent: true
        title: Get field note
        description: >
            Get a single field note by id, including the full element context (selector, element chain, inferred
            selectors, attributes) needed to locate the element in code.
        feature_flag: field-notes
    field-notes-list:
        operation: field_notes_list
        enabled: true
        scopes:
            - field_note:read
        annotations:
            readOnly: true
            destructive: false
            idempotent: true
        list: true
        title: List field notes
        description: >
            List UI field notes a user made with the PostHog toolbar on their own site. Each field note is feedback
            pointed at a specific page element — comment, CSS selector, page URL, host, and optional screenshot. Filter
            by `field_note_status` (pending, acknowledged, resolved, dismissed) to find unaddressed feedback, or by
            `host` to scope to one site. Use this to pick up pending design/UX feedback to act on.
        feature_flag: field-notes
        response:
            include:
                - id
                - comment
                - field_note_status
                - resolution
                - url
                - host
                - pathname
                - selector
                - element_text
                - screenshot_url
                - created_at
                - created_by
    field-notes-partial-update:
        operation: field_notes_partial_update
        enabled: true
        scopes:
            - field_note:write
        annotations:
            readOnly: false
            destructive: false
            idempotent: true
        title: Update field note
        description: >
            Update a field note after acting on it — set `field_note_status` to `acknowledged`, `resolved`, or
            `dismissed`, and optionally add a `resolution` note describing what changed. Send only the fields you want
            to change.
        feature_flag: field-notes