# magyk > Catch the bug. Share the whole story. magyk is a bug reporting Chrome extension and share host. Capture a screenshot or recording with DevTools context (console, network, actions, environment), then share one link teammates and coding agents can open. You can also send a recording link so anyone records their screen in the browser without installing the extension. Website: https://magyk.app/ Chrome extension: https://chromewebstore.google.com/detail/magyk/gnmonnbkjklngachmpmphjcgbphpaace Email: chandra@magyk.app ## Key facts - Audience: engineers, QA, and product teams debugging web apps - Two capture paths: Chrome extension (media + DevTools context) and recording links (browser screen recording, no install) - Share links expire after 48 hours by default. Recording-link submissions last 7 days - After expiry, full media and capture payload are deleted; a thumbnail may remain on the dashboard - Free while early - Shipped from Europe - [FAQ](https://magyk.app/faq): common questions about captures, recording links, privacy, MCP, and AI briefs - [MCP setup](https://magyk.app/mcp): connect magyk to Claude, Cursor, Codex, and other agents - [Privacy](https://magyk.app/privacy) - [Terms](https://magyk.app/terms) - [Contact](https://magyk.app/contact) ## Recording links A recording link is a public URL (`https://magyk.app/r/{code}`) created in the magyk dashboard after sign-in. - Anyone with the link can record their screen in a desktop browser (optional microphone). No Chrome extension and no magyk account required. - Each recording link accepts one recording. Reopening a used link shows that the recording was already submitted. - The recording is stored in the link creator's workspace and becomes a normal capture share link (`https://magyk.app/c/{id}`). - Recording links do not include console, network, or click traces from the reporter's browser. Those come from the Chrome extension. - Typical use: send a URL from a support ticket so a customer can show the bug. ## MCP magyk exposes a remote Model Context Protocol (MCP) server over Streamable HTTP so coding agents can load a capture from a share link. - Setup page: https://magyk.app/mcp - MCP endpoint (Streamable HTTP): https://magyk.app/api/mcp - Supported clients: Claude Code, Cursor, Codex, ChatGPT connectors, VS Code / Copilot, OpenCode, and other Streamable HTTP MCP clients - No magyk login inside the agent for v1. Paste any unexpired capture link (magyk.app/c/…), including captures that arrived from a recording link - Typical agent flow: connect MCP, paste a capture URL, call triage first, then plan and edit - Capture context available to agents: debug brief, transcript, console, network, actions, media, and metadata. Recording-link captures usually have media and optional transcript, not DevTools logs. Install examples: - Claude Code: `claude mcp add magyk https://magyk.app/api/mcp -t http -s user` - Cursor: add `{ "mcpServers": { "magyk": { "url": "https://magyk.app/api/mcp" } } }` to MCP settings - Codex: add `[mcp_servers.magyk]` with `url = "https://magyk.app/api/mcp"` in `~/.codex/config.toml` ## Product magyk helps engineers, QA, and product teams capture a bug with full browser context (screenshots or recordings plus console, network, and environment) and share it as a single link. When the reporter cannot install the extension, a recording link collects a screen recording in the browser. Teammates and AI coding agents can move work forward without reproducing the issue from scratch. Primary use case: bug reporting Chrome extension / DevTools context sharing for debugging web apps, plus recording links for reporters without the extension. ## Optional - [Sitemap](https://magyk.app/sitemap.xml) - Homepage: https://magyk.app/ - FAQ: https://magyk.app/faq - MCP: https://magyk.app/mcp - Privacy: https://magyk.app/privacy - Terms: https://magyk.app/terms - Contact: https://magyk.app/contact