Vybe Solana API FAQs

Question 1

Can I use the Vybe Solana API with platforms like Cursor?

Accepted Answer

Absolutely. It's designed with Open Plugins compatibility and provides configuration examples like `cursor-mcp.json` to enable straightforward integration with directory UIs and platforms such as Cursor's Plugin Directory.

Question 2

How does it support integration with directory UIs and clients?

Accepted Answer

It hosts official `server.json` metadata for the MCP Registry and supports Open Plugins–style MCP configurations (`.mcp.json`, `mcp.json`), enabling directory UIs like Cursor to easily detect and integrate the plugin component.

Question 3

What is the Vybe Solana API?

Accepted Answer

The Vybe Solana API provides public registry metadata compliant with the Model Context Protocol (MCP), specifically designed to facilitate seamless integration of Vybe's Solana API with MCP-compatible clients and tools.

Question 4

Is API access to Vybe's tools secure?

Accepted Answer

Yes, access to Vybe API tools that require calls (e.g., `execute-request`) is secured via client-side `X-API-KEY` headers. API keys are managed externally and not stored in public repositories.

Question 5

How is the MCP registry metadata published and updated?

Accepted Answer

The metadata is automatically published to the official MCP Registry using GitHub Actions with OIDC, ensuring up-to-date and secure distribution without requiring personal tokens.

Vybe Solana API

Vybe Solana API

Key Features

Use Cases

Key Features

Use Cases