Browser Tools

magyk.app

Triage Magyk browser captures by retrieving console logs, network requests, user action timelines, and voice narration transcripts.

1 endpoint7 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://magyk.app/api/mcp

No auth detected

MCP server metadata

Name: Magyk
Version: 1.0.0

Capabilities

tools.listChangedlogging.enabled

Server instructions

Magyk stores bug captures (screenshot or recording) with an optional narration brief (from voice transcript + title/description) and separate DevTools context (console, network, actions). The brief summarizes what the reporter said. it does not deep-link console/network/action IDs. Use getConsole, getNetwork, and getActions for that evidence. When the user pastes a magyk.app/c/:id link (or capture id), call triageCapture first. Use getConsole, getNetwork, getActions, getTranscript, getMedia, or getMetadata only if you need more detail. For recordings: trust the action timeline, errors, network failures, and transcript before opening the video URL. For screenshots: open mediaUrl when the UI is the question. layout bugs often have no console errors. Do not invent evidence that tools did not return. Magyk does not host the fix conversation. plan and edit code in this agent.

Known tools 7

triageCapture

Primary Magyk tool.

Inferred read-only

getConsole

Fetch console logs from a Magyk capture.

Inferred read-only

getNetwork

Fetch network requests from a Magyk capture.

Inferred read-only

getActions

Fetch the user action / event timeline from a Magyk capture (clicks, inputs, navigations).

Inferred read-only

getTranscript

Fetch voice narration transcript cues from a Magyk capture when the reporter spoke while recording.

Inferred read-only

getMedia

Get media metadata for a Magyk capture.

Inferred read-only

getMetadata

Get safe page/environment/target metadata for a Magyk capture.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.magyk]
url = "https://magyk.app/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "magyk": {
      "type": "http",
      "url": "https://magyk.app/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: magyk
Remote MCP URL: https://magyk.app/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "magyk": {
      "url": "https://magyk.app/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "magyk": {
      "type": "http",
      "url": "https://magyk.app/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "magyk",
  "transport": "streamable-http",
  "url": "https://magyk.app/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for magyk.app was fetched 2026-10-01T23:26:11.400Z.

Trust status Neutral

magyk.app is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.