PeerPush

OpenQuok MCP examples for PeerPush directory launch — profiles, peerpush variants, listing readiness, and cached directory SEO.

3 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start your free trial

Directory launch quick reference

Property	Value
Directory site key	peerpush
Submit host	peerpush.com (you click submit on PeerPush — OpenQuok autofills)
Integration docs	PeerPush directory integration
Tools reference	Directory launch tools

Note

These tools manage product profiles and launch readiness. They do not publish to PeerPush for you. After directoryVariantsEnsure tailors copy, use the browser extension to open peerpush.com and submit.

Plan capabilities

Directory launch tools need directory_launch_enabled on the workspace plan. Directory SEO tools need directory_seo_enabled.

List PeerPush destinations

Which PeerPush launch paths are in the OpenQuok catalog right now?

The agent calls directoryDestinationsList and filters rows where the provider slug is peerpush (Standard launch and free queue variants when published).

Main profile and PeerPush variant

Create or open my PeerPush-tailored product profile from my main business profile, and tell me how similar it is to the main profile.

Alternate wording (same tool chain):

List my main product profile, ensure a PeerPush variant exists, and tell me how similar the variant is to the main profile.

The agent should:

Call directoryProfilesList with mainOnly: true and read productProfileId from the first row.
Call directoryVariantsEnsure with that id and directorySiteKey: peerpush.

{
  "mainProductProfileId": "<main-product-profile-id>",
  "directorySiteKey": "peerpush"
}

Idempotent variant

directoryVariantsEnsure returns the existing variant with created: false when one already exists for peerpush.

Use directoryProfilesGet on the main or variant id when you need full profileData or similarityToMainPercent.

Listing readiness before you open peerpush.com

For my main product profile, show PeerPush readiness — submission status and any missing fields.

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directoryListingSummary and reads the peerpush destination row (counts, submissionStatus, readiness gaps).

Fill in my PeerPush profile tagline and description from this draft copy.

Call directoryProfilesUpdate with the variant productProfileId from directoryVariantsEnsure and the fields to patch (tagline, description, or profileData keys).

Logo and screenshots

Set my PeerPush profile logo and up to three screenshot URLs before I open peerpush.com.

The agent should call directoryProfilesUpdate on the main or variant productProfileId with logoUrl and profileData.gallery_urls (max 3 entries). Use public https:// URLs directories and the extension can fetch.

Optional: uploadFromUrl imports a remote image into the workspace media library (same idea as CLI upload-from-url). That does not attach the file to the product profile automatically — still patch logoUrl / gallery_urls with the public URLs you want on the listing. Local files need CLI openquok upload when the agent can run shell commands.

Profile media vs post media

Uploading logo and screenshots in My Products uses the profile-media flow in the app. MCP and CLI directory tools set URL fields on the profile row instead.

CLI equivalent: Directory launch — logo and screenshots.

Submissions (read-only)

List directory submissions recorded for my main product profile.

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directorySubmissionsList (optional destinationId filter when you care about one site).

Directory SEO (cached metrics)

What are my directory SEO ratings for my main profile, and when were they last checked?

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directorySeoOverview. Read checkedAt on each metric and manualRefreshAvailableAt before directorySeoRefresh.

Show domain rating history for the last 90 days for my main product profile.

Call directorySeoHistory with productProfileId and days: 90.

End-to-end workflow

Prepare my product for PeerPush: ensure the peerpush variant, show PeerPush readiness on the listing summary, and give me the latest cached domain rating with checkedAt.

The agent chains directoryProfilesList → directoryVariantsEnsure (peerpush) → directoryListingSummary → directorySeoOverview.