TabMerger is a cross-browser extension that stores your tabs in a single place to save memory usage and increase your productivity.
MCP server Claude CodeCodexCursor +2
Lets the agent create and look up Stripe customers, products, prices, payment links and invoices. Runs locally from the @stripe/mcp npm package. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
Lets the agent create and look up Stripe customers, products, prices, payment links and invoices. Runs locally from the @stripe/mcp npm package. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
MCP server Claude CodeCodexCursor +2
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
MCP server Claude CodeCodexCursor +2
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
MCP server Claude CodeCodexCursor +2
Lets the agent manage Supabase projects: inspect tables, run SQL, handle migrations and read logs. Runs locally from the @supabase/mcp-server-supabase npm package. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
Lets the agent search and read Sentry issues, errors and traces, and act on them. Runs locally from the @sentry/mcp-server npm package. Needs 2 environment variables to run.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: