Everframe

dev.everframev1.0.0Updated Oct 3, 2026

Read in-app bug reports, crashes, screenshots and tickets from mobile, web and TV apps.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant read in-app bug reports, crashes, screenshots and tickets collected from mobile, web and TV applications.

What it does
Everframe is a remote MCP endpoint that exposes the bug and crash reports users file from inside an application. According to the registry description, an assistant can read in-app bug reports, crashes, screenshots and tickets from mobile, web and TV apps. The reports are produced by Everframe's reporting SDKs, which capture screenshots and annotations, session evidence, breadcrumbs, device and application metadata, and captured errors. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Worth adding when you triage user-reported problems from apps instrumented with the Everframe SDKs and want an assistant to pull those reports, crashes and screenshots into the conversation. Less useful if your applications do not send reports to Everframe.
Requirements
A remote endpoint at everframe.dev over streamable HTTP; no packages, environment variables or headers are declared. The manifest declares no authentication, so access to your report data depends on how the endpoint is configured. The SDK side of Everframe is installed separately in your applications.
Before you install
Reports can contain screenshots, session evidence, breadcrumbs and device and application metadata, so treat them as sensitive user data. The manifest declares no authentication, which is unusual for a service holding customer reports; confirm how access is restricted before connecting. The README warns never to commit SDK keys, identity secrets, generated platform configuration or production data.

Installation

In SourceWeft

  1. Open Everframe in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "everframe": {
      "type": "http",
      "url": "https://everframe.dev/mcp"
    }
  }
}

README

Everframe SDKs

The open-source home of the Everframe reporting SDKs, shared protocol and SDK core, developer tooling, and sample applications.

Everframe helps users report problems from inside an application with the context needed to reproduce them: screenshots and annotations, session evidence, breadcrumbs, device and application metadata, and captured errors.

Choose an SDK

PlatformSDKDocumentationExamples
Web and framework-agnostic JavaScript@everframe/webWeb SDKVue, Smart TV
React@everframe/reactReact SDKReact web
React Native, Apple TV, and Android TV@everframe/react-nativeReact Native SDKReact Native, React TV
Flutter on Android, iOS, and webeverframe_flutterFlutter SDKAndroid probe, iOS probe, web probe
Kotlin Multiplatform on Android, iOS, and Kotlin/JSdev.everframe:kmpKMP SDKAndroid probe, iOS probes, browser canvas probe
Android and Android TVdev.everframe Maven modulesAndroid SDKCompose, Views
iOS, iPadOS, and tvOSEverframe Swift packageApple SDKiOS, tvOS replay
Server-side identity@everframe/identityIdentity helperRuntime-specific recipes are included in the package documentation

Each SDK README is the canonical guide for installation, configuration, privacy controls, platform support, and current limitations.

Shared packages and tooling

  • @everframe/protocol defines the versioned report envelope shared by every SDK and provides the generated JSON Schema used by the native implementations.
  • @everframe/sdk-core contains the platform-independent TypeScript reporting runtime and utilities shared by the Web, React, and React Native SDKs.
  • The Babel and SWC plugins preserve React component names in optimized builds.
  • packages/sdk-android and packages/sdk-ios contain the native SDK source, platform tests, and publication tooling.

Using the SDKs

Install the package for your application and follow its platform guide. For JavaScript projects, for example:

sh
pnpm add @everframe/web# orpnpm add @everframe/react# orpnpm add @everframe/react-native# Flutter apps use pub.dev:flutter pub add everframe_flutter

The Android SDK is distributed as dev.everframe Maven modules through Maven Central. Tagged Apple releases can be consumed with Swift Package Manager from this repository. Their documentation contains the current coordinates, products, and setup instructions.

Examples

The examples directory contains runnable hosts for the supported platforms and integration styles:

ExampleDemonstrates
react-webReact web integration and SSR/CSP fixtures
vue-webFramework-agnostic SDK integration from Vue
smarttv-testerBrowser-based Smart TV behavior
react-nativeReact Native bridge integration
flutter-android-probeFlutter Android source and privacy probe
flutter-ios-probeFlutter iOS source and privacy probe
react-tv-sampleReact Native TV host integration
android-composeNative Android with Jetpack Compose
android-viewsNative Android with the Views system
ios-nativeNative iOS integration
tvos-replayCredential-free tvOS replay and remote-focus smoke testing

Examples that connect to Everframe read development credentials from generated, ignored configuration. Start from the checked-in template:

sh
cp .env.example .env

Fill only the values required by the example you are running. Never commit SDK keys, identity secrets, generated platform configuration, or production data.

Contributing

JavaScript development requires Node.js 22 and pnpm 9.15. Android development also requires a compatible JDK and Android SDK; Apple development requires Xcode.

sh
git clone https://github.com/scriptx-com/everframe.gitcd everframecorepack enablepnpm install --frozen-lockfile

Run the same JavaScript workspace checks used by CI:

sh
pnpm test:boundarypnpm check:boundarypnpm build:packagespnpm test:packagespnpm typecheck:packagespnpm build:examplespnpm test:examplespnpm typecheck:examplespnpm check:publish

Run native checks from their platform projects:

sh
# Androidcd packages/sdk-android/android./gradlew test assembleRelease
# Apple, from the repository rootEVERFRAME_DEV_INGEST_URL=http://127.0.0.1:9 \  swift test --package-path packages/sdk-ios --no-parallel

See CONTRIBUTING.md for contribution and licensing rules.

Releases

JavaScript packages are published to npm, the Flutter plugin is published to pub.dev, Android artifacts are published as Maven packages, and tagged Apple releases provide binary XCFrameworks for Swift Package Manager consumers.

The Android and KMP Maven artifacts share one version and one Central Portal upload. Run pnpm build:mobile-maven-bundle with SIGNING_KEY and SIGNING_PASSWORD set to build and verify the signed bundle. Use pnpm build:mobile-maven-bundle --prepare to inspect an unsigned bundle before signing; that ZIP cannot be uploaded to Maven Central.

The root Package.swift is the binary manifest used by Apple SDK consumers. Source development and tests use packages/sdk-ios/Package.swift.

Security

Please report vulnerabilities privately as described in SECURITY.md. The repository's publication gates check the allowed public file boundary, SPDX metadata, committed content, and Git history before release.

License

ScriptX-owned source is available under the MIT License. Bundled upstream files retain their original licenses; see LICENSES and REUSE.toml.

Source: README.md at commit 1f8bc44

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 3, 2026