Skip to main content
Pinpoint

From Push to Full QA Coverage

Pinpoint plugs into your CI/CD pipeline, CLI workflow, and AI coding assistant so every deploy gets tested by dedicated QA specialists. Setup takes minutes, results arrive in hours.

Three Steps to Full QA Coverage

From integration to actionable test results, the entire process is designed to stay out of your way

1

Connect Your Pipeline

Add the Pinpoint plugin to your CI/CD config. A single line connects GitHub Actions, GitLab CI, or Jenkins to our testing platform with no additional tooling required.

2

Push to Staging

Every deployment to your staging environment automatically triggers a dedicated test round. No manual coordination, no Slack messages, no context switching for your developers.

3

Get Results Fast

Receive a comprehensive report within your plan's SLA window covering regressions, edge cases, and exploratory findings with full reproduction steps and severity ratings.

The Full Pipeline Flow

From the moment a developer pushes code to the delivery of a complete test report, here is what happens behind the scenes

CI/CD Integration

Add Pinpoint as a pipeline stage and every staging deployment creates a test round automatically. The CLI ships as a Docker image, which means zero dependencies on your runner.

  • One-line integration with any CI/CD platform that runs Docker or shell commands
  • Automatic test-round creation on every staging deployment
  • Full report delivered within your plan's SLA window
  • No proprietary lock-in, works alongside your existing pipeline stages
GitHub Actions
GitLab CI
Jenkins
CircleCI
Drone
AWS CodePipeline
.github/workflows/pinpoint.ymlYAML
name: Pinpoint QA

on:
  push:
    branches: [main, staging]

jobs:
  pinpoint:
    runs-on: ubuntu-latest
    container: pinpoint/cli:latest
    steps:
      - name: Trigger test round
        env:
          PINPOINT_API_TOKEN: ${{ secrets.PINPOINT_API_TOKEN }}
        run: |
          pinpoint trigger \
            --project "${{ github.repository }}" \
            --environment staging \
            --build-url "${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
TerminalBash
# Configure credentials once
$ pinpoint configure --token "your-api-token"

# Create a project and trigger a test round
$ pinpoint projects create --name "my-app" --type UI
$ pinpoint trigger --project "my-app" --environment staging

# Check results and download reports
$ pinpoint requests list
$ pinpoint reports download abc-1234-def | xargs curl -o report.pdf

# Review and resolve bugs
$ pinpoint bugs list --status open
$ pinpoint bugs update abc-1234-def --status complete

Pinpoint CLI

The command-line interface works anywhere, whether inside a CI runner or on your local machine. Trigger test rounds, query bug reports, and manage projects without opening a browser.

  • Trigger test rounds from any terminal or CI runner
  • Manage projects, test requests, and bug reports from the command line
  • Download PDF reports directly with a single command
  • Lightweight Docker image for containerized pipelines

Environment variables

PINPOINT_API_TOKEN
PINPOINT_PROJECT
PINPOINT_ENV

MCP for AI Agents

Give your AI coding assistant full access to Pinpoint through the Model Context Protocol, including projects, test requests, reports, and bugs

AI-Assisted Bug Resolution

The Pinpoint MCP server exposes projects, test requests, reports, and bugs as structured tool calls. Your AI assistant can manage the full testing lifecycle, from creating requests to resolving bugs, all without leaving the editor.

Key tools (13 total)

  • list_bugsQuery open, complete, or verified reports
  • get_bugFetch full details for a single report
  • update_bug_statusTransition a bug through its workflow
  • list_projectsList all projects in your account
  • create_requestSubmit a new test request for a project
  • get_requestRetrieve details for a test request
  • download_reportGet a presigned URL for a report PDF
  • configureSet or rotate your API token

Compatible platforms

Claude Code
Claude Desktop
Cursor
Windsurf
VS Code + Copilot
.mcp.jsonJSON
{
  "mcpServers": {
    "pinpoint": {
      "command": "npx",
      "args": ["-y", "@pinpoint/mcp-server"],
      "env": {
        "PINPOINT_API_TOKEN": "<your-token>"
      }
    }
  }
}
Agent workflowText
> "List my projects"

Found 2 projects:
  My App        (UI, active)
  Backend API   (API, active)

> "Create a test request for My App"

Created request req-abc-123 for My App.
Status: pending, results within your SLA window.

> "Show open bugs for the payments project"

Found 3 open bugs:
  #421  Stripe webhook timeout on retry    (high)
  #419  Currency rounding error            (medium)
  #418  Missing null check in refund       (medium)

> "Fix bug #418 and mark it complete"

Reading bug #418...
Applied fix in src/payments/refund.ts:47
Marked #418 as complete.

Frequently Asked Questions

Common questions about setup, the CLI, and AI integrations

How long does it take to set up Pinpoint?

Most teams are fully integrated within 15 minutes. Add the Pinpoint CLI to your CI/CD config, set the PINPOINT_API_TOKEN environment variable, and your next deployment triggers a test round automatically.

Which CI/CD platforms does Pinpoint support?

Pinpoint works with GitHub Actions, GitLab CI, Jenkins, CircleCI, Drone, AWS CodePipeline, and any platform that can run a Docker container or shell command. The CLI is platform-agnostic, so if your pipeline can execute a binary, it can run Pinpoint.

How do I install the Pinpoint CLI?

The CLI ships as a Docker image (pinpoint/cli:latest) for CI environments and as a standalone binary for local use. In CI, use the Docker image directly. For local development, visit https://testwithpinpoint.com/releases/cli to download the binary for your platform and add it to your PATH.

What is the MCP server and which AI tools support it?

The Pinpoint MCP (Model Context Protocol) server lets AI coding assistants read and manage your bug reports directly inside the editor. It works with Claude Code, Claude Desktop, Cursor, Windsurf, and VS Code with GitHub Copilot. Configure it once in your .mcp.json file and your AI assistant gains access to list_bugs, get_bug, update_bug_status, and configure tools.

Can Pinpoint automatically fix bugs it finds?

With the MCP integration, your AI coding assistant can read a bug report, locate the relevant code, and propose a fix within your editor. While the fix still requires human review, the workflow from bug discovery to patch is largely automated.

How fast are test results delivered?

Results depend on your plan. Core plans deliver reports within 48 hours, Professional within 24 hours, and Enterprise SLAs are negotiated based on your requirements. Most teams receive actionable findings well within their SLA window.

Does Pinpoint need access to my source code?

Source code access is optional. QA specialists can work with staging URL access alone. However, providing repository access lets the team write targeted automated tests, review code paths, and identify edge cases that would otherwise require exploratory testing to uncover.

What data does Pinpoint collect from my pipeline?

The CLI sends only the metadata needed to create a test round: project name, environment label, build URL, and your API token. No source code, environment variables, or secrets are transmitted unless you explicitly opt into repository access.

Can I use Pinpoint without a CI/CD pipeline?

Yes. The CLI works from any terminal. Run `pinpoint trigger` locally to start a test round on demand, or use `pinpoint bugs` to review recent findings. The MCP server also lets AI assistants trigger and review tests without any pipeline at all.

What does Pinpoint cost?

Pinpoint offers Core, Professional, and Enterprise engagement tiers. Each tier is designed around how frequently your team ships. Apply for access to discuss which tier fits your workflow. All plans include the CLI, MCP server, and full access to the bug reporting dashboard.

Ready to Get Started?

Apply for access to see how Pinpoint fits into your development workflow. Most teams are fully integrated within a single sprint.

Apply for Access