# TokenTool MCP

Token Tool supports integration via the **Model Context Protocol (MCP)**, enabling AI agents to interact directly with tokenization infrastructure.

This allows Token Tool to be used not only through the UI or API, but also as part of **AI-driven workflows and automated systems**.

***

#### What is MCP?

The Model Context Protocol (MCP) is a standardized interface that allows AI agents to securely connect to external tools and execute actions.

Instead of building custom integrations, MCP provides a consistent way to:

* Discover available functions
* Execute structured actions
* Exchange inputs and outputs

With MCP, Token Tool becomes accessible to any MCP-compatible agent or environment.

***

#### Supported Capabilities

Through MCP, Token Tool exposes its core functionality, including:

* Create tokens (ERC-20, SPL Token-2022)
* Manage token lifecycle (mint, burn, pause, transfer ownership)
* Create and distribute NFTs
* Configure token sales
* Interact with deployed contracts

All actions map directly to Token Tool’s underlying API and result in **on-chain transactions**.

***

#### How It Works

```
User / Application
        ↓
AI Agent (MCP Client)
        ↓
Token Tool MCP Server
        ↓
Token Tool API
        ↓
Smart Contracts (Blockchain)
```

* **MCP Client (Agent)** initiates actions
* **MCP Server (Token Tool)** exposes available capabilities
* **Token Tool API** executes the request
* **Blockchain** finalizes the transaction

***

#### Example Use Cases

* **Automated token launches**\
  Trigger token creation based on predefined conditions
* **AI-driven token operations**\
  Manage supply, distributions, or permissions programmatically
* **Conversational interfaces**\
  Create and manage tokens through chat-based systems
* **Workflow automation**\
  Combine token issuance with off-chain systems (e.g. KYC, analytics, notifications)

***

#### Getting Started

1. Set up the MCP server\
   <https://github.com/bitbond/token-tool-mcp>
2. Connect an MCP-compatible agent or environment
3. Configure wallet or custody for transaction signing
4. Execute Token Tool actions via MCP

***

#### Key Considerations

* **Non-custodial**\
  Token Tool does not manage private keys. Transactions must be signed via your wallet or custody provider
* **Execution layer**\
  Token Tool handles token issuance and contract interaction. External systems are responsible for compliance, distribution, and business logic
* **On-chain finality**\
  All actions executed via MCP result in verifiable blockchain transactions

***

#### MCP vs API vs UI

| Approach | Best For                              |
| -------- | ------------------------------------- |
| UI       | No-code token creation and management |
| API      | Direct backend integration            |
| MCP      | AI agents and automated workflows     |

***

#### Summary

The MCP integration extends Token Tool into AI-native environments:

* Standardized agent access
* Programmatic token operations
* Seamless integration into automated systems

Token Tool remains the **issuance and execution layer**, now accessible through AI-driven interfaces.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bitbond.com/asset-tokenization-suite/token-tool/tokentool-mcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.