Help you can put to work

Connect your site. Understand what happens next.

Practical guides for setting up Firefly Agent, reading your results, and taking the next step when something needs attention.

GUIDE 01

Connect ChatGPT, Claude, or Codex

MCP (Model Context Protocol) lets a compatible AI assistant use your StackFirefly monitoring context. This is a manual connection, not a marketplace installation. Availability depends on your AI account and workspace policy.

  1. 1In StackFirefly, open Workspace settings → AI connections for the connection URL and assistant-specific setup guides.
  2. 2Add https://stackfirefly.com/api/mcp as a remote MCP server in your AI client and use OAuth authentication. Sign in to StackFirefly when prompted.
  3. 3Choose one workspace and the sites to share. Start with read-only access to site inventory, check results, issues, available evidence, change history, and Lighthouse metrics.
  4. 4Optionally allow issue actions: acknowledge an issue, record a reported fix, or request verification. These permissions do not allow changes to WordPress or automatic declarations of recovery.
  5. 5Ask your assistant to review open issues or explain a specific finding. Revoke access at any time in Workspace settings → AI connections. Newly added sites are not shared automatically.
  6. 6Your chosen AI provider processes the context under its own terms and privacy settings. No Agent secrets or pairing keys are shared by these tools.

GUIDE 02

Connect your first site

You need permission to install a WordPress plugin and an HTTPS site.

  1. 1Create your StackFirefly account, verify your email, and add your site to a workspace.
  2. 2Open Site settings → Firefly Agent. Download the plugin ZIP, then install and activate it in WordPress under Plugins → Add New → Upload Plugin.
  3. 3Generate a pairing key in StackFirefly. Paste it into the Firefly Agent connection screen in WordPress within 15 minutes. The key can be used once.
  4. 4Return to the site overview. Checks appear as the Agent reports and external checks complete. An unknown result means there is not enough information yet.

GUIDE 03

Connect a WordPress network

Manage monitoring from one workspace while keeping each subsite's results separate.

  1. 1Install and network-activate the Firefly Agent from WordPress Network Admin.
  2. 2Connect the network using the pairing flow, then open its network view in StackFirefly.
  3. 3Select the discovered subsites you want to monitor. Selected sites count toward your workspace's site allowance.
  4. 4Review each site's connection and checks. A working main site does not establish that every subsite is healthy.

GUIDE 04

Understand your results

Open a monitor to see what was checked, the latest finding, and available actions.

  1. 1Needs attention means a warning or failure was reported. Open the finding to see the affected file, component, or check where available.
  2. 2Unknown means the check could not establish a result. Review connection, firewall, and coverage details before treating it as a site failure.
  3. 3Accepted means you chose to keep a supported finding as expected. It is separate from a verified healthy result; changed evidence may need review again.
  4. 4Use History for past results, Performance for page-speed trends, and Email for test delivery details.

GUIDE 05

Review issues and fixes

An issue groups reports of the same problem, so you can investigate it in one place.

  1. 1Open the issue and read what was found and what to do next. Acknowledge it to show your team you are looking into it.
  2. 2Ask AI for an explanation of available evidence, or request expert help. Review the suggested action before making changes.
  3. 3After a change, use Verify fix when available. Some checks need more than one fresh result before recovery is confirmed.
  4. 4For supported error reports that cannot prove recovery automatically, Mark as fixed records your confirmation. A new matching report can reopen the issue.

GUIDE 06

Set expectations for alerts

Connecting a site should give you a starting picture, not a separate email for every old problem.

  1. 1Initial findings are gathered with onboarding email protection. They remain visible in the app while individual emails are held back.
  2. 2Operational alerts are grouped and rate-limited to reduce bursts. Check Alerts for delivery history and suppression reasons.
  3. 3Review your workspace's alert destinations and preferences. A suppressed email does not mean the finding was removed.

GUIDE 07

Keep the Agent connected

Requirements: WordPress 6.5+, PHP 7.4+, plugin installation access, and outbound HTTPS. Use a currently supported PHP version for your site's security.

  1. 1Open Site settings → Firefly Agent for the installed version, connection details, download, and release notes.
  2. 2When an update is available, update through WordPress or request the supported Agent update from StackFirefly.
  3. 3A healthy connection does not need routine re-pairing. If reports stop, check the displayed reason and the site's scheduled tasks.
  4. 4A blocked direct verification request does not prove cron is broken. Ask your host to review the endpoint and firewall details shown in the app.

GUIDE 08

Work with your team

Keep access organised within a workspace.

  1. 1Use Team to invite colleagues and choose a role appropriate to their work. Available actions depend on their permissions.
  2. 2Use Workspace settings to manage the workspace name and review usage; plan information is under Billing.
  3. 3Open your account security settings to enable authenticator-app two-factor authentication and review active sessions.

GUIDE 09

When a result is missing

Start with the message on the monitor or Firefly Agent status.

  1. 1Pairing expired: generate a new key and check that WordPress can make outbound HTTPS requests.
  2. 2Check blocked: review the reported HTTP status and firewall guidance. A 403 alone does not identify which service blocked it.
  3. 3Email not received: distinguish a failed send from a message accepted by WordPress but not received by the test inbox. Review your mail provider's logs.
  4. 4Error details missing: use Capture next trace where available and reproduce the affected action. A capture cannot reconstruct a past request.

Start with one WordPress site.

The beta starts with a 15-day trial, requires no payment card, and falls back to Free.

Start free — no card required