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.jsonandmcp.json— Open 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 usenpx mcp-remoteand the public MCP URL only — no API key in the repo. Add aX-API-KEYheader (or env) in your client when you need live Solana API calls (not just schema browsing); 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.
vybenetwork/solana-mcp-vybe (starts with solana-mcp, includes Vybe).
-
Clone or use this repo at
github.com/vybenetwork/solana-mcp-vybe. -
Tag and push (the workflow sets
server.jsonversionfrom 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.
-
Verify:
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=vybenetwork" | jq .
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 live API calls.
Active server.json name (required until the URL is freed): io.github.vybenetwork/vybe-solana-api. Display title: Solana MCP by Vybe.
Desired rename to io.github.vybenetwork/solana-mcp-vybe is blocked: one remote MCP URL per catalog entry. Track registry#1151. After operators remove the old binding, switch name and publish again.
Publish: push main, then git tag vX.Y.Z && git push origin vX.Y.Z, or Actions → Publish to MCP Registry.