Solana Launchpads MCP Server

An MCP server that tracks daily activity and graduate metrics across multiple Solana launchpads. That is what the solana launchpads mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• MCP Tools — Four tools to retrieve daily metrics:
• Token deployments
• Successful graduates (completed projects)
• Graduation rates
• Active wallet addresses
• Markdown Output — Data is formatted as markdown tables for easy readability

The tools it exposes

The server publishes 4 tools. What each one is for:

• get_daily_tokens_deployed — Retrieves daily token deployments by platform, optionally as percentages
• get_daily_graduates — Fetches daily successful graduates by platform
• get_daily_graduation_rate — Retrieves daily graduation rates by platform
• get_daily_active_addresses — Fetches daily active wallet addresses by platform

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: DUNE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10 or higher - uv (recommended package manager) - A Dune Analytics API key

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Solana Launchpads MCP's toolset — get_daily_tokens_deployed, get_daily_graduates, get_daily_graduation_rate and 1 more — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Solana Launchpads MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.