# Integration Guide
Learn how to integrate Hyperion MCP Server with various AI assistants and development tools.
## Overview
The Hyperion MCP Server can be integrated with:
- **Claude Desktop** - Anthropic's desktop AI assistant
- **Cline** - VS Code extension for AI-powered coding
- **Smithery** - MCP server deployment platform
- **Custom MCP Clients** - Any MCP-compatible application
## Claude Desktop Integration
### Prerequisites
- Claude Desktop app installed ([Download here](https://claude.ai/download))
- Hyperion MCP Server built and ready
### Configuration Steps
1. **Locate Configuration File**
**macOS:**
```
~/Library/Application Support/Claude/claude_desktop_config.json
```
**Windows:**
```
%APPDATA%\Claude\claude_desktop_config.json
```
**Linux:**
```
~/.config/Claude/claude_desktop_config.json
```
2. **Add MCP Server Configuration**
Edit the configuration file and add:
```json
{
"mcpServers": {
"hyperion": {
"command": "node",
"args": ["/absolute/path/to/hyperion-mcp-server/build/index.js"]
}
}
}
```
**Replace** `/absolute/path/to/hyperion-mcp-server` with your actual path.
3. **Restart Claude Desktop**
- Quit Claude Desktop completely
- Relaunch the application
- The Hyperion MCP tools should now be available
### Verification
Test the integration by asking Claude:
```
List all available Hyperion wallets
```
If configured correctly, Claude will use the `list_wallets` tool.
### Example Prompts for Claude
```
Create a new Hyperion wallet named "my-wallet"
Check my tMETIS balance
Send 0.5 tMETIS to 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb
Deploy an ERC20 token named "MyToken" with symbol "MTK" and supply 1000000
```
## Cline (VS Code) Integration
### Prerequisites
- VS Code installed
- Cline extension installed ([Install from marketplace](https://marketplace.visualstudio.com/items?itemName=saoudrizwan.claude-dev))
- Hyperion MCP Server built
### Configuration Steps
1. **Open Cline Settings**
- Open VS Code
- Click on Cline icon in sidebar
- Click settings gear icon
- Navigate to "MCP Servers" section
2. **Add Server Configuration**
Click "Edit Config" and add:
```json
{
"mcpServers": {
"hyperion": {
"command": "node",
"args": ["./build/index.js"],
"cwd": "/absolute/path/to/hyperion-mcp-server"
}
}
}
```
3. **Reload VS Code**
- Reload the VS Code window
- Cline should now have access to Hyperion tools
### Verification
In Cline chat, try:
```
Show me the current Hyperion network information
```
### Example Workflows with Cline
**Workflow 1: Token Deployment**
```
1. Create a new wallet for testing
2. Deploy an ERC20 token with these specs:
- Name: TestToken
- Symbol: TEST
- Supply: 1000000
- Mintable: true
3. Show me the contract address
```
**Workflow 2: Transaction Automation**
```
Check my balance, then send 0.1 tMETIS to 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb if I have enough
```
## Smithery Integration
### Prerequisites
- Smithery account ([Sign up at smithery.ai](https://smithery.ai))
- Hyperion MCP Server repository
### Deployment Steps
1. **Install Smithery CLI**
```bash
npm install -g @smithery/cli
```
2. **Login to Smithery**
```bash
npx @smithery/cli login
```
3. **Deploy Server**
```bash
cd hyperion-mcp-server
npx @smithery/cli deploy
```
4. **Configure in Smithery Dashboard**
- Go to [smithery.ai/dashboard](https://smithery.ai/dashboard)
- Find "Hyperion MCP Server"
- Click "Configure"
- Add your wallet private key in the secure config
5. **Use in Smithery Apps**
The server is now available to any Smithery-connected AI assistant.
### Smithery Environment Variables
Configure these in the Smithery dashboard:
```
HYPERION_PRIVATE_KEY=your_private_key_here
HYPERION_RPC_URL=https://rpc.hyperion-testnet.metisdevops.link
```
## Custom MCP Client Integration
### Using the MCP SDK
For custom integrations, use the MCP SDK:
```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
// Create transport
const transport = new StdioClientTransport({
command: "node",
args: ["/path/to/hyperion-mcp-server/build/index.js"],
});
// Create client
const client = new Client({
name: "my-app",
version: "1.0.0",
}, {
capabilities: {},
});
// Connect
await client.connect(transport);
// List available tools
const tools = await client.listTools();
console.log("Available tools:", tools);
// Call a tool
const result = await client.callTool({
name: "get_network_info",
arguments: {},
});
console.log("Network info:", result);
```
### HTTP Transport (Advanced)
For web applications, use HTTP transport:
```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";
const transport = new SSEClientTransport(
new URL("http://localhost:3000/mcp")
);
const client = new Client({
name: "web-app",
version: "1.0.0",
}, {
capabilities: {},
});
await client.connect(transport);
```
## Environment Variables
Configure these environment variables for all integrations:
```bash
# Network Configuration
HYPERION_RPC_URL=https://rpc.hyperion-testnet.metisdevops.link
HYPERION_CHAIN_ID=133717
HYPERION_EXPLORER_URL=https://hyperion-testnet.metisdevops.link
# Optional: Default Wallet
DEFAULT_WALLET_NAME=my-wallet
# Optional: Gas Settings
DEFAULT_GAS_LIMIT=300000
DEFAULT_GAS_PRICE=1.5
```
## Troubleshooting Integration Issues
### Server Not Found
**Problem:** MCP client can't find the server
**Solutions:**
- Verify the path to `build/index.js` is absolute
- Ensure the server is built: `npm run build`
- Check file permissions
### Tools Not Available
**Problem:** Tools don't appear in the client
**Solutions:**
- Restart the MCP client application
- Check server logs for errors
- Verify MCP SDK version compatibility
### Connection Errors
**Problem:** Client can't connect to server
**Solutions:**
- Ensure Node.js is in PATH
- Check for port conflicts (if using HTTP)
- Verify network connectivity for RPC
### Permission Errors
**Problem:** Can't execute server script
**Solutions:**
- Check file permissions: `chmod +x build/index.js`
- Verify Node.js installation
- Run with appropriate user permissions
## Best Practices
1. **Use Absolute Paths**
- Always use absolute paths in configuration files
- Avoid relative paths that may break
2. **Secure Credentials**
- Never hardcode private keys in config files
- Use environment variables for sensitive data
- Consider using secret management tools
3. **Monitor Logs**
- Check server logs for errors
- Enable debug mode for troubleshooting
- Keep logs for audit trails
4. **Version Control**
- Keep MCP server updated
- Document configuration changes
- Test integrations after updates
---
**Next**: See [Examples](./examples.md) for real-world usage →
