Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"solana-kit": {
"command": "npx",
"args": [
"-y",
"@xgamesfun/solana",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add solana-kit -- npx -y @xgamesfun/solana mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"solana-kit": {
"command": "npx",
"args": [
"-y",
"@xgamesfun/solana",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"solana-kit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@xgamesfun/solana",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 XGamesFun 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.20.1)于8天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Figma Context MCP, Claude Real Video, Figma MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
The Figma MCP server brings Figma design context directly into your AI workflow.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The tools for loot, one shared Solana program for game and community economies. This repository is the npm package @xgamesfun/solana:
@xgamesfun/solana/client), a player module for apps (/play) and a results client (/results);xsolana CLI and an MCP server with ten xsolana_* tools;xsolana-economy skill, and one plugin that carries the tools and the skill to Claude Code and Codex;An economy is a JSON spec, not a new smart contract. Every project shares the one program, and none writes its own.
Status: loot 0.22.0, program ID
9cwqM1TXytPnFZsLfmUyv2dg4uW6Ch9C6UJVPns7NFQ, devnet only. The program is
not independently audited, and nothing runs on mainnet until it is. See SECURITY.md.
Disclaimer: provided as is, with no warranty and no guarantee that the program or the tools are safe. Use them
at your own risk; you are responsible for every transaction you approve and for making sure what you build is legal
where it runs. Nothing here is legal or financial advice. Read DISCLAIMER.md before you use it.
Every move leaves a public receipt. docs/program.md describes how the program behaves.
The MCP server and the skill let Claude Code, Codex or any MCP agent turn a one-line idea into a checked, simulated economy and hand you the command that puts it live in your own wallet.
Claude Code
/plugin marketplace add XGamesFun/solana-kit
/plugin install xsolana@xgamesfun
Codex
codex plugin marketplace add XGamesFun/solana-kit
codex plugin add xsolana@xgamesfun
Any agent with MCP (Cursor, opencode, Cline…): run the server with npx -y --package=@xgamesfun/solana@0.22.0 xsolana mcp. Or let npx -y @xgamesfun/solana@0.22.0 connect register it, with the skill, for Claude Code and Codex.
Then ask for an economy, for example *"a fishing game where each cast costs 0.02 SOL, with a rare golden fish and a monthly draw"*.
Going live is always yours: npx -y @xgamesfun/solana@0.22.0 approve opens a page on your computer where you connect a devnet wallet and approve each transaction. The agent never signs and never asks for a key.
Every tool runs from the CLI too, on a spec file (xsolana.json by default):
npx -y @xgamesfun/solana@0.22.0 examples shop with loot boxes # the nearest worked examples
npx -y @xgamesfun/solana@0.22.0 check xsolana.json # refusals and warnings npx -y @xgamesfun/solana@0.22.0 simulate xsolana.json # where the money goes, day by day npx -y @xgamesfun/solana@0.22.0 cost xsolana.json # what going live and each action cost npx -y @xgamesfun/solana@0.22.0 explain xsolana.json # the economy in plain words npx -y @xgamesfun/solana@0.22.0 approve xsolana.json # go live, approved in your own wallet
xsolana help lists every command. Every command names the exact version, so npx runs that release and never whatever is newest under the name.
npm install @xgamesfun/solana
import * as loot from '@xgamesfun/solana/client';
const ix = loot.openBoxIx({ player, project, box, nonce }); // one builder per instruction, no Solana SDK
| Import | What |
|---|---|
@xgamesfun/solana | the economy tools: check, simulate, plan, cost, explainEconomy, model |
@xgamesfun/solana/client | every PDA, one builder per instruction, account and receipt decoders, grant vouchers |
@xgamesfun/solana/play | solanaApp: what a player does with a live economy, from a browser app |
@xgamesfun/solana/results | results and vouchers a game's server signs |
@xgamesfun/solana/chain/* | browser-safe Solana primitives: base58, Borsh, transactions, PDAs, tokens, Core |
@xgamesfun/solana/idl.json | the program's IDL, the authority for account and argument layouts |
@xgamesfun/solana/release.json | the program build, IDL and client this release is pinned to |
The client, chain and play modules run in browsers and Node 22 or later, with no bundler required. The package ships TypeScript declarations for every entry point.
docs/program.md | the program: who signs, accounts, every instruction, fees, limits, receipts, costs |
docs/nfts.md | NFTs and tokens, with and without the project's authority |
docs/harnesses.md | how the plugin reaches Claude Code and Codex, and the release checklist |
skills/xsolana-economy | the skill an agent follows |
examples/ | whole economies that check and go live in the tests; ideas.json, 112 real economies rated |
evals/ | fresh-session evals of agents building on loot |
CHANGELOG.md, SECURITY.md | versions, the trust model, reporting a vulnerability |
| Path | What |
|---|---|
js/chain/ | browser-safe Solana primitives, no SDK |
js/client/ | the client; idl/ is the program's IDL |
js/economy/ | the economy spec (version 2, schema.json), checker, simulation, setup plan, cost, explainer, guide |
js/play/, js/results/ | a player's side of a live economy; results a server vouches for |
js/approve/, js/mcp/, js/connect/ | the approval page, the MCP server and its tools, xsolana connect |
js/sim/, js/test/ | LiteSVM running the real program; the tests and their pinned fixtures |
bin/xsolana.mjs | the CLI |
skills/, plugin/ | the skill (copied to plugin/skills, .claude/skills, .agents/skills) and the plugin |
scripts/ | fixtures, skill sync, IDL sync, release manifest, a devnet end-to-end run |
release.json | the program binary, IDL and client hashes this version is pinned to |
Node 22 or later.
npm ci
npm run fixtures # downloads the loot program from devnet and the programs it calls from mainnet, each checked by hash npm test # every instruction the client builds, and every example's whole setup, against the real program in LiteSVM npm run lint # ESLint npm run check # fixtures, skill copies and release.json in step, lint, then the tests
Nothing in the tests deploys or spends SOL.
| Variable | What it does |
|---|---|
XSOLANA_RPC_URL | a devnet RPC of your own for xsolana approve and xsolana status (a mainnet URL is refused) |
XSOLANA_NO_OPEN | xsolana approve prints its link without opening a browser |
XSOLANA_DEBUG | the CLI prints a failure's whole stack, not one line |
| XSOLANA_PROGRAM_DIR | the tests run that program build's target/deploy/loot.so, and check the IDL against it | To try the tools in your own agent from a clone, node bin/xsolana.mjs connect --local registers this checkout's MCP server and the skill with Claude Code and Codex (--remove takes them out again).
After editing skills/, run npm run sync-skills. Changes to tool texts, the skill or the plugin are best measured with the evals before and after (evals/README.md). AGENTS.md has the rules for working in this repository, for people and coding agents alike.
Issues and pull requests are welcome: see CONTRIBUTING.md. Please run npm run check before sending a change, and report a vulnerability privately as SECURITY.md describes.
Apache-2.0. See NOTICE and DISCLAIMER.md: provided as is, without warranty, at your own risk.