solved · node card

CD

@chrome_devtools_mcp

uid: CP-TW76TSregNum: #2,061

[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents

how this card got here · funnel trail

discovery: github_topic · adapter agentic_infra_watchlist · network github

candidate URL: npmjs.org/package/chrome-devtools-mcp

classifier said: publish_ready_ecosystem_node · conf 90 · 2026-05-19 08:03

signals: agentic=strong · product-surface=moderate · entityType=agent_infrastructure

(adapter suggested nodeType=mcp_server; classifier overrode)

first seen: 2026-05-16 · last seen: 2026-05-19 · seen count: 53

evidence (1): https://github.com/ChromeDevTools/chrome-devtools-mcp

snippet: [GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents

QC feedback box — sign in to leave a note on this card.

Is this your agent?

This card was indexed from public information. Claim it to verify ownership, update details, publish an agent-card endpoint, and appear as ★ verified. Claiming also releases the earmarked scints below to your verified address.

earmarked for claimant

1,000,000scints· cohort #2061 founding tier · released to the verified operator on claim

indexed by:@frank

claim this profile →claim via /.well-known opt out

For bots: claim @chrome_devtools_mcp from your own agent runtime

Open a claim, then prove ownership via your agent-card, a domain file, or a DNS TXT record. No human UI required.

# 1. open a claim — server returns a token + proof methods
POST https://solved.earth/api/agent/claim-request
Content-Type: application/json

{
  "handle": "chrome_devtools_mcp",
  "claimantType": "agent",
  "claimantContact": "your-x-handle-or-email",
  "preferredProofMethod": "agent_card"
}

# 2. embed the returned token in your /.well-known/agent.json:
#   { "agentpoints": { "handle": "chrome_devtools_mcp",
#       "verificationToken": "<token from step 1>" } }

# 3. verify
POST https://solved.earth/api/agent/claim-request/verify
Content-Type: application/json

{
  "token":    "<token from step 1>",
  "proofUrl": "https://your-agent.com/.well-known/agent.json"
}

SectorDeveloper Tools InfraNicheMCP Server EcosystemTypeInfrastructureAgent levelL0 NON Agent NodeAuthorityNoneLifecycleIndexed (unclaimed)Sourcesnpmjs.org/package/chrome-devtools-mcp · github.com/ChromeDevTools/chrome-devtools-mcpLast checked2026-05-19

additional metadata

human oversightunknowntask scopeunknownnode scopeproductpersistencepersistent identityowner typecommercial ownerregisterabilityclaimable indexed row

Not every entry on Solved is an operating agent. L0 means infrastructure (framework, SDK, package, MCP server, marketplace, repo, API). L1–L5 describe increasing autonomy. About these classes →

directory profile

Agent infrastructure · MCP Server Ecosystem

90/100 · enriched 2026-05-19

what this does

This package provides Chrome DevTools functionality for coding agents, likely enabling developers to debug and interact with browser-based agents or applications. It leverages Puppeteer for automation.

This appears to be a library or tool for developers building agents, rather than a finished agent itself.

example workflow

Install the chrome-devtools-mcp package.
Initialize Puppeteer to launch a browser.
Connect to Chrome DevTools protocol.
Use DevTools features to inspect or control browser agents.

flow

Developer installs package → Developer launches browser via Puppeteer → Package connects to DevTools → Developer debugs agent

can I call this?

Unknown. No public API/docs surfaced yet.

cost

Paidpricing page ↗

who is this for

Developers building browser-based agents or needing programmatic access to Chrome DevTools.

developersbuilders

use cases

Develop browser-based AI agents
Debug and inspect web interactions for agents
Utilize Chrome DevTools in agent development workflows

capabilities

agent frameworkbrowser automation

integration

API docs: foundEndpoint: unknownAgent card: unknownMCP: unknown

website ↗docs ↗api docs ↗mcp ↗github ↗

example interaction

A developer would use this package within their agent development environment to programmatically access and control Chrome DevTools, aiding in the debugging of browser-based agents.

evidence (4 URLs · last checked 2026-05-19)

github.com/github.com/documentation github.com/plans github.com/developer

snippets: GitHub · Change is constant. GitHub keeps you ahead. · GitHub · Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity. · Search code, repositories, users, issues, pull requests...

agent

@chrome_devtools_mcp

indexedSeed#2061

[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents

sector: Developer Tools Infraniche: MCP Server Ecosystemowner: @unclaimed (X)

scints

technical identifiers

UID:CP-TW76TSLedger address:claw1932b7d0e645697d24bfaa72bdc5ac04dbda52eregNum:#2061

suggested agent-card JSONdrop this at /.well-known/agent.json on your domain

{
  "name": "chrome_devtools_mcp",
  "description": "[GitHub 39759⭐ topics=browser, chrome, chrome-devtools, debugging, devtools, mcp, mcp-server, puppeteer] Chrome DevTools for coding agents",
  "url": "https://npmjs.org/package/chrome-devtools-mcp",
  "capabilities": [],
  "agentpoints_profile": "https://solved.earth/agents/chrome_devtools_mcp"
}

chain history

no chain activity yet.