$git clone https://github.com/vybenetwork/solana-mcp-vybePublic Model Context Protocol (MCP) registry metadata for Solana MCP by Vybe.
| 1 | # Solana MCP by Vybe |
| 2 | Solana MCP by Vybe lets Cursor, Claude, and other MCP clients browse schemas or make live Solana API calls through one public MCP server. |
| 3 | |
| 4 | Public **Model Context Protocol (MCP) registry metadata** for **Solana MCP by Vybe**. |
| 5 | |
| 6 | The live MCP endpoint is: |
| 7 | |
| 8 | `https://mcp.vybenetwork.xyz` |
| 9 | |
| 10 | Product and setup guides: [docs.vybenetwork.com/docs/mcp](https://docs.vybenetwork.com/docs/mcp). |
| 11 | |
| 12 | This repository holds: |
| 13 | |
| 14 | - **`server.json`** — metadata published to the [official MCP Registry](https://registry.modelcontextprotocol.io) (GitHub Actions). |
| 15 | - **`.mcp.json` and `mcp.json`** — [Open Plugins](https://open-plugins.com)–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 MCP URL only — **no secrets in the repo.** Clients authenticate via **OAuth** for this host (see discovery on `https://mcp.vybenetwork.xyz`). |
| 16 | |
| 17 | `examples/cursor-mcp.json` is the same idea for native **`url`** config: URL only; use your client’s OAuth flow for this MCP. |
| 18 | |
| 19 | ## GitHub repository name |
| 20 | |
| 21 | **`vybenetwork/solana-mcp-vybe`** (starts with `solana-mcp`, includes Vybe). |
| 22 | |
| 23 | ## Publish a new listing version |
| 24 | |
| 25 | 1. Clone or use this repo at `github.com/vybenetwork/solana-mcp-vybe`. |
| 26 | 2. Tag and push (the workflow sets `server.json` `version` from the tag): |
| 27 | |
| 28 | ```bash |
| 29 | git tag v1.0.0 |
| 30 | git push origin v1.0.0 |
| 31 | ``` |
| 32 | |
| 33 | Or run **Actions → Publish to MCP Registry → Run workflow** (uses the version already in `server.json`). |
| 34 | |
| 35 | Publishing uses **GitHub OIDC** in Actions; no personal token secret is required. |
| 36 | |
| 37 | **If you use `mcp-publisher login github` locally** and get **403** for `io.github.vybenetwork/...`: Git apps like **Git Credential Manager** are unrelated. Open **GitHub → Settings → Applications → Authorized OAuth Apps**, choose the app you authorized during **`mcp-publisher login github`** (device flow), then under **Organization access** click **Grant** for **`vybenetwork`**. On SAML-enforced orgs, also complete **SSO** for that OAuth app. Then run **`mcp-publisher logout`**, **`mcp-publisher login github`**, and **`publish`** again. |
| 38 | |
| 39 | 3. Verify: |
| 40 | |
| 41 | ```bash |
| 42 | curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=vybenetwork" | jq . |
| 43 | ``` |
| 44 | |
| 45 | ## Cursor and other directories |
| 46 | |
| 47 | Use `examples/cursor-mcp.json` as the install snippet. For [Cursor Directory](https://cursor.directory), submit after the registry publish succeeds; use **OAuth** (or whatever your client supports) for `https://mcp.vybenetwork.xyz`. |
| 48 | |
| 49 | ## Registry catalog id |
| 50 | |
| 51 | **`server.json` `name`:** **`io.github.vybenetwork/solana-mcp-vybe`**. **Display title:** **Solana MCP by Vybe**. |
| 52 | |
| 53 | **Publish:** push `main`, then `git tag vX.Y.Z && git push origin vX.Y.Z`, or **Actions → Publish to MCP Registry**. |