PinpointAssign Work Like Your Own Team
Augment embeds across development and QA, so you hand off work the same way you assign your own team. We slot into your CI/CD pipeline, CLI workflow, and AI coding assistant, with no new tools and no new processes, and we are effective from day one.
FROM YOUR BOARDTO SHIPPED.
You assign a ticket and it comes back as a reviewed, merged PR, all inside the workflow your team already runs.
Your Board
The work lives where it already lives. Augment meets you on the same board your team uses today, not in a separate portal.
Assign a Ticket
You assign a high-leverage ticket, the same way you assign your own team. No extra coordination, no context switching for your developers.
We Pick It Up
A Pinpoint senior engineer picks it up, brings judgment to the hard parts, and works it like a teammate already inside your sprint.
PR and Review
PR plus architecture review, in the same standups. The work shows up where your team already reviews it, open to the same scrutiny as any contribution.
Ship
The work ships and we stay accountable for it after the merge, owning fixes and follow-through sprint after sprint.
NO NEW TOOLS ◦ NO NEW PROCESSES ◦ ACCOUNTABLE LIKE ANY TEAMMATE
A DEPLOY IS A HANDOFF.
Add Augment as a pipeline stage and a deploy becomes one more way to hand us work, since every staging deployment creates a test round automatically. The CLI ships as a Docker image, which means zero dependencies on your runner.
WHAT A STAGING DEPLOY TRIGGERS
- Developer pushes code
- CI/CD pipeline runs
- Pinpoint plugin triggers
- Hands-on review requested
- Tester reviews deployment
- Test report delivered
- Optional review meeting
- 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
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 }}"THE TERMINAL IS ENOUGH.
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.
# 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- 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
AI-ASSISTED.HUMAN-OWNED.
Give your AI coding assistant full access to Pinpoint through the Model Context Protocol, including projects, test requests, reports, and bugs.
The MCP server exposes the full testing lifecycle as structured tool calls. Your assistant can create requests, read reports, and triage bugs without leaving the editor, while a senior engineer stays in the loop on the fixes that matter.
KEY TOOLS (13 TOTAL)
list_bugsQuery open, complete, or verified reportsget_bugFetch full details for a single reportupdate_bug_statusTransition a bug through its workflowlist_projectsList all projects in your accountcreate_requestSubmit a new test request for a projectget_requestRetrieve details for a test requestdownload_reportGet a presigned URL for a report PDFconfigureSet or rotate your API token
COMPATIBLE PLATFORMS
{
"mcpServers": {
"pinpoint": {
"command": "npx",
"args": ["-y", "@pinpoint/mcp-server"]
}
}
}> "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.FREQUENTLYASKEDQUESTIONS
Common questions about setup, the CLI, and AI integrations
01How 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.
02Which CI/CD platforms does Pinpoint support?
Pinpoint works with GitHub Actions, GitLab CI, Jenkins, CircleCI, Drone, AWS CodePipeline, and any platform that runs Docker or shell commands. If your pipeline can execute a binary, it can run Pinpoint.
03How do I install the Pinpoint CLI?
The CLI ships as a Docker image (pinpoint/cli:latest) for CI and as a standalone binary for local use. Download the binary at testwithpinpoint.com/releases/cli and add it to your PATH.
04What is the MCP server and which AI tools support it?
The MCP (Model Context Protocol) server lets AI coding assistants manage bug reports inside the editor. It works with Claude Code, Claude Desktop, Cursor, Windsurf, and VS Code with Copilot. Configure it once in your .mcp.json file.
05Does the team use AI to fix bugs automatically?
AI helps the embedded team move fast. Through the MCP integration, an assistant can read a bug report, locate the relevant code, and draft a fix in your editor. A senior engineer owns the outcome and reviews every change before it ships, so the outlier cases that break systems get judgment, not a guess.
06How fast are test results delivered?
Results depend on your plan. Core plans deliver reports within 72 hours, Professional within 48 hours, and Enterprise SLAs are custom, negotiated based on your requirements. Most teams receive actionable findings well within their SLA window.
07Does the team need access to my source code?
Source code access is optional. The embedded team can work with staging URL access alone. Providing repository access lets them write targeted automated tests, review code paths, and identify edge cases that would otherwise require exploratory testing to uncover.
08What 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.
09Can I use Pinpoint without a CI/CD pipeline?
Yes. Run `pinpoint trigger` from any terminal to start a test round on demand, or use `pinpoint bugs` to review findings. The MCP server also lets AI assistants trigger and review tests without a pipeline.
10How do Augment engagements work?
Augment is available across Core, Professional, and Enterprise engagements, shaped around where the pressure on your team is highest across dev and QA. Every engagement includes the CLI, MCP server, and full dashboard access. Apply for access to discuss which engagement fits your workflow.
READY TO GET STARTED?
Apply for access to see how Augment slots into your team across dev and QA. Most teams are assigning us work within a single sprint.
Apply for Access