home / mcp / cg-alpha mcp server

cg-alpha MCP Server

MCP server integrating ELFA crypto data, CoinGecko prices, and built-in technical analysis (RSI & Bollinger Bands).

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "jcf0-cg-alpha-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/cg-alpha-mcp/mcp-server.js"
      ],
      "env": {
        "ELFA_BASE": "https://api.elfa.ai",
        "ELFA_HEADER": "x-elfa-api-key",
        "ELFA_API_KEY": "YOUR_ELFA_API_KEY",
        "ELFA_AUTH_TYPE": "x-elfa-api-key",
        "COINGECKO_API_KEY": "YOUR_COINGECKO_API_KEY"
      }
    }
  }
}

You run cg-alpha MCP Server to connect ELFA data and CoinGecko MCP data, with a tiny TA module for quick token performance insights. It exposes a set of MCP tools you can invoke from your MCP client to fetch trending tokens, token news, keyword mentions, and generic ELFA queries, plus built-in RSI and Bollinger Bands calculations for price series.

How to use

Connect cg-alpha MCP Server to your MCP client (Claude Desktop, Cursor, or similar) as a local server. Once connected, you can access a set of tools that let you pull ELFA data, CoinGecko data, and perform quick TA calculations. Typical workflows include comparing top trending tokens from ELFA and CoinGecko, fetching token news, and computing RSI or Bollinger Bands for selected tokens across different timeframes.

How to install

# 1) Clone the project
git clone https://github.com/<you>/cg-alpha-mcp.git

# 2) Change into the project directory
cd cg-alpha-mcp

# 3) Install dependencies
npm install

# 4) Create a private env file from the template
cp .env.example .env

# 5) Populate environment variables in .env
#   ELFA_API_KEY=YOUR_ELFA_API_KEY
#   COINGECKO_API_KEY=YOUR_COINGECKO_API_KEY (optional)
```} ,{

Additional sections

Configure and run cg-alpha MCP Server locally. The server is designed to be loaded by an MCP client as a local, stdio-based server. Use Node to start the server from its runtime script.

Configuration and runtime tips

Environment variables control how the server talks to external services. You can adjust header behavior and base URL to fit your setup. The key variables you’ll encounter are ELFA_API_KEY, ELFA_HEADER, ELFA_AUTH_TYPE, ELFA_BASE, and COINGECKO_API_KEY. Keep your .env file private and ensure it is placed alongside mcp-server.js or in the working directory used by your MCP client.

Troubleshooting

401 errors indicate missing or invalid ELFA API keys. Ensure ELFA_API_KEY is set in your .env file and reload the environment in your MCP client using the provided command elfa_reload_env to apply changes without restarting the server.

Available tools

elfa_status

Shows current base URL and masked auth status for quick health checks.

elfa_reload_env

Reloads the environment variables from .env at runtime without restarting the server.

elfa_set_auth

Manually sets the API key and header style if needed, using a JSON payload.

elfa_trending

Wrapper around the ELFA trending endpoint to fetch top tokens in a given timeframe.

elfa_token_news

Fetches token news for specified symbols with optional date range.

elfa_keyword_mentions

Fetches keyword mentions with a limit for multi-keyword analysis.

elfa_query

Generic proxy to call any ELFA path with method and query parameters.

rsi

Technical Analysis RSI calculation for a price series (14-period by default).

bollinger

Technical Analysis Bollinger Bands calculation for a price series (default 20-day period, 2 std dev).