FastMCP FastMCP
Sign In
T

Thirdweb

Read/write to over 2k blockchains, enabling data querying, contract analysis/deployment, and transac...

3 views
0 installs
Updated Dec 25, 2025
Not audited
API Development Developer Tools
Read/write to over 2k blockchains, enabling data querying, contract analysis/deployment, and transaction execution, powered by Thirdweb.

  1. Open the FastMCP connection interface (click “Install Now”)
    Click the Install Now button to open the FastMCP / MCP connection form where environment variables are entered. You will paste each value below into the matching environment-variable field in that interface.

  2. Obtain THIRDWEB_SECRET_KEY (required)

    1. Sign in to your thirdweb dashboard (https://thirdweb.com/dashboard).
    2. Create or open the Project you want to use.
    3. Go to Project / API Keys (or Create API Key) and create a Secret Key (API Secret). Copy the secret key value immediately — secret keys are shown only once and must be stored securely. (portal.thirdweb.com)

  3. Paste THIRDWEB_SECRET_KEY into FastMCP
    In the FastMCP form, set the environment variable name THIRDWEB_SECRET_KEY and paste the secret key value you copied. Save the entry.

  4. Decide chain IDs you need and add them (optional / configuration choice)
    Determine the numeric chain IDs for the networks you want (e.g., 1 = Ethereum mainnet, 137 = Polygon). Add those chain IDs into the MCP server configuration or command arguments (or use the FastMCP field for chain settings if present).

  5. Obtain THIRDWEB_ENGINE_URL (if you will use Engine)

    1. In the thirdweb dashboard, navigate to the Engine tab and create (deploy) or import an Engine instance.
    2. Once created, copy the Engine URL provided for your instance — this is the base URL you will use for Engine API calls. (portal.thirdweb.com)

  6. Paste THIRDWEB_ENGINE_URL into FastMCP (optional)
    In the FastMCP form, set THIRDWEB_ENGINE_URL to the Engine URL you copied and save.

  7. Obtain an Engine authentication token (choose one method)
    Option A — Long-lived Engine Access Token (recommended for server-to-server):

    1. Open your Engine instance in the thirdweb dashboard → Access Tokens → Create Access Token.
    2. Copy the token (it is shown only once) and store it securely. Use this token as THIRDWEB_ENGINE_AUTH_JWT (or in the Authorization header for Engine). (portal.thirdweb.com)

    Option B — Keypair Authentication (short-lived JWTs):

    1. If you prefer keypair auth, follow the Engine Keypair Authentication guide: add your public key in the Engine dashboard, then sign short-lived JWTs with your private key per the Keypair Auth instructions and supply them per request. (This is an on-demand JWT flow rather than a single persistent secret.) (portal.thirdweb.com)

  8. Paste THIRDWEB_ENGINE_AUTH_JWT into FastMCP (if using Engine access token)
    If you created a long-lived Engine access token, set THIRDWEB_ENGINE_AUTH_JWT (or the env key your MCP expects) to that token in the FastMCP form and save.

  9. Get / confirm THIRDWEB_ENGINE_BACKEND_WALLET_ADDRESS (if using Engine backend wallets)

    1. In your Engine instance dashboard, create or import a backend/server wallet (Backend Wallets / Import).
    2. After adding the wallet, copy its wallet address (the backend-wallet address). Use this value for THIRDWEB_ENGINE_BACKEND_WALLET_ADDRESS in the FastMCP form. (blog.thirdweb.com)

  10. Obtain THIRDWEB_VAULT_ACCESS_TOKEN (if using EngineCloud / Vault-managed server wallets)

  1. If you use EngineCloud/EngineVault for server wallets, create an Access Token scoped to the operations you need via the Vault/Access Tokens flow. You can either:
    • Use the Vault UI / Engine dashboard Access Tokens area to create a token, or
    • Use the Vault SDK / API to create a base access token (engine/vault docs show how to create tokens programmatically using your project secret).
  2. Copy and securely store the Vault Access Token (it is shown only once). Supply this as THIRDWEB_VAULT_ACCESS_TOKEN. (portal.thirdweb.com)

  1. Paste THIRDWEB_VAULT_ACCESS_TOKEN into FastMCP (if required)
    In the FastMCP form, set THIRDWEB_VAULT_ACCESS_TOKEN to the vault token you created and save.

  2. Verify and secure your values

  1. Confirm each env var value has been saved in FastMCP and matches the exact string copied from thirdweb.
  2. Store all secret values in a secure secrets manager if possible and do not expose them in client-side code. Note: secret keys and access tokens are sensitive and often shown only once — if lost, revoke and recreate. (portal.thirdweb.com)

  1. Restart / test the MCP server connection
    After filling all required env fields in FastMCP, restart or re-install the MCP (use the Install Now flow) and run a quick test (e.g., call a read-only Engine or Storage endpoint) to verify authentication and connectivity.

  2. If you need programmatic creation (CI/CD)
    For automated setups, create secrets programmatically (Vault SDK or Engine API) and inject them into your CI/CD secrets store, then point FastMCP/env injection at those secrets. See the Vault SDK and Engine docs for examples. (portal.thirdweb.com)

Quick Start

View on GitHub

More for API Development

View All →

More for Developer Tools

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.