Get started

Quickstart

Connect your workspace, issue a scoped runtime credential, start one agent, and verify the complete LiveProbe path.

Before you start

You need an invitation to a LiveProbe Clerk workspace, an MCP client that supports remote OAuth servers, and access to the deployment configuration for the service you want to observe. Runtime agents support Node.js 20+, Python 3.12+, and Java 17+.

Use the deployed revision

Every runtime agent refuses to start without a concrete hexadecimal commit SHA. Supply the revision that built the deployed process, not an arbitrary local checkout.

1. Connect the hosted MCP server

Add the production endpoint to Cursor or another OAuth MCP client:

json
{
  "mcpServers": {
    "liveprobe": {
      "url": "https://liveprobe.tryastrea.tech/mcp"
    }
  }
}

Choose Login, sign in through Clerk, and select the workspace you were invited to. No shared API key or local npm package is needed for hosted MCP access.

2. Create a runtime identity

Ask the connected LiveProbe MCP server to perform these steps:

  1. Create a projectUse one stable ID for the repository or application, such as acme.
  2. Create an environmentAdd a deployment target such as staging or production.
  3. Register a serviceUse one stable service ID for each independently deployed process, such as api or worker.
  4. Create a service credentialThe plaintext lp_service_... key is returned once. Place it directly in the deployment secret manager.
text
Create project "acme", add its "production" environment,
register service "api", and create a production service credential
labeled "Acme API production".

3. Start one runtime agent

Configure the same project, environment, service, credential, and deployed commit in the application. The language guides contain exact startup code.

dotenv
LIVEPROBE_BROKER_URL=https://liveprobe.tryastrea.tech
LIVEPROBE_PROJECT_ID=acme
LIVEPROBE_ENVIRONMENT=production
LIVEPROBE_SERVICE_ID=api
LIVEPROBE_API_KEY=lp_service_<shown-once-secret>
LIVEPROBE_COMMIT_SHA=<deployed-git-sha>

Deploy the agent with the application. The application does not need to run on GCP; it only needs outbound HTTPS access to liveprobe.tryastrea.tech.

4. Verify the connection

Run these read-only tools before placing a probe:

text
Ping the LiveProbe broker. In project acme and environment
production, list online services and show the safety overview.
Do not create a probe yet.

list_services should show the service ID, SDK, deployed commit, latest heartbeat, capabilities, and online state. An empty list means the agent has not successfully heartbeated in the selected project and environment.