Okto Web3

Provides Okto Web3 integration across portfolios, accounts, NFTs, and token transfers with auto authentication.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "okto-hq-okto-mcp-server": {
      "command": "npx",
      "args": [
        "@okto_web3/okto-mcp-server@latest",
        "auth"
      ],
      "env": {
        "OKTO_CLIENT_SWA": "your_swa_here",
        "OKTO_ENVIRONMENT": "sandbox",
        "OKTO_CLIENT_PRIVATE_KEY": "your_private_key_here"
      }
    }
  }
}

You can use the Okto Web3 MCP Server to manage Web3 portfolios, accounts, NFTs, and transfers through natural language interactions. It provides secure, auto-authenticated access so your AI assistants can perform actions across multiple blockchains with ease.

How to use

Connect your MCP client to the Okto Web3 MCP Server to access portfolio data, account details across chains, NFT collections, transaction history, and token transfers. You’ll authenticate once, then you can run commands or ask your assistant to view balances, check prices, transfer tokens, or browse your NFT holdings. The server supports both Desktop and Web application credentials and stores credentials securely on your machine for repeated use.

Typical usage patterns include authenticating from any location, then invoking actions via your MCP client: view portfolios, inspect NFT portfolios, list supported chains, check token balances, review transaction history, and perform token transfers. Authentication is designed to launch in your browser and save credentials locally so you don’t need to re-authenticate for every request.

How to install

Prerequisites: you need Node.js and npm installed on your system. Verify installations with these commands.

node -v
npm -v

Install and run the MCP server via the recommended authentication flow. You will authenticate once and store credentials for future use.

Global authentication (recommended) and then run authentication from anywhere.

# First time: place gcp-oauth.keys.json in your home directory's .okto-mcp folder
mkdir -p ~/.okto-mcp
mv gcp-oauth.keys.json ~/.okto-mcp/

# Run authentication from anywhere
npx @okto_web3/okto-mcp-server@latest auth

Local authentication (place keys in the current directory). The file will be copied to the global config during authentication.

# Place gcp-oauth.keys.json in your current directory
# Run authentication to use global config
npx @okto_web3/okto-mcp-server@latest auth

Configuration and security

Configure credentials and environment variables to enable secure access and proper routing to your Okto environment. The server stores credentials locally and uses offline access for persistent authentication.

Environment variables shown in examples control the Okto environment, client private key, and client SWA. Keep these values private and do not commit them to version control.

Troubleshooting

If you encounter issues when authenticating, verify that your gcp-oauth.keys.json file is located in the expected place and that permissions allow read access.

If an invalid credentials format is detected, ensure the OAuth keys include the correct web or installed credentials and that the redirect URI is configured for web-based authentication.

If port conflicts occur during authentication, free port 3000 or use another available port for your local setup.

If Okto authentication fails, confirm that environment variables are set correctly and that the provided Okto credentials are valid for the sandbox or production environment.

Notes

You can use either desktop or web application credentials. Credential storage is global but scoped to your user account, so other users on the same machine won’t access your credentials.

Security and credentials overview

OAuth credentials are stored securely in your local environment at ~/.okto-mcp. The server uses offline access to maintain persistent authentication, and credentials should never be shared or committed to version control.

Available tools

Get Portfolio

Retrieves detailed portfolio information including holdings and balances.

Get Account

Retrieves account details across multiple chains.

Get NFT Collections

Lists all NFT collections associated with the account.

Get Orders History

Retrieves transaction history.

Get NFT Portfolio

Shows detailed NFT holdings information.

Get Tokens

Lists all available tokens and their details.

Token Transfer

Transfers tokens between addresses.

Get Chains

Lists all supported blockchain networks.