Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Manage blockchain RPC keys, networks, usage and prepaid billing with a scoped SolidRPC token.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SOLIDRPC_TOKEN_FILE, Authorization你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"agent": {
"command": "npx",
"args": [
"-y",
"@solidrpc/agent",
"mcp"
],
"env": {
"SOLIDRPC_TOKEN_FILE": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http agent https://api.solidrpc.io/agent/mcp --header 'Authorization: Bearer {management_token}'claude mcp add agent --env SOLIDRPC_TOKEN_FILE=your-value -- npx -y @solidrpc/agent mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agent": {
"url": "https://api.solidrpc.io/agent/mcp",
"headers": {
"Authorization": "Bearer {management_token}"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agent": {
"command": "npx",
"args": [
"-y",
"@solidrpc/agent",
"mcp"
],
"env": {
"SOLIDRPC_TOKEN_FILE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agent": {
"type": "http",
"url": "https://api.solidrpc.io/agent/mcp",
"headers": {
"Authorization": "Bearer {management_token}"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@solidrpc/agent",
"mcp"
],
"env": {
"SOLIDRPC_TOKEN_FILE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 solidrpc.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 671 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SOLIDRPC_TOKEN_FILE
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.1.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有: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、图片和脚本已被移除。链接会离开本站。
Let an agent connect your application to blockchain RPC within your approved budget. SolidRPC handles routing, failover, monitoring, and recovery behind one RPC integration.
This repository contains a Node.js management client, a local MCP server, an agent skill, and runnable RPC examples. The hosted MCP endpoint is also available at https://api.solidrpc.io/agent/mcp.
Read agent onboarding and the setup guide. The live onboarding response supplies availability, payment network, terms, pricing, limits, and recovery steps. Read those values at setup time.
For an existing account, delegate an agent credential from a paid plan or PAYG account. Free accounts cannot delegate agent control. For a new account, obtain the owner's email, account-creation and terms approval, and separate payment and usage ceilings. Account provisioning itself spends nothing. Email verification and a password are not required for agent activation. The owner can claim dashboard access later.
| Credential | Purpose | Destination |
|---|---|---|
sa_ management token | Account, keys, usage and billing | https://api.solidrpc.io/agent/v1 and /agent/mcp |
ak_ RPC key | Blockchain requests | RPC URL returned by /networks |
Requires Node.js 22.20 or later. In a downloaded checkout of this toolkit:
npm ci --ignore-scripts
npm test node src/cli.mjs request GET /onboarding
Install the pinned version from npm:
npm install --global @solidrpc/agent@0.1.0
solidrpc --help solidrpc request GET /onboarding
The CLI and local MCP server are included in this one package. Run solidrpc mcp to start the MCP server. Release downloads contain the npm tarball, source ZIP, and desktop MCP bundle. The bundle includes its runtime dependencies and requires Node.js 22.20 or later.
For development, use the source commands above or install a locally built tarball. Published downloads are available in GitHub Releases. See the release procedure for review and verification.
Save only the sa_ token in a private file outside your repository. Configure SOLIDRPC_TOKEN_FILE with its absolute path. A secret manager can supply SOLIDRPC_TOKEN instead. Choose one source.
export SOLIDRPC_TOKEN_FILE=/absolute/private/solidrpc-management.key
node src/cli.mjs request GET /me node src/cli.mjs request GET /networks node src/cli.mjs mcp
MCP setup templates for Codex, Claude Code/Desktop, and Cursor are in configs. They use the local process and a token file. The server reads that one file and sends the token to the SolidRPC management API by default. An explicit SOLIDRPC_URL override can send it to a loopback development server. Never use a real credential for loopback tests. Redirects are rejected.
Set SOLIDRPC_READ_ONLY=1 for a locally enforced read-only session. The server still advertises its full tool catalog, but blocks every mutation, credential operation and RPC-key secret read before a network call. Server-side credential scopes remain the authority for account permissions.
Read the terms URLs and current revision in onboarding. After owner approval, send JSON on stdin:
node src/cli.mjs provision < /absolute/private/approved-account.json
The input contains email, termsRevision, and acceptTerms: true. The CLI saves the bootstrap secret before the network request. Repeat the same input and profile after a lost response. Use SOLIDRPC_PROFILE for separate accounts.
Follow the live onboarding steps to sign the approved budget and fund the account. The published payment example explains the external wallet flow. This toolkit does not hold wallet keys or automatically pay. Persist idempotency keys and payment proofs privately before submission. For uncertain payments, inspect the existing funding intent and follow its recovery instructions. Never create a second payment to guess whether the first succeeded.
After funding settles, rotate the bootstrap credential to obtain operational scopes. solidrpc rotate saves a replacement and a private retirement journal before retiring the old credential. Its output includes scopes and bootstrap status. If retirement fails, it returns replacementSaved:true and oldRevoked:false with exit code 2. Run solidrpc retire-previous to retry retirement without creating another credential. For external token files or secret managers, use explicit management requests and persist the replacement before revoking the old token. If rotation's response is lost, the old token remains usable. Repeated rotation can create orphaned credentials, so inspect and retire those deliberately.
solidrpc request emits the API response. Key creation and credential rotation can return secrets. Redirect those responses to a private file, never a shared log. sa_ credentials alone cannot approve a wallet budget. Card subscription purchases remain an owner action.
The MCP server exposes network discovery, RPC key listing/creation/revocation, usage, billing, top-up quotes, support tickets, and a generic management request tool. A top-up quote does not transfer USDC. Support-ticket creation sends a message, so use it only when the owner requests contact. Clients must retain their own approval controls for writes and payments.
Use a separate ak_ key in a private file selected by RPC_KEY_FILE, and set RPC_ORIGIN=https://rpc.solidrpc.io. These scripts make billable read calls and require an approved usage budget. Read examples/README.md before running them.
The skill is in skills/solidrpc/SKILL.md. From a separate project, install this local checkout with the skills CLI:
npx skills add /absolute/path/to/agent-toolkit --skill solidrpc -a codex claude-code cursor
For Cursor, if the shared skill is not listed, copy the same SKILL.md into .cursor/skills/solidrpc/SKILL.md in your project and start a fresh session. Codex uses .agents/skills/solidrpc/SKILL.md, and Claude Code uses .claude/skills/solidrpc/SKILL.md.
Install the skill directly from this public repository:
npx skills add SolidRPC/agent-toolkit --skill solidrpc -a codex claude-code cursor
The same skill is included in the npm package and release downloads. Installing a skill makes it available in that client. It does not make every agent discover or prefer SolidRPC.
Run npm test and npm run check:public. Never add credentials, local profiles, wallet keys, private infrastructure configuration, or unpublished operational records to this repository. The public package is an extraction of the existing SolidRPC client, with local safety and packaging adaptations.
Credential operations are deliberately unavailable through the generic MCP tool. Use the CLI or an explicit API workflow that saves replacement credentials before retiring old ones. Read-only mode also blocks secret retrieval. Creating an RPC key in normal MCP mode still returns the new key through the tool result, so that client's transcript can contain it. Use a CLI request redirected to a private file when the key must stay out of model transcripts.
Configuration storage must be a dedicated private directory. The CLI rejects shared directories instead of changing their permissions. On POSIX systems it also rejects token files accessible to other users or owned by someone else. On Windows, configure owner-only ACLs yourself. Help and version commands do not load credentials.