solana-nft-mcp

The NFT APIs I tried return an empty ownership history for a Metaplex Core asset, and an AI reading that empty answer tells you the card has never traded. solana-nft-mcp reads the chain itself: who owned it, who can freeze it, what sold and for how much, and where the deals are. Read-only, no sign-up, nothing collected, runs on your machine.

Why

Ask an assistant about a Solana card today and it answers from memory. It will say a card "never traded", because the mainstream NFT APIs return an empty history for Metaplex Core assets while the transfers sit on chain the whole time. It will compare two floors quoted in two currencies as if they were one.

solana-nft-mcp hands the same assistant live, labelled data instead: the chain for supply, ownership, provenance and custody rules, Magic Eden without a key, and OpenSea through a free key the server issues itself. Each number comes back with its marketplace, its currency, its read time, and what the source could not see.

The server runs on your machine and your AI app starts it. There is no hosted service and no account between you and the data. The picture is generated from the running server, so the counts cannot drift from the code: npm test fails if they do.

Install

Node 22 or newer. Two ways to run it.

From npm, no clone. Wherever a client asks for a command, give it npx with the arguments -y solana-nft-mcp. The first start downloads the package; later starts reuse it.

claude mcp add solana-nft -- npx -y solana-nft-mcp

From source. Build once, then point the client at dist/index.js:

git clone https://github.com/p1xelapp/solana-nft-mcp.git
cd solana-nft-mcp && npm install && npm run build

Claude Code

claude mcp add solana-nft -- node /absolute/path/to/solana-nft-mcp/dist/index.js

Claude Desktop. Settings -> Developer -> Edit Config, add the block below, then quit the app fully and reopen it. Or install the .mcpb bundle from the latest release by dragging it onto Settings -> Extensions.

{
  "mcpServers": {
    "solana-nft": {
      "command": "node",
      "args": ["/absolute/path/to/solana-nft-mcp/dist/index.js"]
    }
  }
}

Other clients. Tested: Claude Desktop, Claude Code, Codex CLI 0.153.4 (codex exec -c 'mcp_servers.solana-nft.command="node"' -c 'mcp_servers.solana-nft.args=["/absolute/path/to/dist/index.js"]'). Cursor, Windsurf, Gemini CLI, Zed, Cline and VS Code take the same command / args pair in their own config; the server is plain stdio with no client-specific code, but those have not been tested here. ChatGPT on the web and Grok cannot run a local process. The server speaks MCP protocol revision 2025-11-25 through the official TypeScript SDK v1. A client that offers the newer 2026-07-28 revision gets 2025-11-25 back, which current clients accept; one that refuses anything older cannot use this server yet.

Did it work? Your app lists the tools near the message box (Claude Code: /mcp). You should see 21, starting with identify. If none: the path must be absolute and end in dist/index.js, npm run build must have run, and the app must be fully quit and reopened.

OpenSea is on without any setup. The first questi

... View full README on GitHub