Skip to main content

Get your first signal

At the end of this page, one project shows a heartbeat you sent. The same project then takes error tracking and analytics without a second account.

Samples run on , facts checked on

Before you begin

  • A PostDeploy account. The trial runs 14 days and needs no card.
  • An MCP client that supports remote servers with OAuth, for example the coding agent you already use.
  • A terminal with curl, to send the first heartbeat.

Create the organization and project

People create organizations and projects in the dashboard. Everything inside a project, such as monitors, keys and sources, comes from your agent.

  1. Step 1. Register at postdeploy.dev/register.

  2. Step 2. On "Create your organization", enter a name and select "Create organization".

  3. Step 3. Under "Create your first project", enter a project name and select "Create project". The dashboard opens "Connect an agent".

Connect your agent

  1. Step 1. Copy the setup prompt from "Connect an agent" and give it to your MCP client. It names this endpoint and OAuth.

    Prompt text
    Set up a remote MCP server named "my-project" for this project.
    Endpoint: https://postdeploy.dev/mcp
    Authentication: OAuth.
  2. Step 2. Your client opens a browser. Sign in, choose the organization and project, clear any permission the client does not need, and select "Allow access".

  3. Step 3. Return to "Connect an agent" and select "Check connection". The screen shows "Your agent is connected".

Read Connect an MCP client for permissions, token lifetimes and revocation.

Send the first heartbeat

A heartbeat is the fastest first signal, because it needs no SDK and no deploy.

  1. Step 1. Ask your agent to create a heartbeat monitor. The response contains a token that starts with hb_. PostDeploy shows it once.

    Prompt text
    Create a heartbeat monitor named nightly-backup that expects a ping every day, with a one hour grace period. Show me the heartbeat token.
  2. Step 2. Send a ping. The server answers 202 Accepted.

    Terminal shell
    export POSTDEPLOY_HEARTBEAT_TOKEN=hb_your_token
    curl -i "https://ingest.postdeploy.dev/h/$POSTDEPLOY_HEARTBEAT_TOKEN"
  3. Step 3. Open Monitor in the dashboard. The row "nightly-backup" shows a recent check, and its detail screen lists it under "Recent checks" as Up.

Add the next signal

Production errors
Install the SDK for your runtime. Start at Capture production errors.
Pageviews and events
Add one script tag to your site. Follow Install Measure.
Uptime checks
Ask your agent to check a URL. Read Choose uptime checks or heartbeats.

Troubleshoot

There is no button to create a key or monitor
The dashboard is for review. Your connected agent creates monitors, keys and sources.
The heartbeat token is lost
PostDeploy shows a token once. Ask your agent to reissue the heartbeat token, then approve the request under "Pending confirmations" on the project MCP screen.
curl prints 404
The token is wrong or was reissued. Copy the token from the latest agent response.

Limits

  • The dashboard does not create monitors, keys or sources. A connected MCP client does.
  • A heartbeat that stops arriving does not send an alert. Read missed runs before you depend on it.

Create the project now.

14 days free, no card required. Then $29 a month.

Start your 14-day free trial