Yokai

Created By
ankorstorea year ago
Simple, modular, and observable Go framework for backend applications.
Overview

What is Yokai?

Yokai is a simple, modular, and observable Go framework designed for building backend applications efficiently.

How to use Yokai?

To use Yokai, you can start by selecting one of the ready-to-use application templates for gRPC, HTTP, MCP, or worker applications, and follow the documentation for setup and configuration.

Key features of Yokai?

  • Modular architecture allowing easy extension with built-in and custom modules.
  • Built-in observability features including logging, tracing, and metrics instrumentation.
  • Dependency injection system to manage application components seamlessly.

Use cases of Yokai?

  1. Developing production-grade backend applications with minimal boilerplate code.
  2. Creating microservices using gRPC or HTTP protocols.
  3. Implementing observability in applications for better monitoring and debugging.

FAQ from Yokai?

  • Is Yokai suitable for large-scale applications?

Yes! Yokai is designed to handle production-grade applications with modularity and observability in mind.

  • What programming language is Yokai built with?

Yokai is built using Go, specifically designed for backend development.

  • How can I contribute to Yokai?

Contributions are welcome! Please follow the guidelines in the repository for contributing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ankorstore
Star
698
Language
Go
License
MIT license

Recommend Servers

View All
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