Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Cross-chain bridge aggregator — compares LI.FI, deBridge, Relay, Across & more for best rates.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
LIFI_API_KEY, SQUID_INTEGRATOR_ID标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"bridgekitty": {
"command": "npx",
"args": [
"-y",
"@persistenceone/bridgekitty"
],
"env": {
"LIFI_API_KEY": "your-value",
"SQUID_INTEGRATOR_ID": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add bridgekitty --env LIFI_API_KEY=your-value --env SQUID_INTEGRATOR_ID=your-value -- npx -y @persistenceone/bridgekitty运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"bridgekitty": {
"command": "npx",
"args": [
"-y",
"@persistenceone/bridgekitty"
],
"env": {
"LIFI_API_KEY": "your-value",
"SQUID_INTEGRATOR_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"bridgekitty": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@persistenceone/bridgekitty"
],
"env": {
"LIFI_API_KEY": "your-value",
"SQUID_INTEGRATOR_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SQUID_INTEGRATOR_ID env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 persistenceOne 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:LIFI_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.1)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Cross-chain bridge aggregator MCP server for AI agents. One server, 5 bridge backends, best routes across EVM, Solana, and Cosmos chains.
BridgeKitty gives AI agents (Claude, Cursor, GPT, or any MCP-compatible AI) the ability to find and execute cross-chain bridge transfers — with automatic route optimization, fee comparison, balance checks, and safety warnings.
Latest npm release: @persistenceone/bridgekitty@0.3.9
xprt-farming-toolkit packageWhat's New in v0.3.0
What's New in v0.2.0
| Backend | Type | Chains | Strength |
|---|---|---|---|
| deBridge (DLN) | Direct | EVM + Solana | Fast intent-based fills, Solana support |
| Relay | Direct | EVM + Solana | No protocol fee, gas-optimized |
| LI.FI | Aggregator | EVM | Widest coverage (30+ bridges, any-to-any swap) |
| Across | Direct | EVM | Fastest fills (~6s), same-token bridging |
| Squid (Axelar) | Aggregator | EVM + Cosmos | Only option for EVM → Cosmos routes |
| Direction | Backends | Status |
|---|---|---|
| EVM → EVM | All 5 | ✅ Production |
| EVM → Solana | deBridge, Relay | ✅ Production |
| Solana → EVM | deBridge | ✅ Production |
| EVM → Cosmos | Squid | ✅ Production |
npx @persistenceone/bridgekitty
Add to your MCP config (~/.claude/claude_code_config.json):
{
"mcpServers": { "bridgekitty": { "command": "npx", "args": ["@persistenceone/bridgekitty"] } } }
Add to Cursor's MCP settings (Settings > MCP Servers):
{
"bridgekitty": { "command": "npx", "args": ["@persistenceone/bridgekitty"] } }
Add to claude_desktop_config.json:
{
"mcpServers": { "bridgekitty": { "command": "npx", "args": ["@persistenceone/bridgekitty"] } } }
BridgeKitty can manage wallets for autonomous bridging. Run wallet_setup to create wallets for EVM, Cosmos, and Solana — or provide your own addresses in quotes.
Wallet config is stored in ~/.bridgekitty/.env (or the directory you run from). Keys never leave the local machine.
| Variable | Description |
|---|---|
PRIVATE_KEY | EVM private key (hex) |
MNEMONIC | BIP-39 mnemonic (derives EVM, Cosmos, Solana keys) |
SOLANA_PRIVATE_KEY | Solana private key (base58) |
By default, bridge_execute returns unsigned transactions for the agent or user to sign externally.
Set sign_and_send: true to enable autonomous signing — BridgeKitty will use the wallet keys stored in ~/.bridgekitty/.env to handle the full flow:
eth_estimateGas pre-flight check| Variable | Description |
|---|---|
LIFI_API_KEY | LI.FI API key (higher rate limits) |
DEBRIDGE_API_KEY | deBridge API key |
SQUID_INTEGRATOR_ID | Squid integrator ID |
| Tool | Description |
|---|---|
bridge_get_quote | Get competitive quotes from all backends. Shows fees, time estimates, balance warnings. |
bridge_execute | Build transaction(s) from a quote. Handles approvals, auto-refreshes expired quotes. Set sign_and_send: true to auto-sign and broadcast. |
bridge_status | Track bridge progress. On-chain fallback when API hasn't indexed yet. |
bridge_chains | List supported chains with provider coverage. |
bridge_tokens | Search tokens on a chain. |
| Tool | Description |
|---|---|
bridge_quote_multi | Multi-hop route resolution when no direct route exists. |
bridgekitty_help | Agent onboarding guide with examples and tool usage. |
xprt_onboard | Guided onboarding flow for first-time users. |
| Tool | Description |
|---|---|
wallet_setup | Create wallets for EVM, Cosmos, Solana from a single mnemonic. |
wallet_import | Import an existing wallet from a mnemonic or private key. |
wallet_status | Show configured wallet addresses and key source. |
wallet_balance | Check balances across all chains with USD prices (CoinGecko). |
XPRT staking & farming has moved to the standalone
xprt-farming-toolkitpackage.
Agent: "Bridge 100 USDC from Base to Arbitrum"
→ bridge_get_quote: Gets quotes from deBridge, Relay, LI.FI, Across → Shows: best rate, fees, estimated time, balance check → bridge_execute: Builds approval tx + bridge tx → Agent signs and sends both transactions → bridge_status: Tracks until destination confirmed
Agent: "Bridge 100 USDC from Base to Arbitrum"
→ bridge_get_quote: Gets quotes from all backends → bridge_execute with sign_and_send: true → Auto-signs approval tx + bridge tx using local wallet keys → Returns tx hash + explorer link → bridge_status: Tracks until destination confirmed
Agent → MCP Tools → Routing Engine → [deBridge, Relay, LI.FI, Across, Squid]
↓ Quote Cache (60s) + Circuit Breaker ↓ Best Quote → buildTransaction ↓ ┌──────────┴──────────┐ ↓ ↓ Unsigned TX Signed + Broadcast (default) (sign_and_send)
sign_and_send uses locally-stored keys only (never transmitted over the network).env file permission checks + overwrite protectionwallet_balance (only native SOL)MIT