XRPL MCP Server

Created By
lgcarriera year ago
XRP Ledger MCP Server
Overview

What is XRPL MCP Server?

XRPL MCP Server is a Model Context Protocol (MCP) server that provides AI models with access to XRP Ledger data and functionality, acting as a bridge between large language models (LLMs) and the XRP Ledger.

How to use XRPL MCP Server?

To use the XRPL MCP Server, you can either clone the repository and run it from source or install it using pip. After installation, you can integrate it with MCP-compatible AI applications like Claude to access XRP Ledger data.

Key features of XRPL MCP Server?

  • Retrieve account information (balance, sequence number)
  • Query trust lines and issued currencies
  • View NFTs owned by accounts
  • Access transaction history and order book data
  • Submit signed transactions to the network
  • Get server status information
  • Easy integration with AI applications through a standardized API

Use cases of XRPL MCP Server?

  1. Accessing real-time account information for XRP Ledger accounts.
  2. Integrating with AI assistants to provide users with instant access to their XRP Ledger data.
  3. Facilitating transactions and NFT management through AI-driven applications.

FAQ from XRPL MCP Server?

  • Can I use XRPL MCP Server with any AI model?

Yes! It is designed to work with any MCP-compatible AI model, such as Claude or GPT.

  • Is there a cost to use XRPL MCP Server?

No, XRPL MCP Server is open-source and free to use.

  • What programming language is XRPL MCP Server written in?

XRPL MCP Server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lgcarrier
Star
1
Language
Python
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)

9 hours ago