Endor

Created By
endorhqa year ago
Endor lets your AI agents run services like MariaDB, Postgres, Redis, Memcached, Alpine, or Valkey in isolated sandboxes. Get pre-configured applications that boot in less than 5 seconds, with direct AI agent integration for instant development and testing environments.
Overview

Endor MCP Server

Endor enables AI agents to run isolated services and create development and testing environments instantly.

Endor provides a foundation layer for AI tools, providing isolated services that run in seconds.

Installation Guides

What AI Agents Can Do

Once configured, your AI agents can:

  • Start services instantly: MariaDB, PostgreSQL, Redis, Valkey, and more
  • Create isolated environments: Each service runs in its own sandbox
  • Run commands: Execute any Linux command in isolated environments
  • Test integrations: Spin up services for testing without local installation

AI agents automatically identify when to use Endor based on your development needs, making database and service management seamless.

Available Services

Endor provides the following pre-configured services:

  • Alpine Linux: Lightweight container for general development
  • MariaDB: MySQL-compatible database server
  • PostgreSQL: Advanced relational database
  • Redis: In-memory data structure store
  • Valkey: Redis-compatible cache server
  • Memcached: High-performance caching system

All services boot in less than 5 seconds and run in isolated Alpine Linux Virtual Machine.

Documentation

For detailed setup instructions and usage examples, visit: https://docs.endor.dev

Server Config

{
  "mcpServers": {
    "endor": {
      "command": "npx -y @endorhq/cli@latest",
      "args": [
        "mcp",
        "--allow-net"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
endorhq
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago