linea-mcp
If you are the rightful owner of linea-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
A Model Context Protocol (MCP) server that provides on-chain tools for AI applications to interact with the Linea blockchain.
Linea MCP Server
A Model Context Protocol (MCP) server that provides on-chain tools for AI applications to interact with the Linea blockchain.
Overview
Linea-MCP extends any MCP client's capabilities by providing tools to interact with the Linea blockchain, an Ethereum Layer 2 scaling solution using zero-knowledge proof technology. This server enables AI assistants like Claude, Cursor, and other MCP-compatible clients to perform blockchain operations through natural language requests.
Key Features
- Wallet Management: Retrieve addresses and check balances
- Token Operations: Transfer ERC20 tokens, check balances, list tokens
- Smart Contract Interactions: Deploy and call contracts
- NFT Management: List and transfer NFTs
- Bridge Operations: Bridge assets between Ethereum and Linea
- DeFi Integrations: Interact with DeFi protocols
- Verax Integration: Verify identity with Linea Verax attestations
- Linea ENS: Resolve and manage Linea ENS names
for detailed usage examples.
Quick Start
Prerequisites
- Node.js (v16+)
- npm or yarn
- Access to Linea RPC endpoints
Installation Options
Option 1: Quick Install (Global Package)
# Install globally
npm install -g linea-mcp
# Create a basic .env file
echo "LINEA_MAINNET_RPC_URL=https://rpc.linea.build
LINEA_TESTNET_RPC_URL=https://rpc.sepolia.linea.build
WALLET_PRIVATE_KEY=your_wallet_private_key_here
INFURA_API_KEY=your_infura_key_here" > .env
# Start the server
linea-mcp
Option 2: Development Install (From Source)
# Clone the repository
git clone https://github.com/qvkare/linea-mcp.git
cd linea-mcp
# Install dependencies
npm install
# Configure environment
cp .env.example .env
# Edit .env with your configuration
# Build and start
npm run build
node dist/index.js # Using Node directly is more reliable than npm start
Integration with MCP Clients
This MCP server can be integrated with any MCP-compatible client including Cursor, Claude Desktop, Windsurf, Cline, and other AI assistants.
General Configuration Steps
- Find your client's MCP configuration file location
- Add a Linea MCP server configuration section
- Configure the server using one of the following approaches:
Option 1: Using Global Installation (Simple)
{
"mcpServers": {
"linea": {
"command": "npx",
"args": ["linea-mcp@latest"],
"env": {
"PORT": "3000",
"LINEA_MAINNET_RPC_URL": "https://rpc.linea.build",
"LINEA_TESTNET_RPC_URL": "https://rpc.sepolia.linea.build",
"INFURA_API_KEY": "your_infura_key",
"ALCHEMY_API_KEY": "your_alchemy_key",
"PRIVATE_KEY_ENCRYPTION_KEY": "your_encryption_key_please_change",
"WALLET_PRIVATE_KEY": "your_wallet_private_key_or_mnemonic",
"NODE_ENV": "development",
"ETHEREUM_RPC_URL": "https://mainnet.infura.io/v3/your_infura_key",
"ETHEREUM_TESTNET_RPC_URL": "https://sepolia.infura.io/v3/your_infura_key"
}
}
}
}
Option 2: Using Local Installation (Recommended for Development)
{
"mcpServers": {
"linea": {
"command": "node",
"args": ["/absolute/path/to/linea-mcp/dist/index.js"],
"cwd": "/absolute/path/to/linea-mcp",
"env": {
// Same environment variables as Option 1
"PORT": "3000",
"LINEA_MAINNET_RPC_URL": "https://rpc.linea.build",
// ... other variables from Option 1
}
}
}
}
Important Note: When using a local installation, directly running the JavaScript file with Node.js provides more reliable communication than using npm scripts.
Client-Specific Locations
-
Cursor:
- Windows:
%APPDATA%\Cursor\mcp.json - macOS:
~/Library/Application Support/Cursor/mcp.json - Linux:
~/.config/Cursor/mcp.json
- Windows:
-
Claude Desktop:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- Windows:
-
Other Clients: Refer to your client's documentation for MCP configuration location
Troubleshooting
Common Issues
-
"No tools available" or "Client closed" errors:
- Use direct Node.js execution (
"command": "node", "args": ["/path/to/dist/index.js"]) instead of npm scripts - Ensure environment variables are configured correctly
- Restart your client after configuration changes
- Use direct Node.js execution (
-
JSON parsing errors in logs:
- These indicate communication protocol issues
- Using direct Node.js execution usually resolves these problems
- Make sure the
cwdproperty is set correctly
-
Complete troubleshooting guide:
- See for detailed solutions to common problems
Available Tools
The server provides tools across multiple categories:
- Wallet: Address management, balance checking, fund transfers
- Tokens: ERC20 transfers, balance checking, token information
- Contracts: Deployment and interaction
- NFTs: Listing and transfers
- Bridge: Asset bridging between Ethereum and Linea
- DeFi: Liquidity pools, token swaps, yield farming
- ENS: Name resolution and record management
- Verax: Identity verification
For a complete list of tools and their usage, see .
Security Considerations
- Never share your private keys or seed phrases
- Use environment variables for sensitive configuration
- Test extensively with testnet before using on mainnet
License
This project is licensed under the MIT License - see the LICENSE file for details.
