This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Capture browser console logs via the Chrome DevTools Protocol and expose them to an MCP client over SSE.
Useful for getting console log for extensions that run outside of the main browser window!
npm install -g @onlyhumn/chrome-console-log-mcp-serverOr run without installing:
npx @onlyhumn/chrome-console-log-mcp-server --match "YOUR_URL_SUBSTRING"From a clone:
npm install
node server.js --match "YOUR_URL_SUBSTRING"Related MCP server: Kaboom Browser AI Devtools MCP
Start the browser with remote debugging:
/Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser --remote-debugging-port=9222Start the server (requires --match):
npx @onlyhumn/chrome-console-log-mcp-server --match "YOUR_URL_SUBSTRING"Examples:
npx @onlyhumn/chrome-console-log-mcp-server --match "localhost:3000"
npx @onlyhumn/chrome-console-log-mcp-server --match "vlt-panel.html"Configure your MCP client:
Type: sse
URL: http://localhost:8766/sse
Open or focus a page whose URL contains the match string. The server prints Attached to ... when it finds a match. Use the getConsoleLogs tool to read captured output.
Flag | Default | Meaning |
| required | URL substring for CDP targets |
|
| CDP remote debugging port |
|
| HTTP port for MCP SSE |
|
| log directory |
|
| rotate threshold |
|
| rotated |
|
| CDP target rescan interval (ms) |
Console events are appended to /tmp/chrome-console-logs/current.jsonl. When the file exceeds the rotate threshold it is gzipped and pruned so only the newest --log-keep archives remain.
Publishes run from GitHub Actions on v* tags. The tag must match package.json "version".
Ensure the npm org/user owns the @onlyhumn scope.
First publish only: from a machine logged into npm (npm login), run npm publish --access public once so the package exists, or create the package on npmjs.com if your account allows it.
On the package page → Trusted Publisher (values are case-sensitive; must match GitHub OIDC claims):
Repository: ONLYHUMN/chrome-console-log-mcp-server (not lowercase onlyhumn/...)
Workflow filename: publish.yml
Leave Environment blank (workflow does not set one)
Bump "version" in package.json, commit, push to master.
Tag and push:
git tag v1.0.1
git push origin v1.0.1A Trusted Publishing failure often shows up as a misleading E404 from npm publish.
Browser must be started with --remote-debugging-port=9222 (or the port you pass to --port)
--match is required; without it the process exits immediately
Confirm the server printed Attached to ... for your page
MCP client URL should be http://localhost:8766/sse (or your --mcp-port)
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Discord MCP server for ChatGPT, Claude and any AI agent: list servers and channels, read channel messages, search messages, send message, reply to message, send DM, read mentions and assign role in your own Discord account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Discord yourself; Cotlet does not store your password and you need no Discord API key. About the official Discord API: Yes, Discord has an official API for bots and OAuth2 apps, but it acts as a bot that a server manager adds, not as you, and Discord has no official MCP server for it (checked 5 Nov 2026). The MCP server on Discord's docs site only searches documentation. Setup and FAQ: https://cotlet.dev/integrations/discord-api-mcp-server
Riverside MCP server for ChatGPT, Claude and any AI agent: create studio, schedule session, invite guest and download recording in your own Riverside account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Riverside yourself; Cotlet does not store your password and you need no Riverside API key. About the official Riverside API: Riverside has a Business API for select Business accounts only, with a key from your customer success manager, and it mostly gets or deletes recordings and lists scheduled events (checked 11 Oct 2026). Its official MCP server (beta, Grow, Webinar and Business plans) searches, edits and posts clips, but cannot schedule sessions or invite guests. Setup and FAQ: https://cotlet.dev/integrations/riverside-api-mcp-server
DICE MCP server for ChatGPT, Claude and any AI agent: create event, update ticket tier, get sales report, list ticket holders and issue comp tickets in your own DICE account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to DICE yourself; Cotlet does not store your password and you need no DICE API key. About the official DICE API: DICE has a read-only partner API, the Ticket Holders GraphQL API, with a token you generate in MIO (checked 11 Oct 2026). It reads events, tickets, orders, returns and transfers, and documents no mutations, so it cannot create events, change ticket types or message fans. Setup and FAQ: https://cotlet.dev/integrations/dice-api-mcp-server
Medium MCP server for ChatGPT, Claude and any AI agent: create post, edit post, cross-post article and get post stats in your own Medium account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Medium yourself; Cotlet does not store your password and you need no Medium API key. About the official Medium API: Medium has an old REST API, but it is no longer supported and Medium does not allow new integrations (checked 11 Oct 2026). Accounts that still hold a token can only create posts, list publications and upload images, with no editing, stats or responses. Setup and FAQ: https://cotlet.dev/integrations/medium-api-mcp-server
