Everr
dev.everr/everr · 55 stars · TypeScript · AGPL-3.0
MCP server Query your traces, logs, metrics and GitHub Actions CI runs in Everr with read-only SQL.
Listed in: Best MCP servers for GitHub
Install
The repo has no one-line install. Follow its README.
Published as
- Remote
https://app.everr.dev/mcpStreamable HTTP
From the server's entry in the official MCP Registry.
Files
Self-hosted application
@everr/app is the complete self-hosted application and the base for
@everr/app-cloud. It owns shared product features and the defaults needed to run
one workspace. Cloud composes those features and supplies its own policy and
cloud capabilities. The app must remain usable without importing or depending
on cloud.
For installation, configuration, deployment, and account recovery, see the deployment guide. For migration ownership and database compatibility, see DATABASE-MIGRATIONS.md.
Ownership
Shared features own their behavior and server-side authorization. Application
specific decisions enter through typed contracts in src/composition, exported
from @everr/app/composition. Each application provides adapters in its own
src/app/composition directory. Keep contracts type-only so importing a
contract does not load an application's implementation.
The self-hosted app owns the single-workspace installation flow, its default identity and retention policies, and the shared feature implementations. Cloud owns billing, usage metering, tenant provisioning, commercial policy, and its Polar integration. Shared code should depend on the narrow contract for the behavior it needs, not on cloud modules or application implementation paths.
Server responsibilities are separated by workflow: runtime manages migrations
and workers; entry handles installation, signup, and guarded organization
entry; deployment configuration provides the ingest endpoint; identity owns
authentication and membership lifecycle behavior, including shared endpoint
guards. Account preflight stays alongside identity. After membership validation,
getActiveOrganizationAccess calls getOrganizationEntryRedirect(session) and
applies the returned destination while preserving returnTo. Cloud owns
organization creation cookies and continuation behavior. Identity adapters may
implement provider.beforeMembershipMutation for lock acquisition and
beforeMembershipChange or afterMembershipChange for application policy;
creation-only organization hooks remain separate. Shared endpoint guards remain
in place.
Identity composition selects two cohesive parts together: policy contains
signup admission, account-deletion preflight, and membership/deletion rules;
provider contains Better Auth persistence, plugins, organization-creation hooks,
session onboarding, and request-wide locking. Signup policy receives an invitation
ID rather than provider endpoint context. The identity module translates policy
denials into provider responses and retains ownership of shared guards.
Authentication is exposed through the explicitly server-only
@everr/app/identity/server entry; browser identity
and role helpers use @everr/app/identity/client and @everr/app/identity/roles.
Keep provider internals inside src/identity.
createApplicationAuth in @everr/app/identity/module constructs identity from
the selected policy/provider adapter, a database, authentication settings, mail
delivery, and invitation eligibility. Importing this constructor does not read
environment settings or create database clients. identity/server is the
production composition entry. Database and request-lock constructors likewise
accept explicit configuration or pools; application composition owns their
instances. Tests can construct independent identities with disposable databases
and external-provider doubles without replacing global modules.
Call auth.deleteAccount({ headers, deleteOrganization }) for account deletion.
Identity resolves an uncached session and checks the authentication provider's
freshness requirement before any deletion. It discovers organization IDs, acquires
application-owned locks through provider.lockAccountDeletion, then reads current
ownership and application policy while holding those locks through provider writes. Callers do
not manage identity locks or account-deletion preflight. Organization deletion
and user deletion are separate provider commits; if the second operation fails,
the error explicitly reports that the organization was already deleted and
preserves the original cause.
The provider's user.deleteUser.beforeDelete uses the same ownership and
application-policy guard before credential or session cleanup begins. Server
callers use auth.deleteAccount; HTTP deletion and token callbacks enter through
the request-scoped auth.handler. Before discovering memberships, deletion takes
provider.lockUserLifecycle. Shared organization creation takes the same lock,
rechecks that the creator exists, and retains it through creation and its hooks.
auth.api.createOrganization supplies the request scope for server callers,
including onboarding and checkout callbacks. Cloud uses a per-user lock;
the installation reuses its workspace lock. Contention fails immediately, so
creation and billing can acquire their other locks without waiting in a cycle.
Expected identity policy denials throw IdentityPolicyError, exported from
@everr/app/identity/policy-error. Identity translates them to forbidden provider
responses. Application adapters translate their own business denials into this
type and propagate database or external-provider failures unchanged.
Cloud organization creation, checkout completion, and downgrade are owned by
cloud's organizations/commands.server.ts. Request handlers validate input and
pass the authenticated actor to that workflow. The workflow owns eligibility,
lock ordering, billing coordination, and persistence. Infrastructure exports such
as database executors and migrations remain available for transactional extensions.
Shared membership mutations belong to @everr/app/identity/memberships.
restrictOrganizationToOwner checks the retained Owner, removes other Members,
and cancels pending invitations within the caller's transaction. Cloud owns
downgrade eligibility and billing coordination and composes this shared operation
with its plan update. The operation returns the actual removed Membership IDs
for publication after that transaction commits; the shared module imports no
cloud billing types.
Extending the application
-
Use ordinary component props and
childrenwhen adding content to a shared component. For example, account composition keeps shared profile and session behavior while supplying the application's account-lifecycle action:account: (props) => ( <AccountSettings {...props}> <AccountDeletion /> </AccountSettings> ),Keep shared authorization checks around actions restricted to administrators or signed-in users.
-
Compose a page when an application needs different data loading or rendering.
ApplicationPages.memberscan provide both. Itsloadfunction may prefetch data, and its component owns rendering:members: { async load({ queryClient, organizationId }) { await queryClient.fetchQuery(membersPolicy(organizationId)); }, component: MembersPage, },Shared routes continue to own authentication and authorization guards.
-
Register new application routes explicitly in
AppComposition.routes. A route declaration names its mount point, URL path, and source file:import { resolve } from "node:path"; import type { AppComposition } from "@everr/app/build/composition"; export const composition: AppComposition = { directory: import.meta.dirname, routes: { signedIn: [ { type: "route", path: "settings", file: resolve(import.meta.dirname, "src/routes/settings.tsx"), }, ], }, };Shared routes retain file-based discovery. After changing routes, regenerate the application's checked-in TanStack route tree by running its development server or build. Do not add a component or feature registry for contributions.
-
Keep application policy in its adapter. Shared identity code owns membership endpoint quirks and normalizes lifecycle behavior before invoking application hooks, so an adapter cannot replace the shared membership and deletion guards.
Each application's tsconfig.json selects a complete set of named
@composition/* modules. Vite and Vitest use the same selection. The root
pnpm run check command checks package imports and composition contracts.
It also keeps identity policy free of authentication-provider dependencies,
provider internals private, browser composition free of server implementations,
and cloud request handlers free of direct database coordination. Browser pages
may consume explicit server-function interfaces. These rules preserve the existing
named adapters; new seams should correspond to behavior that actually varies.
Navigation uses the selected application's generated TanStack route types. Use
literal route patterns with params for dynamic destinations. Shared navigation
lists accept only parameter-free ApplicationPath values; RailRow preserves
TanStack's route, params, and search inference. Breadcrumb segments accept a
link element so each route can declare a fully typed <Link /> directly.
Compile-only navigation checks run with both applications' typecheck commands
and verify that invalid routes, params, search, and cross-application links fail.
When changing migration behavior or supported upgrade paths, update the migration guide. When changing installation, deployment, or recovery procedures, update the deployment guide.
Local development
Follow the worktree development guide, then run from the repository root:
pnpm install pnpm dev # Or use the interactive process interface: pnpm dev --tui
App and Cloud run together with separate databases, users, and host collectors.
The launcher supplies local connection settings and credentials. On first startup
in an unconfigured worktree, it copies each application's .env from the main
worktree. The applications load those files for integration settings. See
.env.example for available settings.
Shared ClickHouse databases, base users, table definitions, and SQL query limits
live in packages/app/clickhouse. A file tagged self-hosted or cloud after its
number (0012-cloud-apply-rls.sql) applies to that product only.
Each application applies them on startup to its own ClickHouse container, using the
same app and otel database names. See DATABASE-MIGRATIONS.md.
Each worktree has its own database volumes and Portless URLs. Ctrl+C stops the
stack while retaining database data. In TUI mode, confirm the quit dialog.
Telemetry
Create an ingest key in the application and send OTLP/HTTP to its printed Portless ingest URL. App and Cloud use separate collectors and key-verification endpoints. The self-hosted App collector buffers in memory; Cloud retains persistent queues and usage accounting. Self-hosted reads do not filter by tenant.
Production self-hosted uses the separate deployment stack. Configure exporters with the installation's public ingestion URL and an ingest key.
Shared identity publishes User, Organization, and Membership lifecycle facts
through EventPublisher<IdentityEvent>. identity/identity-adapter.ts captures
persisted before/after identity under locks and publishes after its outermost
source transaction commits. Better Auth 1.6.33 also runs queued database
after-hooks following rollback, so those hooks are not the publication boundary.
Providers build adapters for the supplied database executor to preserve their
billing and Organization lifecycle checks inside nested transactions. Installation
setup publishes User, Organization, and initial Membership creation after its own
transaction commits. Onboarding publishes its Organization update after its
standalone statement succeeds. Membership facts retain the persisted relationship
ID plus its User and Organization IDs. Parent deletion facts require cleanup of
all remote associations for that parent; database cascades do not fabricate child
facts. The self-hosted composition selects no CRM routes.
Business event publication diagnostics reuse the server OTel providers. The error
log business_events.publication.failed carries event type, version, event and
subject IDs, and the failure stage (validation, job, or enqueue). Enqueue
failures also identify the Graphile task. Exception attributes describe the
error; job construction messages and stacks are redacted. See the
event bus guide for the emitted-event
catalog, direct Graphile admission, handler wiring and accepted loss.
For an isolated local verification, set OTEL_EXPORTER_OTLP_ENDPOINT to the OTLP
origin returned by that instance's status, then start the app. For deployed server
export, configure EVERR_INGEST_ENDPOINT and secret EVERR_INGEST_KEY, restart
the app, and query that installation for the log after exercising a
publication failure. An explicit OTEL_EXPORTER_OTLP_ENDPOINT takes precedence
and does not add the Everr ingest-key header. No new exporter configuration or
production activation is introduced by the publisher. Local test ingestion does
not prove production ingestion.
Useful package commands include pnpm --filter @everr/app build,
pnpm --filter @everr/app typecheck, and
pnpm --filter @everr/app test:ci. Run pnpm run check from the
repository root to check package imports.
Facts
- Kind
- MCP server
- Repo
- everr-labs/everr
- Group
- Uncategorized
- Stars
- 55
- License
- AGPL-3.0
- Language
- TypeScript
- Last push
- 2026-11-15
- MCP Registry
- dev.everr/everr
- Homepage
- everr.dev
- Topics
- ai-tools, ci-cd, claude-code, codex, developer-tools, observability, performance, testing
Also in Best MCP servers for GitHub
- 24GitHubgithub/github-mcp-serverGitHub's official MCP Server34.5k
- 39GitDiagramcom.gitdiagram/gitdiagramArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.18.9k
- 1223io.github.Dave-London/pare-githubio.github.Dave-London/pare-githubPare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.141
Also new this week
- 5HyperFrames by HeyGenio.github.heygen-com/hyperframesOfficial HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.84.8k
- 29OpenSEOcom.everyapp/openseoKeyword research, site audits, rank tracking and AI visibility for your AI agent.27.8k
- 50e2eio.github.e2e-inc/e2eOpen live web and mobile app sessions from an e2e project to inspect the app and try locators.13.9k