Agentipy Mcp Server

Created By
niceberginca year ago
The Agentipy MCP Server is an open-source Model Context Protocol (MCP) server that enables Claude AI to interact with the Solana blockchain. It provides a standardized interface for AI agents to perform various blockchain operations, including transactions, wallet management, and data queries.
Overview

what is Agentipy MCP Server?

Agentipy MCP Server is a Model Context Protocol (MCP) server designed to provide on-chain tools for Claude AI, enabling it to interact with the Solana blockchain through a standardized interface.

how to use Agentipy MCP Server?

To use the Agentipy MCP Server, clone the repository from GitHub, set up a virtual environment, install the required dependencies, and configure your environment variables with your Solana wallet and API keys. Then, integrate it with Claude Desktop by modifying the configuration file and restarting the application.

key features of Agentipy MCP Server?

  • Interact with the Solana blockchain
  • Execute transactions and manage wallets
  • Get price predictions and trade tokens
  • Deploy new tokens and access real-time price data
  • Monitor trending tokens and market movements

use cases of Agentipy MCP Server?

  1. Facilitating AI agents to perform blockchain operations seamlessly.
  2. Enabling automated trading and staking of tokens.
  3. Providing real-time analytics and price predictions for cryptocurrencies.

FAQ from Agentipy MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a specification that standardizes interactions between AI agents and blockchain networks.

  • Is there a cost to use the Agentipy MCP Server?

The server is open-source and free to use, but you may incur costs related to blockchain transactions.

  • What are the prerequisites for using the server?

You need Python 3.8 or higher, a Solana wallet, and optional API keys for additional features.

Server Config

{
  "mcpServers": {
    "agentipy": {
      "command": "/path/to/your/run_mcp.sh",
      "env": {
        "RPC_URL": "your_solana_rpc_url_here",
        "SOLANA_PRIVATE_KEY": "your_private_key_here",
        "OPENAI_API_KEY": "your_openai_api_key",
        "ALLORA_API_KEY": "your_allora_api_key",
        "COINGECKO_PRO_API_KEY": "your_coingecko_api_key"
      },
      "disabled": false,
      "autoApprove": [
        "GET_BALANCE",
        "GET_PRICE_PREDICTION"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
niceberginc
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago