vechain

VeChain MCP Server provides a set of tools to interact with the VeChain network via an MCP-enabled host. It exposes documentation lookup through the VeChain Docs section, Thor REST API access for accounts, transactions, blocks, and fees, and integrated wallet functionality for creating wallets and signing data. The Goat SDK included with the server offers wallet address and chain queries, message signing, balance checks (including ERC20 tokens), token information by ticker, unit conversions, and EVM-related signing and token approvals. To use the server, register it in your MCP host configuration, then issue queries such as search_documentation for VeChain API details, get_account to retrieve account data, get_block or get_transaction to inspect blockchain state, create_wallet to manage keys, sign_certificate or sign_raw_transaction for cryptographic operations, and use the Goat SDK endpoints for token operations and signing actions. The server is designed to work with both mainnet and testnet environments and supports streamable-http communication when deployed behind an MCP host that uses stdio streaming.

Prerequisites:

• Node.js installed on your machine (recommended LTS release)
• npm or pnpm installed
• Access to the repository where the VeChain MCP Server lives

Install and run locally:

1. Clone the repository or pull the project into your workspace.
2. Install dependencies (example with npm): npm install
3. If using npx to run the server package directly from the registry, ensure you have network access and run: npm run build (if a build script is provided by the project) npm run start (to start the server) or use the MCP host integration as described in the integration docs.

Environment and runtime:

• Ensure environment variables are set as described in the .env Config section (AGENT_SECRET_KEY, ENVIRONMENT, USE_STREAMABLE_HTTP, PORT, HOST).
• When using streamable-http, configure your MCP host to point to the vechainMcp server entry and provide the appropriate URL if needed by your host.

Verification:

• Confirm the server starts without errors and is reachable via the configured host/port.
• Use the included tools (Docs search, HTTP Thor API endpoints, wallet creation, signing operations, and Goat SDK calls) to validate functionality.

Environment variables are crucial for enabling signatures and network behavior. Ensure AGENT_SECRET_KEY is kept secret and variant values are provided for ENVIRONMENT (mainnet/test) and USE_STREAMABLE_HTTP depending on deployment. If running behind a reverse proxy or load balancer, ensure PORT and HOST are correctly exposed. The Goat SDK functions require wallet setup and proper token configurations when interacting with ERC20 tokens. If you encounter issues with npx package resolution, verify network access and package naming consistency with your npm registry. For local testing, you can use the provided pnpx/tsx workflow referenced in the repository README as an alternative to npx in some environments.