Okto MCP Server

🚀 Okto Web3 MCP Server

An MCP (Model Context Protocol) server for Okto Web3 integration, designed for the Claude desktop application with automatic authentication. This server enables AI assistants to manage Web3 transactions and portfolios through natural language interaction.

🚀 Quick Start

The Okto Web3 MCP Server is a powerful tool that allows AI assistants to manage Web3 transactions and portfolios via natural language interaction. It is specifically designed for the Claude desktop application and comes with automatic authentication capabilities.

✨ Features

• View portfolio details, including holdings and balances.
• Retrieve account information across multiple chains.
• List all NFT collections associated with an account.
• Review transaction history.
• View detailed NFT holding information.
• List all available tokens and their details.
• Transfer tokens to a specified address.
• Get a list of all supported blockchain networks.

📦 Installation

1. Prepare OAuth Credentials

• Ensure you have a valid Google OAuth 2.0 credentials file gcp-oauth.keys.json.
• Place it in the current directory or the .okto-mcp folder in your user's home directory.

2. Configure Environment Variables

export OKTO_ENV=development  # or production

3. Authentication Process

• Run the authentication script to obtain an access token.
• The script will automatically handle the credentials file and establish a secure authorized session.

💻 Configuration for Claude Desktop App

Add the following configuration to ~/.config/claude/web3.json:

{
  "mcp-server": {
    "url": "http://localhost:3000",
    "auth": {
      "type": "okto",
      "env": "${OKTO_ENV}"
    }
  }
}

💻 Usage Examples

1. Portfolio Details Query

{
  "examples": ["Query asset status across all chains"]
}

2. Multi-chain Account Information Retrieval

{}

3. NFT Collection Listing

{}

4. Transaction History Review

{}

5. Detailed NFT Portfolio Information

{}

6. Available Token Listing

{}

7. Token Transfer Operation

Specify transfer parameters:

{
  "amount": "1000000000000000000",
  "recipient": "0x...",
  "token": "0x...",
  "caip2Id": "eip155:1"
}

8. Supported Blockchain Network Listing

{}

🛡️ Security Notes

• Securely store OAuth credentials in the local environment (~/.okto-mcp).
• The server uses offline access mode to maintain a persistent authentication state.
• Never share or commit credentials to version control systems.
• Regularly check and revoke unused Google account permissions.
• Securely store Okto credentials via environment variables.
• Credentials are restricted to the current user.

🛠️ Troubleshooting

1. OAuth Key Not Found

• Ensure the gcp-oauth.keys.json file exists in the current directory or ~/.okto-mcp/.
• Verify file permission settings.

2. Invalid Credential Format

• Confirm that the OAuth credentials file contains a valid web or installed type configuration.
• For web applications, verify that the redirect URI is correctly configured.

3. Port Already in Use

• If port 3000 is occupied, release the port before running the authentication process.
• You can use commands to find and terminate the occupying process.

4. Okto Authentication Failure

• Check if the environment variables are correctly configured.
• Confirm that the Okto credentials are valid.
• Ensure you are using the correct environment (testing/production).

📄 License

ISC

📞 Support and Feedback

If you encounter any issues or have questions, please submit an ISSUE in the GitHub repository.