How Brad Feld plugged Marker.io into the operating system of his company

The problem they were solving

Brad runs and ships multiple products as a solo operator. User feedback and bug reports arrive across three different surfaces: Linear tickets, Help Scout conversations, and Marker.io bug reports. Each with its own format and its own dashboard. Pulling that signal together by hand is exactly the kind of work CompanyOS is designed to eliminate: the entire premise of his setup is that Claude Code, not a human, should be the layer that reaches into every tool.

‍

What they built

Brad wired Marker.io's MCP server directly into CompanyOS (his Claude Code-based operating layer) so visual bug reports flow into the same AI-driven workflows that handle the rest of the business.

• Marker.io bug reports auto-route into Linear, with no manual ticket creation
• The co-feedback skill pulls Marker.io reports alongside Linear tickets and Help Scout conversations, then aggregates them into thematic patterns for product decisions
• Marker.io is one of 13 MCP servers connected into the Claude Code workflow: bug reporting and feature enhancement are queried on-demand whenever Claude needs visual context for a fix
• Authentication via Bearer token (PAT-style), chosen specifically because API keys survive Claude Code updates (Brad's stated architectural preference)

‍

Where they are now

Marker.io is one of 13 MCP servers wired into Brad's Claude Code configuration. Bug reports flow into his Linear process automatically. When his workflow needs context from Marker.io, Claude Code queries it directly through the MCP server without separate dashboard or manual hand-off. The co-feedback skill aggregates Marker.io reports alongside Linear and Help Scout into thematic patterns that feed product decisions across his portfolio.

‍

Why this is worth stealing

• ‍Bug reports become AI-readable. Marker.io captures the visual + console + network state in a structured form. Once that's behind an MCP server, an AI agent can consume it the same way a developer would.\
• Cross-tool pattern analysis beats single-tool triage. Aggregating Marker.io with Linear and Help Scout in one skill means recurring issues surface across surfaces, not just within one of them.‍
• MCP turns "another tool to check" into "a system Claude already uses." The integration removes the context-switch tax: the data is there when the workflow needs it, and stays out of the way otherwise.