mcpField
S
StablecoinX

StablecoinX

Local
harness.stablecoinx.comFinance
RepositoryVisit website

About StablecoinX

StablecoinX merchant tools: auth, payments, paymaster, webhooks, floYsh sites and vault settings

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "e2xlabs-stablecoinx": {
      "command": "npx",
      "args": [
        "-y",
        "@stablecoinx/mcp"
      ],
      "env": {
        "SCX_STATE_PASSPHRASE": "<SCX_STATE_PASSPHRASE>",
        "SCX_STATE_DIR": "<SCX_STATE_DIR>"
      }
    }
  }
}
Run commandnpx -y @stablecoinx/mcp
Environment variables to set
SCX_STATE_PASSPHRASESecretPassphrase used to encrypt the local state file (JWT / API key / session key) at rest. Pick any string. The harness endpoint, thirdweb client, origin and login chain are baked into the package — this is the only required input.
SCX_STATE_DIROptional. Directory for the encrypted local state file. Defaults to %APPDATA%/stablecoinx-mcp (Windows) or $XDG_CONFIG_HOME/stablecoinx-mcp.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@stablecoinx/mcp0.2.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.