Pinpoint MCP Server
Give your AI coding assistant full access to Pinpoint through the Model Context Protocol. Manage projects, test requests, reports, and bugs without leaving the editor.
Setup
Select your editor below for step-by-step instructions. The server runs through npx, so there is no global install required.
- 1Create or open .mcp.json in your project root
- 2Paste the configuration below
- 3Restart Claude Code to pick up the new server
- 4The server will prompt you to log in on first use
.mcp.json
Place this file in your project root or home directory. The server automatically discovers your account details when you connect.
{
"mcpServers": {
"pinpoint": {
"command": "npx",
"args": [
"-y",
"pinpointmcp@latest"
]
}
}
}Available Tools
Once connected, your AI assistant gains access to 25 tool calls grouped across seven categories. Each one maps directly to the Pinpoint API.
Bug Management
list_bugsFilter bug reports by status, project, and page through results
get_bugRetrieve the full report for a specific bug including reproduction steps
update_bug_statusMark a bug as in_progress or complete with optional resolution notes
configureSet or rotate your API token at runtime without editing config files
Project Management
list_projectsList all projects in your account
create_projectRegister a new project for testing (respects plan limits)
update_projectUpdate a project's name, description, or type
delete_projectRemove a project by ID
Project creation beyond your plan's included limit returns an error directing you to the dashboard for billing confirmation. This prevents unintended charges when used by AI agents.
Environments
add_environmentAdd a new environment to a project with a name and base URL
list_environmentsList environments for a project
update_environmentUpdate an environment's name, base URL, or default status
remove_environmentRemove an environment from a project
Test Requests
list_requestsList test requests for your account
create_requestCreate a new test request for a project
get_requestRetrieve details for a specific test request
Reports
get_reportRetrieve metadata for a specific bug report
download_reportGet a presigned download URL for a report PDF
list_dispatch_reportsList all reports generated for a test request
Spectre Scan
list_scan_runsList Spectre scan runs showing commit, branch, and finding counts
list_scan_findingsList findings for a project filtered by category, severity, or status
get_scan_findingGet detailed information about a finding including location and suggested fix
update_finding_statusUpdate a finding's status to acknowledged, resolved, or false positive
Dependency Insights
get_blast_radiusCompute the proportion of the dependency graph reachable from a given component
get_dependency_chainTraverse the dependency chain from a component with relationship labels
get_test_coverageCalculate test coverage for a scope by examining tested-by edge ratios
Resources
MCP resources let your assistant read Pinpoint data as structured context without making explicit tool calls.
pinpoint://projectsJSON list of active projects
pinpoint://projects/{id}Markdown-formatted project details
pinpoint://projects/{id}/scansJSON summary of latest scan run and finding counts
pinpoint://requests/{id}Markdown-formatted request details
pinpoint://bugsJSON list of open bugs
pinpoint://bugs/{id}Markdown-formatted bug details
pinpoint://findings/{id}Markdown-formatted scan finding details
Prompts
Pre-built prompt templates that structure multi-step analysis workflows for your AI assistant.
solve_bugStructured prompt for analyzing and fixing a specific bug. Fetches the full bug report and builds a step-by-step resolution workflow.
review_requestAnalyze test request results and associated reports. Accepts a request ID, fetches the dispatch details and all reports, and builds a structured analysis prompt.
fix_findingStructured prompt for fixing a specific Spectre scan finding. Includes location, description, suggested action, and related components.
Usage
Here is what the workflow looks like in practice. Ask your assistant in plain language and Pinpoint handles the rest.
Show me all open bugs for the payments project
Found 3 open bugs for payments: #421 Stripe webhook timeout on retry (high) #419 Currency rounding error in checkout (medium) #418 Missing null check in refund handler (medium)
Get the details for bug #418
Bug #418 — Missing null check in refund handler Status: open Severity: medium Found in: v2.4.1 Reproduction steps: 1. Initiate a refund for an order with no payment method 2. Observe a NullPointerException at refund.ts:47 Expected: Graceful error message returned to the caller Actual: Unhandled exception crashes the request
Fix bug #418 and mark it complete
Reading bug #418... Located null check issue in src/payments/refund.ts:47 Applied fix — added guard clause before accessing payment method. Marking bug #418 as complete with note "Added null check for missing payment method." Pinpoint will verify the fix during the next test round.
Mark bug #421 as in_progress, I'm starting on it now
Updated bug #421 "Stripe webhook timeout on retry" from open → in_progress.
Configure Pinpoint with my new API token abc-xyz-123
Pinpoint API token updated successfully. Connected to testwithpinpoint.com, ready to go.
List my projects
Found 2 projects: My App (UI, active) Backend API (API, active)
Create a test request for the My App project
Created test request req-abc-123 for project My App. Status: pending. You'll receive results within your SLA window.
Show me the reports for request req-abc-123
Found 2 reports for req-abc-123: #1 Login timeout on mobile (high) #2 Form validation skipped on Safari (medium) Use get_report or download_report for full details.