Copying endpoints across projects

This skill duplicates a PostHog endpoint — a saved HogQL or insight query exposed as a callable API route — either into another project in the same organization, or under a new name in the same project.

The one thing to know first

There is no server-side endpoint copy operation. Feature flags have feature-flags-copy-flags-create and experiments have experiment-copy-to-project; endpoints have neither. Copying an endpoint means:

1. Read the full source config with endpoint-get.
2. Recreate it with endpoint-create (in the target project, or under a new name in the same project).

Both endpoint-get and endpoint-create operate only on the active MCP project — neither takes a project id. So a cross-project copy requires the active project to be switched between the read (source) and the write (target). Read the source first, capture the config, then switch to the target and create. If you cannot switch projects in this session, tell the user rather than creating the copy in the wrong project.

When to use this skill

• "Copy this endpoint to another project", "duplicate this endpoint", "clone the endpoint"
• "Promote the endpoint from staging to production" (projects-as-environments)
• "Make a copy so I can iterate without touching the live one" (same-project duplicate under a new name)
• Replicating an endpoint's query, variables, and freshness config in a different workspace