Skip to main content

thirdweb MCP

Project description

thirdweb MCP Server

A Model Context Protocol (MCP) server implementation for thirdweb services integration. This server allows you to integrate thirdweb's tools with any MCP-compatible client.

Overview

thirdweb MCP provides a unified interface to access thirdweb's suite of blockchain tools and services through the standardized Model Context Protocol. It supports multiple communication transports and can be integrated with various thirdweb services:

  • Nebula: Autonomous onchain execution - real-time on-chain analysis, code generation and contract interactions
  • Insight: Blockchain data analysis capabilities for real-time on-chain data
  • Engine: Integration with thirdweb's backend infrastructure for contract deployments and interactions
  • EngineCloud: Cloud-based engine operations for server wallets, contract interactions, and transaction management
  • Storage: Decentralized storage capabilities for uploading and retrieving data via IPFS

Installation

Prerequisites

  • Python 3.10 or higher
  • uv

Run with uvx

THIRDWEB_SECRET_KEY=... \
    uvx thirdweb-mcp

Install and run with pipx

pipx install thirdweb-mcp

THIRDWEB_SECRET_KEY=... \
    thirdweb-mcp

Install from source

git clone https://github.com/thirdweb-dev/ai.git thirdweb-ai
cd thirdweb-ai/python/thirdweb-mcp
uv sync

Configuration

The thirdweb MCP server requires configuration based on which services you want to enable:

  1. thirdweb Secret Key: Required for Nebula, Insight, Storage, and EngineCloud services. Obtain from the thirdweb dashboard.
  2. Chain IDs: Blockchain network IDs to connect to (e.g., 1 for Ethereum mainnet, 137 for Polygon).
  3. Engine Configuration: If using the Engine service, you'll need the Engine URL and authentication JWT.
  4. EngineCloud Configuration: For EngineCloud operations, you may need the Vault Access Token for server wallet operations.

You can provide these through command-line options or environment variables.

Usage

Command-line options

# Basic usage with default settings (stdio transport with Nebula and Insight)
THIRDWEB_SECRET_KEY=... thirdweb-mcp 

# Using SSE transport on a custom port
THIRDWEB_SECRET_KEY=... thirdweb-mcp --transport sse --port 8080

# Enabling all services with specific chain IDs
THIRDWEB_SECRET_KEY=... thirdweb-mcp --chain-id 1 --chain-id 137 \
    --engine-url YOUR_ENGINE_URL \
    --engine-auth-jwt YOUR_ENGINE_JWT \ 
    --engine-backend-wallet-address YOUR_ENGINE_BACKEND_WALLET_ADDRESS \
    --vault-access-token YOUR_VAULT_ACCESS_TOKEN

Environment variables

You can also configure the MCP server using environment variables:

  • THIRDWEB_SECRET_KEY: Your thirdweb API secret key
  • THIRDWEB_ENGINE_URL: URL endpoint for thirdweb Engine service
  • THIRDWEB_ENGINE_AUTH_JWT: Authentication JWT token for Engine
  • THIRDWEB_ENGINE_BACKEND_WALLET_ADDRESS: Wallet address for Engine backend
  • THIRDWEB_ENGINE_CLOUD_URL: URL endpoint for EngineCloud service (defaults to https://engine.thirdweb.com/v1)
  • THIRDWEB_VAULT_ACCESS_TOKEN: Vault access token for EngineCloud server wallet operations

Integration with Claude Desktop

To add this MCP server to Claude Desktop:

  1. Install the MCP: pipx install thirdweb-mcp

  2. Create or edit the Claude Desktop configuration file at:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
    • Linux: ~/.config/Claude/claude_desktop_config.json
  3. Add the following configuration:

    {
      "mcpServers": {
        "thirdweb-mcp": {
          "command": "thirdweb-mcp",
          "args": [], // add `--chain-id` optionally
          "env": {
            "THIRDWEB_SECRET_KEY": "your thirdweb secret key from dashboard",
            "THIRDWEB_ENGINE_URL": "(OPTIONAL) your engine url",
            "THIRDWEB_ENGINE_AUTH_JWT": "(OPTIONAL) your engine auth jwt",
            "THIRDWEB_ENGINE_BACKEND_WALLET_ADDRESS": "(OPTIONAL) your engine backend wallet address",
            "THIRDWEB_VAULT_ACCESS_TOKEN": "(OPTIONAL) your vault access token for EngineCloud"
          },
        }
      }
    }
    
  4. Restart Claude Desktop for the changes to take effect.

Read more on MCP Quickstart

Integration with MCP clients

This server can be integrated with any client that supports the Model Context Protocol:

  1. Run the MCP server with the appropriate configuration
  2. Connect your MCP client to the server using the selected transport (stdio or SSE)
  3. Access thirdweb services through the exposed MCP tools

Available Services

Nebula

Autonomous onchain execution and analysis:

  • Analyze smart contract code
  • Contract interactions and deployments
  • Autonomous onchain tasks execution

Insight

Offers blockchain data analysis capabilities:

  • Query on-chain data across multiple networks
  • Analyze transactions, blocks, and smart contract events
  • Monitor wallet activities and token movements

Engine

Integrates with thirdweb's backend infrastructure:

  • Deploy smart contracts
  • Interact with deployed contracts
  • Manage wallet connections and transactions

EngineCloud

Cloud-based engine operations with advanced capabilities:

  • Create and manage server wallets with KMS integration
  • Read from and write to smart contracts
  • Send transactions and query transaction history
  • Check native token balances on various chains

Storage

Provides decentralized storage functionality:

  • Upload files, directories, and JSON data to IPFS
  • Retrieve content from IPFS using thirdweb gateway
  • Preserve directory structures when uploading

License

Apache-2.0 License

Support

For questions or support, please contact support@thirdweb.com or visit thirdweb.com.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

thirdweb_mcp-0.1.18.tar.gz (9.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

thirdweb_mcp-0.1.18-py3-none-any.whl (9.6 kB view details)

Uploaded Python 3

File details

Details for the file thirdweb_mcp-0.1.18.tar.gz.

File metadata

  • Download URL: thirdweb_mcp-0.1.18.tar.gz
  • Upload date:
  • Size: 9.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for thirdweb_mcp-0.1.18.tar.gz
Algorithm Hash digest
SHA256 62c7dc2656243383402d5707d65d063a70cc70420bcd9dd0870c7de711e643c5
MD5 4a62e04bd97b18df0086dd375544c0d3
BLAKE2b-256 487dfccbbc8f48b299e667cff722570784e183969984a4e9706ceca1cad1249b

See more details on using hashes here.

File details

Details for the file thirdweb_mcp-0.1.18-py3-none-any.whl.

File metadata

  • Download URL: thirdweb_mcp-0.1.18-py3-none-any.whl
  • Upload date:
  • Size: 9.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for thirdweb_mcp-0.1.18-py3-none-any.whl
Algorithm Hash digest
SHA256 646da50774dd4de2998c8f00398b22ab01f7027e55212f6816a99bbcc3b29c7f
MD5 66ab8170186a0ac4ec07360334161bb7
BLAKE2b-256 bbd178f83e7e77eeb63f0fb7d240d6ae5910f6993480fd88143d2bc88473540e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page