mcpField
E
Edwin

Edwin

Local
docs.edwin.financeFinance66Updated 50w ago

About Edwin

Edwin MCP Server is an example implementation of an MCP server for the Edwin SDK. It lets AI agents call Edwin's tools through a standard protocol. It targets DeFi use cases that involve EVM and Solana wallets.

Key features

  1. 01Exposes all tools configured in an Edwin instance
  2. 02Supports EVM and Solana wallets
  3. 03Configured through a .env file
  4. 04Connects to Claude Desktop

Use cases

  1. 01Letting an AI agent check wallet balances
  2. 02Letting an AI agent run token transfers or contract calls

MCP support

The project is an MCP server that exposes the tools configured in the Edwin SDK to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Edwin MCP Server

This is an example implementation of a Model Context Protocol (MCP) server for the Edwin SDK. It allows AI agents to interact with Edwin's tools through a standardized protocol.

Prerequisites

  • Node.js >= 18.0.0
  • pnpm (recommended) or npm
  • A local Claude instance or access to Claude API
  • EVM and/or Solana wallet private keys (depending on your needs)

Installation

  1. Clone the repository and navigate to the mcp-server directory:
cd examples/mcp-server
  1. Install dependencies:
pnpm install
  1. Build the project:
pnpm build

Running the Server

Option 1: Local Development
  1. Create your environment file:
cp .env.example .env
  1. Configure your .env file with the following required settings:

    • SOLANA_RPC_URL: Your RPC endpoint
    • EVM_PRIVATE_KEY: Your EVM wallet private key
    • SOLANA_PRIVATE_KEY: Your Solana wallet private key
    • EDWIN_MCP_MODE=true: Enable MCP mode
  2. Start the server:

    • For production: pnpm start
    • For development with hot reloading: pnpm dev
Option 2: Using with Claude Desktop
  1. After building the project, use the provided claude_desktop_config.json to configure your Claude Desktop:

    • Open Claude Desktop
    • Go to Settings
    • Import the configuration from claude_desktop_config.json
  2. The server will automatically start when needed by Claude Desktop.

Available Tools

The server exposes all tools configured in your Edwin instance. Common tools include:

  • Wallet operations
  • Balance checking
  • Transaction signing
  • Token transfers
  • Contract interactions

Security Considerations

  1. Never commit your .env file with private keys
  2. Use appropriate CORS settings in production
  3. Implement rate limiting for production use
  4. Keep your private keys secure and never share them

Troubleshooting

  1. Server won't start:

    • Check if the port is already in use
    • Verify your environment variables are set correctly
    • Check the logs for specific error messages
  2. Tools not available:

    • Ensure your Edwin instance is properly configured
    • Check if the tools are properly registered
    • Verify your wallet keys are correct
  3. Connection issues:

    • Check if the server is running
    • Verify the port is correct
    • Check network connectivity

Contributing

Feel free to submit issues and enhancement requests!

License

This project is licensed under the same terms as the main Edwin SDK.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.