Yokai MCP Template 🏗️

Created By
Suraj1245a year ago
MCP server template based on the Yokai Go framework.
Overview

What is Yokai MCP Template?

Yokai MCP Template is a robust server template based on the Yokai Go framework, designed for building modular MCP servers with features for observability and dependency injection.

How to use Yokai MCP Template?

To use the Yokai MCP Template, clone the repository, install dependencies, build the application, and start the server using the provided commands.

Key features of Yokai MCP Template?

  • Modular Architecture: Easily extend your server with new modules.
  • Dependency Injection: Simplifies management of dependencies.
  • Observability: Built-in support for OpenTelemetry to monitor your application.
  • Lightweight: Fast performance with minimal overhead.
  • Go Language: Built with Go for speed and efficiency.

Use cases of Yokai MCP Template?

  1. Building scalable and maintainable MCP servers.
  2. Integrating observability features into applications.
  3. Developing modular applications with dependency management.

FAQ from Yokai MCP Template?

  • Is the Yokai MCP Template free to use?

Yes! The Yokai MCP Template is open-source and free to use.

  • What programming language is used?

The template is built using the Go programming language.

  • How can I contribute to the project?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Suraj1245
Star
0
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
Tavily Mcp
@tavily-ai

JavaScript
a year ago