MCP Jupiter

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Jupiter?

MCP Jupiter is a Model Context Protocol (MCP) server that provides Claude with access to Jupiter's swap API, enabling operations like getting quotes and executing swap transactions on the Solana blockchain.

how to use MCP Jupiter?

To use MCP Jupiter, clone the repository, install dependencies, and configure Claude Desktop to access the MCP server. You can then interact with the server to perform token swaps.

key features of MCP Jupiter?

  • Get quotes for swapping tokens on Jupiter
  • Build and send swap transactions on the Solana blockchain
  • Easy integration with Claude Desktop application

use cases of MCP Jupiter?

  1. Swapping tokens on the Solana blockchain
  2. Automating token transactions through Claude
  3. Accessing real-time swap quotes for trading decisions

FAQ from MCP Jupiter?

  • What is the purpose of MCP Jupiter?

MCP Jupiter allows users to interact with the Jupiter swap API for token transactions.

  • Is there a cost to use MCP Jupiter?

No, MCP Jupiter is free to use as it is an open-source project.

  • What are the prerequisites for using MCP Jupiter?

You need Node.js (v16 or higher) and the Claude Desktop application.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago