Claude Chrome MCP

Created By
durapensaa year ago
Developer tool suite enabling Claude Desktop, Claude Code, and other MCP hosts like Cursor, to interact with claude.ai in Chrome browsers.
Overview

What is Claude Chrome MCP (CCM)?

Claude Chrome MCP (CCM) is a developer tool suite that enables integration between Claude Desktop, Claude Code, and other MCP hosts like Cursor with claude.ai in Chrome browsers.

How to use Claude Chrome MCP?

To use Claude Chrome MCP, install the Chrome extension, set up the MCP server in Claude Desktop, and utilize the CLI tool for direct browser control.

Key features of Claude Chrome MCP?

  • Chrome Extension for debugging and interaction with claude.ai
  • MCP Server for exposing Chrome capabilities to clients
  • Command-line interface for managing Claude sessions and tabs

Use cases of Claude Chrome MCP?

  1. Creating and managing Claude.ai tabs in Chrome.
  2. Sending messages and retrieving responses from Claude sessions.
  3. Debugging and executing scripts in the browser environment.

FAQ from Claude Chrome MCP?

  • Is the Chrome extension required for all functionalities?

Yes, the extension is necessary for interacting with claude.ai pages.

  • Can I use the CLI tool without the MCP server?

No, the CLI tool requires the MCP server to function properly.

  • What programming languages are supported?

The project is primarily built with JavaScript and includes TypeScript support for API definitions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
durapensa
Star
1
Language
JavaScript
License
GPL-3.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago