FastMCP FastMCP
Sign In
iExec MCP Server Logo

iExec MCP Server

Official

An MCP server that enables AI agents to interact with the iExec protocol for confidential data manag...

7 views
0 installs
Updated Jan 19, 2026
Not audited
Security Developer Tools
Tools I Recommend
ShipFast ShipFast Sponsor ClaudeKit ClaudeKit Sponsor RunPod RunPod Sponsor
An MCP server that enables AI agents to interact with the iExec protocol for confidential data management, governance, and Web3Mail services. It allows users to protect sensitive information, manage access permissions, and perform blockchain wallet operations through natural language commands.

  1. Open the FastMCP connection interface and click the "Install Now" button to add a new MCP server entry — the ENV values below must be filled into that FastMCP connection form.

  2. Decide which secret method you will use:

    • Option A — use a wallet file (recommended for production): set ENV key PRIVATE_KEY_PATH to the absolute path of your wallet.json.
    • Option B — use a raw private key (convenient for quick tests): set ENV key PRIVATE_KEY to your private key value (prefixed with 0x).

  3. If you choose Option A (create or use wallet file):

    1. Create a new iExec wallet (or use an existing one):
      • Install iExec CLI (if needed): npm install -g iexec
      • Create an unencrypted wallet: iexec wallet create --unencrypted
    2. Locate the generated wallet file (absolute path):
      • Linux: ~/.ethereum/keystore/wallet.json
        • Get absolute path: realpath ~/.ethereum/keystore/wallet.json
      • macOS: ~/Library/Ethereum/keystore/wallet.json
        • Get absolute path: realpath ~/Library/Ethereum/keystore/wallet.json
      • Windows (PowerShell): %APPDATA%\Ethereum\keystore\wallet.json
        • Get absolute path in PowerShell: Resolve-Path $env:APPDATA\Ethereum\keystore\wallet.json
    3. In the FastMCP connection form (after clicking "Install Now"):
      • Set ENV name: PRIVATE_KEY_PATH
      • Set ENV value: the absolute path you obtained (e.g., /home/alice/.ethereum/keystore/wallet.json or C:\Users\Alice\AppData\Roaming\Ethereum\keystore\wallet.json)
    4. Save/apply the FastMCP entry.

  4. If you choose Option B (use raw private key):

    1. Place your private key string (0x...) somewhere secure, or create a local wallet file:
      • To create a local wallet.json (example):
        mkdir -p ./my-wallet
        echo '{"privateKey":"0xYOUR_PRIVATE_KEY"}' > ./my-wallet/wallet.json
      • Get the absolute path if you will use the file (see Step 3.2).
    2. In the FastMCP connection form (after clicking "Install Now"):
      • Either set ENV name: PRIVATE_KEY and ENV value: 0xYOUR_PRIVATE_KEY
      • Or set ENV name: PRIVATE_KEY_PATH and ENV value: absolute path to the wallet.json created above
    3. Save/apply the FastMCP entry.

  5. Notes for Docker or containerized MCP entries:

    • If your MCP entry uses Docker and you specify PRIVATE_KEY_PATH, you must also mount the host directory containing wallet.json into the container and use the container path in PRIVATE_KEY_PATH (e.g., host /home/alice/keystore -> container /app/keystore, then set PRIVATE_KEY_PATH to /app/keystore/wallet.json).
    • If you use PRIVATE_KEY (raw key) you only need to set that ENV in FastMCP.

  6. After saving the FastMCP entry:

    • Restart or re-install the MCP connection using the FastMCP interface if required.
    • Verify the server connects successfully (the MCP tool should report an active/plugged server).

  7. Security reminders (must follow):

    • Prefer PRIVATE_KEY_PATH (wallet file) for production; do not paste raw keys into long-lived or shared configurations.
    • Never commit PRIVATE_KEY or wallet.json into source control.
    • Keep your wallet file and private key offline and secure; the iExec MCP server runs locally and the key is not transmitted externally.

Quick Start

View on GitHub

More for Security

View All →

More for Developer Tools

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.