charieswei
/
vibe-coding-cn
mirror of https://github.com/tukuaiai/vibe-coding-cn.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
vibe-coding-cn/i18n/en/skills/coingecko/references/introduction.md

36 KiB
Raw Blame History

Coingecko - Introduction

Pages: 4

🔥 Getting Started

URL: llms-txt#🔥-getting-started

Contents:

  • Which MCP Server Should You Use?
  • 🔗 Endpoint Options
    • Primary Endpoint (HTTP Streaming)
    • Alternative Endpoint (SSE — Server-Sent Events)
  • Remote Server (Public, Keyless)
  • Remote Server (Authenticated)
    • Step 1: Add the configuration
    • Step 2: Authorize your MCP access
  • Local Server (API Key Required)

Connecting your AI to CoinGecko is simple. We offer several MCP server options to fit your needs, from keyless access for testing to authenticated connections for production applications.

Most MCP-compatible clients, like Claude Desktop, Gemini CLI, and Cursor, can be configured using a simple JSON file (e.g., claude_desktop_config.json)

### Prerequisites

Which MCP Server Should You Use?

Here's a breakdown of the available options to help you choose the right one:

MCP Server Type Best For Endpoints Status Setup Details
Remote Server (Public, Keyless) - First-time users, quick tests, and basic queries
- Connect instantly without any registration
- Subject to shared rate limits, not for heavy use		 Primary: /mcp
Alternative: /sse		 Public Beta mcp.api.coingecko.com
Remote Server (Authenticated) - Scalable apps, AI agent integrations
- Unlocks 76+ tools available under your Demo/Pro plan
- Higher, reliable rate limits with 24/7 uptime. Get your API key here		 Primary: /mcp
Alternative: /sse		 Public Beta mcp.pro-api.coingecko.com
Local Server - Ideal for local development, desktop AI apps
- Build/test your AI app even without an active internet connection
- Demo/Pro API key to access more tools. Get your API key here		 Local server instance Beta npmjs/coingecko-mcp

🔗 Endpoint Options

Each remote server offers two connection methods to ensure compatibility with various MCP clients:

Primary Endpoint (HTTP Streaming)

  • Public Server: https://mcp.api.coingecko.com/mcp
  • Pro Server: https://mcp.pro-api.coingecko.com/mcp
  • Uses HTTP streaming protocol for real-time data transfer.
  • Recommended for most modern MCP clients.

Alternative Endpoint (SSE — Server-Sent Events)

  • Public Server: https://mcp.api.coingecko.com/sse
  • Pro Server: https://mcp.pro-api.coingecko.com/sse
  • Uses Server-Sent Events for compatibility.
  • Use this if you encounter connection issues with the primary endpoint.
Most clients work with either endpoint. The configuration examples below use the SSE endpoint by default for maximum compatibility.

Remote Server (Public, Keyless)

The easiest way to get started. Just add the following to your client's mcp_config.json file.

### Client-Specific Config

The file name and location depend on your client. Find your config file here: modelcontextprotocol.io/quickstart

Add the following configuration to your mcp_config.json:

Here's a quick 2-minute tutorial for setting up the public server with Claude Desktop: