Edwin

Created By
examplesa year ago
Overview

what is Edwin?

Edwin is a TypeScript library that acts as a bridge between AI agents and DeFi protocols, providing a secure and unified interface for interaction while simplifying blockchain operations.

how to use Edwin?

To use Edwin, install the SDK with pnpm install edwin-sdk, configure your wallet and services, and then interact with DeFi protocols using the provided methods.

key features of Edwin?

  • Supports lending and borrowing operations
  • Liquidity provision capabilities
  • Cross-chain support for various protocols
  • Type-safe interactions with DeFi protocols
  • AI-friendly templates for easy integration

use cases of Edwin?

  1. Creating AI agents that can lend and borrow assets in DeFi.
  2. Providing liquidity to decentralized exchanges.
  3. Developing cross-chain DeFi applications.

FAQ from Edwin?

  • What programming language is Edwin built with?

Edwin is built with TypeScript, making it type-safe and easy to integrate with other TypeScript projects.

  • Is there documentation available?

Yes! Detailed documentation can be found at docs.edwin.finance.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find the guidelines in the Contributing Guide.

Server Config

{
  "mcpServers": {
    "edwin": {
      "command": "node",
      "env": {
        "SOLANA_RPC_URL": "<YOUR_SOLANA_RPC_URL",
        "EVM_PRIVATE_KEY": "<YOUR_EVM_AGENT_PRIVATE_KEY",
        "SOLANA_PRIVATE_KEY": "<YOUR_SOLANA_AGENT_PRIVATE_KEY",
        "EDWIN_MCP_MODE": "true",
        "EDWIN_FILE_LOGGING": "true"
      },
      "args": [
        "<EDWIN_PARENT_PATH>/edwin/examples/mcp-server/dist/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
examples
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago