Faylee

app.fayleePublished by faylee.appOfficial publisherv1.0.0Updated Oct 24, 2026

Read browser bug recordings: video, console, network, steps. Fix the bug and comment back.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Lets an assistant read browser bug recordings — video, console, network and steps — and comment back after fixing the bug.

What you can do
Faylee exposes browser bug recordings to an assistant: the session video, console output, network activity and the recorded reproduction steps. The assistant can review that evidence to diagnose the reported bug, then post a comment back on the recording once it has a fix.
When to use it
Useful when bug reports arrive as recorded browser sessions and you want the assistant to inspect the actual console and network evidence rather than a written description. Suited to triage and follow-up on front-end issues captured in Faylee.
Requirements
A remote MCP endpoint at over streamable HTTP. Authentication is required via OAuth; clients that support MCP OAuth should sign in interactively. Headless clients instead send an Authorization header with a Bearer Faylee personal token.
Before you install
The Authorization header carries a Faylee personal token, so treat it as a secret and prefer interactive OAuth where possible. Recordings can contain console output, network requests and user session video, which may include sensitive data. The assistant can write comments back to recordings, so review what it posts.

Installation

In SourceWeft

  1. Open Faylee in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.faylee%2Ffaylee/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.