4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
ThirdWeb MCP Server

Bring Web3
to Claude Desktop

Learn how to connect ThirdWeb to Claude Desktop and start using 29 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Broadcast Solana TransactionComplete AuthCreate Solana WalletDeploy ContractExecute Solana SwapFetch With PaymentGet Payment RequirementsGet Solana BalanceGet Solana Swap QuoteGet Transaction StatusGet User DetailsGet Wallet MeInitiate AuthLink ProfileList Solana WalletsList TransactionsPregenerate WalletQuery EventsQuery TransactionsRead ContractSend Raw TransactionsSend Solana TokensSettle PaymentSign Solana MessageSign Solana TransactionSocial AuthUnlink ProfileVerify PaymentWrite Contract

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
ThirdWeb

What is the ThirdWeb MCP Server?

Connect your ThirdWeb account to any AI agent to build and manage Web3 applications through natural language. This server provides a comprehensive suite of tools for blockchain interaction and identity management.

What you can do

  • Authentication & Identity — Handle email, SMS, social, and passkey logins. Link multiple social profiles to a single wallet address using initiate_auth and link_profile.
  • Wallet Management — Retrieve authenticated user details, search for users by address or email, and pre-generate wallets for new users via get_user_details and pregenerate_wallet.
  • Smart Contract Interaction — Execute read-only multicalls or state-changing transactions across any supported chain using read_contract and write_contract.
  • Event Monitoring — Query historical contract events with advanced filtering for data analysis using query_events.

How it works

  1. Subscribe to this server
  2. Provide your ThirdWeb Secret Key and API URL
  3. Start building Web3 workflows from your favorite MCP client

Who is this for?

  • Web3 Developers — Rapidly prototype contract interactions and test auth flows directly from the IDE.
  • DApp Operators — Manage user profiles and monitor contract events without custom scripts.
  • Product Managers — Query on-chain data and user details to understand platform activity.

Built-in capabilities (29)

broadcast_solana_transaction

Broadcast a transaction on Solana

complete_auth

Verify challenge and complete login

create_solana_wallet

Create a Solana wallet

deploy_contract

Deploy a contract using bytecode and ABI

execute_solana_swap

Execute a token swap on Solana Mainnet

fetch_with_payment

Proxy a request to a paid API using x402

get_payment_requirements

Generate payment requirements for a resource (x402)

get_solana_balance

Get Solana wallet balance

get_solana_swap_quote

Get a token swap quote on Solana Mainnet

get_transaction_status

Get status of a transaction

get_user_details

Search for users in your project

get_wallet_me

Retrieve details of the authenticated user

initiate_auth

Start authentication process for email, phone, passkey, or SIWE

link_profile

Tie multiple social identities to a single wallet address

list_solana_wallets

List Solana wallets

list_transactions

List transactions

pregenerate_wallet

Create a wallet for a user before they first log in

query_events

Fetch historical events for a contract

query_transactions

Fetch transaction history for a contract

read_contract

Execute one or more read-only calls (multicall)

send_raw_transactions

Broadcast encoded transactions

send_solana_tokens

Send Solana tokens

settle_payment

Submit the payment on-chain (x402)

sign_solana_message

Sign a message on Solana

sign_solana_transaction

Sign a transaction on Solana

social_auth

OAuth flow for social providers

unlink_profile

Unlink a social identity from a wallet address

verify_payment

Validate a signed payment payload (x402)

write_contract

Execute one or more state-changing calls atomically

Why Claude Desktop?

Claude Desktop is the definitive way to connect ThirdWeb to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 29 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

ThirdWeb in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

ThirdWeb and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect ThirdWeb to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for ThirdWeb in Claude Desktop

The ThirdWeb MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 29 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

ThirdWeb
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures ThirdWeb for Claude Desktop

Every tool call from Claude Desktop to the ThirdWeb MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I read data from a smart contract without paying gas?

Yes! Use the read_contract tool. It performs read-only calls (multicall) to the blockchain, which do not require gas or state changes.

02

How do I start an authentication flow for a new user?

You can use the initiate_auth tool by specifying the method (email, sms, etc.) and the user's identifier. Then, use complete_auth with the verification code to finish the login.

03

Can I find a user's profile if I only have their wallet address?

Absolutely. Use the get_user_details tool and provide the address parameter. The agent will return any associated user IDs, emails, or phone numbers linked to that wallet in your project.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →