MCP Hub
Back to servers

Solana MCP by Vybe

Solana MCP by Vybe: OpenAPI discovery, doc search, live API execution with your Vybe API key.

Registry
Updated
Apr 9, 2026

solana-mcp-vybe

Public Model Context Protocol (MCP) registry metadata for Solana MCP by Vybe (hosted on ReadMe).

The live MCP endpoint is:

https://docs.vybenetwork.com/mcp

This repository holds:

  • server.json — metadata published to the official MCP Registry (GitHub Actions).
  • .mcp.json and mcp.jsonOpen Plugins–style MCP config at the repo root so directory UIs (e.g. Cursor “Submit a Plugin” with Auto GitHub scan) can detect a plugin component. They use npx mcp-remote and the public MCP URL only — no API key in the repo. Add a X-API-KEY header (or env) in your client when you need tools that call the Vybe API (e.g. execute-request); keys come from vybe.fyi.

examples/cursor-mcp.json is the same idea for native url config: URL only, optional headers in the client when needed.

GitHub repository name

vybenetwork/solana-mcp-vybe (starts with solana-mcp, includes Vybe).

Publish a new listing version

  1. Clone or use this repo at github.com/vybenetwork/solana-mcp-vybe.

  2. Tag and push (the workflow sets server.json version from the tag):

    git tag v1.0.0
    git push origin v1.0.0
    

    Or run Actions → Publish to MCP Registry → Run workflow (uses the version already in server.json).

Publishing uses GitHub OIDC in Actions; no personal token secret is required.

  1. Verify:

    curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=vybenetwork" | jq .
    

Cursor and other directories

Use examples/cursor-mcp.json as the install snippet. For Cursor Directory, submit after the registry publish succeeds; add X-API-KEY locally when you need execute-request.

Registry server id

Registry id: io.github.vybenetwork/vybe-solana-api (server.json name; display title is Solana MCP by Vybe).

Reviews

No reviews yet

Sign in to write a review