Your Ping matches, in your AI assistant.

Ping’s MCP server gives your assistant read access to your stored job matches and employer listings. Ask it to compare roles, explain recorded match reasons or review saved opportunities with you.

Read the setup guide Create your brief

Connection setup is under verification. The client instructions below are configuration previews.

Ping MCP conversationIllustrative example

Show my saved matches and flag any pay details I still need to confirm.

Example toolslist_matchesget_match

Senior Product Designer

The recorded result supports product design and remote work from Germany. Annual base pay is unconfirmed in this fictional posting.

Source: Employer posting
Pay: Needs confirmation

Fictional role and response. This is not a live connection, tool result or saved match.

Four tools for the recorded details.

The server reads results and employer listings already in Ping. Your assistant can help compare the details without starting another matching run.

Review your matches

list_matches

Read your current strong and worth-considering matches, saved opportunities and history.

Understand one result

get_match

Open a recorded match to review its reasons, concerns, source links and availability.

Browse employer listings

list_job_listings

Read active listings from verified employer sources. These catalogue results are not personalized match judgments.

Read the posting details

get_job_listing

Inspect one active listing, including its listed work arrangements, compensation and description.

Your account, read-only access.

Personal match results are limited to the account you authorize. Catalogue listings are shared employer postings from verified sources.

The four tools read existing results. They do not change preferences, save or dismiss roles, submit applications, start scouting or send email. Manage your brief and saved roles in Ping, and apply through the employer’s listing.

Authentication uses Ping sign-in and consent through WorkOS. The client manages its OAuth connection; there is no Ping API-key creation step.

One server address. OAuth sign-in.

These clients document support for remote HTTP MCP and OAuth. The steps below are connection previews; Ping sign-in has not yet been tested end to end in each client.

Server addresshttps://pingjobs.co/mcp

Claude Code connection preview

Add the remote server, then open /mcp in Claude Code to follow its authentication flow.

claude mcp add --transport http --scope user ping https://pingjobs.co/mcp

Read the official Claude Code guide

Add the remote server
Use the URL above in your client’s MCP configuration. Each client connects to the same Ping endpoint.
Authorize your Ping account
When the connection flow is available, follow the client’s OAuth prompt to sign in and consent. Personal match results belong to the account you authorize.
Ask about existing results
Try “Show my saved Ping matches and note which listings are still available,” or “Compare the disclosed work arrangements and pay for these two listings.”

Connection setup is under verification. Contact support@pingjobs.co to check availability before relying on an integration.

Give your next move a clear brief.

You can save a brief today. Matching is still being set up; continuous scouting and email alerts are not open yet.

Create your brief