Bring Nft Minting
to CrewAI
Learn how to connect Toket to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Toket MCP Server?
Connect your Toket account to any AI agent and simplify how you deploy NFT collections, mint digital assets, and monitor blockchain interactions through natural conversation.
What you can do
- Collection Management — List all your NFT collections and deploy new ERC-721 smart contracts instantly via AI.
- Asset Minting — Mint NFTs into specific collections or use 'Easy Mint' to quickly generate assets for recipients.
- Transaction Oversight — List and check the status of minting transactions to ensure successful blockchain delivery.
- Gas Management — Monitor your Gas Tank balance to keep your automated minting operations running smoothly.
- Metadata Control — Retrieve detailed metadata for collections and individual minted assets.
- Blockchain Visibility — Track the history of your digital asset distribution directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Toket API Key (found in your account dashboard)
3. Start managing your Web3 ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Web3 Marketers — quickly mint rewards or loyalty NFTs for community members via simple AI commands.
- NFT Project Owners — monitor collection deployments and verify minting statuses across multiple chains.
- Developers — automate the creation of smart contracts and asset distribution directly from the workspace.
Built-in capabilities (8)
Provide name, symbol, and owner wallet. Create a new NFT collection
Quickly mint an NFT
Get details of a specific collection
Check Gas Tank balance
Get status of a minting transaction
List all NFT collections
List all minted NFTs
Mint an NFT into a collection
Why CrewAI?
When paired with CrewAI, Toket becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Toket tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Toket in CrewAI
Toket and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Toket to CrewAI 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Toket in CrewAI
The Toket 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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.
* 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
How Vinkius secures
Toket for CrewAI
Every tool call from CrewAI to the Toket MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I deploy a new NFT collection using the AI?
Yes! Use the create_collection action. Provide a name, symbol, and the owner wallet address. Your agent will deploy a new ERC-721 smart contract instantly.
How do I check my remaining balance for transaction fees (Gas)?
Run the get_gas_tank_status query. The agent will retrieve your current Gas Tank balance to ensure you have enough funds for automated minting.
Is it possible to track the status of an NFT minting process?
Absolutely. Use the get_mint_status tool and provide the Transaction ID. Your agent will return the real-time status of the blockchain interaction.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.