npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ainative/cody-for-chrome-mcp

v0.1.1

Published

MCP server for Cody in Chrome browser integration

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ainative-studioainative-studio

Keywords

mcpchromebrowser-automationcodyainative

Readme

@ainative/cody-for-chrome-mcp

MCP server that bridges Cody CLI to the Cody in Chrome browser extension.

How it works

Cody CLI  -->  MCP stdio transport  -->  cody-for-chrome-mcp  -->  Unix socket  -->  Chrome extension

When Cody CLI starts a browser-automation session it spawns this server as a subprocess (stdio transport). Each tool call is forwarded to the running Chrome extension over a local Unix socket (/tmp/cody-mcp-browser-bridge-<user>/*.sock). On Windows the same protocol runs over a named pipe.

Tools (13)

| Tool | Description | |------|-------------| | tabs_context_mcp | Get URL, title, and content of open tabs | | tabs_create_mcp | Open a new tab at a URL | | tabs_close | Close a tab by ID | | navigate | Navigate the active tab to a URL | | click | Click an element by CSS selector | | fill_form | Fill a form field (selector + value) | | scroll | Scroll the page or an element | | screenshot | Capture viewport screenshot as base64 | | gif_creator | Record a GIF of interactions (start/stop/get) | | read_console_messages | Read browser console logs | | read_network | Read XHR/fetch network requests | | javascript_tool | Execute JavaScript in the page context | | wait_for_element | Wait for a CSS selector to appear |

Usage

The server is spawned automatically by Cody CLI when the cody-in-chrome MCP server is configured. You can also run it manually for debugging:

npx @ainative/cody-for-chrome-mcp

Requirements

  • Node >= 18 or Bun >= 1.1
  • Cody in Chrome extension installed from https://ainative.studio/chrome
  • Extension must be running and logged in with the same AINative account as Cody CLI

Author

AINative Studio — https://ainative.studio