Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA
README.md
<img width="1920" height="1080" alt="Copia de que es (4) (1)" src="https://github.com/user-attachments/assets/510e6db8-cc45-486e-88c0-7e80f2c2e9fa" />
# 🚀 Tu Primer Servidor MCP con Gemini CLI: Domina la Terminal con IA 💻

¡Bienvenido a tu aventura para conectar Gemini CLI con un servidor MCP (Model Context Protocol)! 🎉  
Este proyecto te permite interactuar con la API de CoinGecko usando Gemini CLI, desbloqueando un arsenal de herramientas para obtener datos de criptomonedas: precios, tendencias, NFTs y mucho más. Aprende a configurarlo local o remotamente con esta guía paso a paso. 🌐

---

## 🎥 Tutorial en Video  
Aprende en vivo cómo conectar tu primer servidor MCP, explora sus herramientas y automatiza tus proyectos como un experto en IA terminal.  
🔗 [Ver video en YouTube]([https://youtu.be/xxxx](https://www.youtube.com/watch?v=VnJpMbtYxS4)

[![Mira el tutorial](https://img.youtube.com/vi/VnJpMbtYxS4/0.jpg)](https://www.youtube.com/watch?v=VnJpMbtYxS4)


---

## 🌍 Únete a la Comunidad  
Comparte, aprende y crece con iacomunia.com – tu espacio para innovar con inteligencia artificial y automatización.

---

## 🛠 ¿Qué es este proyecto?  
Un servidor MCP para conectar Gemini CLI con la API de CoinGecko.  
⚡ Al arrancar obtendrás acceso a 46 herramientas para consultas cripto avanzadas, con comandos simples y mucha potencia.

---

## 📋 Requisitos  
- Node.js 20.18.1+ (`node --version`)  
- Yarn (`yarn --version`)  
- Gemini CLI instalado y configurado

---

## ⚙️ Instalación rápida

`
git clone https://github.com/IAcomunIA/MCP_firts.git
cd MCP_firts
yarn install

`
---

## 🔧 Configuración

1. Crea archivo `.env` con tu API key (opcional para demo):

`

COINGECKO_DEMO_API_KEY=tu-api-key

`
2. Modifica la configuración de Gemini CLI en `~/.gemini/settings.json`  
👉 **Opción Local:**

```json
{
  "mcpServers": {
    "coingecko_mcp_local": {
      "command": "npx",
      "args": ["-y", "@coingecko/coingecko-mcp"],
      "cwd": "/ruta/a/MCP_firts/",
      "env": {
        "COINGECKO_DEMO_API_KEY": "YOUR_DEMO_API_KEY",
        "COINGECKO_ENVIRONMENT": "demo"
      }
    }
  }
}
```
👉 **Opción Remota:**
```json
{
"mcpServers": {
"coingecko_mcp": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.api.coingecko.com/sse"
]
}
}
}
```
---

## 🚦 Cómo usar

Arranca el servidor local:
```json
yarn start
```
Interactúa con Gemini CLI usando comandos como:
```json
gemini get_simple_price
gemini get_coins_markets
```
¡Explora todas las herramientas y automatiza consultas cripto directas!

---

## 🐛 Solución de problemas comunes

- **No encuentra MCP:** Revisa que la ruta `cwd` en settings.json sea correcta.  
- **API Key inválida:** Usa modo demo o verifica tu `.env`.  
- **Problemas con Yarn:** Instala o actualiza `yarn` y ejecuta `yarn install` otra vez.

---

## 🌟 Recursos útiles

- [Awesome MCP Servers – 1000+ MCP open source](https://github.com/wong2/awesome-mcp-servers)  
- [Documentación oficial CoinGecko API](https://www.coingecko.com/en/api)  
- [Comunidad iacomunia.com](https://iacomunia.com)

---

## 🤝 ¿Quieres contribuir?  
¿Tienes mejoras o ideas? ¡Abre un issue o pull request!  
Sé parte activa y crece junto a la comunidad MCP.

---

*¡A programar y automatizar con inteligencia artificial en tu terminal!* 🚀  
*❤️ Hecho con pasión por la comunidad iAcomunIA*

TDQS

B3.2/5.0

Scored across 50 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific resources like coins, NFTs, exchanges, pools, or tokens, with clear descriptions that differentiate them. However, some overlap exists, such as multiple price-fetching tools (e.g., get_simple_price, get_id_simple_token_price, get_addresses_networks_simple_onchain_token_price) that could cause confusion in selection, though descriptions help clarify contexts like on-chain vs. API IDs.

Naming Consistency3/5

The naming follows a general get_ prefix pattern but is inconsistent in structure. Some tools use verb_noun (e.g., get_coins_markets), while others have long, descriptive names with underscores separating multiple nouns (e.g., get_addresses_networks_simple_onchain_token_price). There's no uniform convention, making it mixed but still readable due to the consistent use of underscores and the get_ prefix.

Tool Count2/5

With 50 tools, the count is excessive for a single server, even given the broad domain of cryptocurrency data. This many tools can overwhelm agents and increase cognitive load, as it includes highly specialized endpoints (e.g., for on-chain pools, NFTs, public treasury) that might be better organized into sub-servers or modules. It feels heavy and unwieldy for typical agent use.

Completeness5/5

The tool set is exceptionally comprehensive for the CoinGecko and GeckoTerminal APIs, covering a wide range of cryptocurrency data including coins, markets, NFTs, exchanges, on-chain analytics, and public treasury information. It provides extensive read operations with historical data, charts, searches, and metadata, leaving no obvious gaps for querying cryptocurrency information within the scope of these APIs.

Maintenance

ActivityInactive
ResponsivenessNo issues