What does the server actually do?
It wraps your Ebitengine game so that Cursor can communicate with it through the Model Context Protocol. You only need to call `mcp.Wrap(&Game{})` inside `ebiten.RunGame`.
@sedyh
基本情報
Ebitengine MCP server for Cursor
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
Ebitengine Recorder MCP for Cursor is an MCP (Model Context Protocol) server that wraps an Ebitengine game before passing it to ebiten.RunGame, enabling Cursor to interact with the game via the MCP protocol. It is intended for developers building games with Ebitengine who want to use Cursor's AI features with their game context.
Wrap your game with mcp.Wrap(&Game{}) inside ebiten.RunGame. Then add the provided JSON configuration to your MCP servers, specifying the command go run github.com/sedyh/ebitengine-mcp/cmd/trun with arguments ["." , "-mcp"].
go run – no prebuilt binary required.It wraps your Ebitengine game so that Cursor can communicate with it through the Model Context Protocol. You only need to call `mcp.Wrap(&Game{})` inside `ebiten.RunGame`.
Add the JSON configuration to your MCP servers list in Cursor. When Cursor starts the server, it runs `go run github.com/sedyh/ebitengine-mcp/cmd/trun` in your project directory.
You need Go installed, along with the Ebitengine library and the `sedyh/ebitengine-mcp` package. The module will be fetched automatically when you use `go run`.
The README only shows a fixed command with arguments `["." , "-mcp"]`. No other configuration or options are documented.
The README does not mention any authentication or transport security. It uses the default MCP transport (likely stdio, as common for local MCP servers).
Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

Turn a plain-language guide into a narrated walkthrough video of your deployed web app. Your coding agent can write the guide from the source and bring back the MP4.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

AI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·
コメント