Yokai MCP Server Template

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

What is Yokai MCP Template?

Yokai MCP Template is a server template based on the Yokai Go framework, designed to facilitate the development of Model Context Protocol (MCP) servers.

How to use Yokai MCP Template?

To use the Yokai MCP Template, you can create a repository using the GitHub template or install it using gonew. After setting up, run the command make fresh to start the application.

Key features of Yokai MCP Template?

  • Ready-to-extend Yokai application with MCP server module installed.
  • Pre-configured development environment using Docker for live reloading.
  • Includes a Dockerfile for production deployment.
  • Examples of MCP tools and tests to help you get started.

Use cases of Yokai MCP Template?

  1. Developing custom MCP servers for various applications.
  2. Rapid prototyping of server functionalities using the provided template.
  3. Learning and experimenting with the Yokai framework and MCP concepts.

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 under the MIT license.

  • What programming language is used in the Yokai MCP Template?

The template is built using the Go programming language.

  • How can I contribute to the Yokai MCP Template?

You can contribute by submitting issues or pull requests on the GitHub repository.

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

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago