Flare

io.flareappPublished by flareapp.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Error tracking for Laravel and PHP apps. Let your agent fetch errors, stack traces and context.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Flare is a remote MCP server for error tracking in Laravel and PHP apps, letting an assistant fetch errors, stack traces and context.

What you can do
Fetch errors recorded for Laravel and PHP applications, including stack traces and surrounding context, so an assistant can inspect what went wrong. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you track a Laravel or PHP application in Flare and want an assistant to look up recorded errors and their stack traces while debugging.
Requirements
A remote endpoint at flareapp.io reached over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Flare account, so the assistant can read error data from your tracked applications; review the scopes granted during sign-in. The manifest lists no write tools, but the available operations are not documented.

Installation

In SourceWeft

  1. Open Flare 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/io.flareapp%2Fflare/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": {
    "flare": {
      "type": "http",
      "url": "https://flareapp.io/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 9, 2026

Score

67% 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
  • 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.