CoinGecko Server

Created By
crazyrabbitLTCa year ago
An Anthropic MCP server (with OpenAI Function calling compatibility) for the Coingecko Pro API
Overview

what is CoinGecko Server?

CoinGecko Server is an Anthropic Model Context Protocol (MCP) server that provides an interface for interacting with the CoinGecko Pro API, allowing users to access cryptocurrency data seamlessly.

how to use CoinGecko Server?

To use CoinGecko Server, install it via npm, set up your environment with the required API key, and configure it with Claude Desktop or OpenAI Function Calling for data retrieval.

key features of CoinGecko Server?

  • Paginated list of supported cryptocurrencies
  • Coin ID lookup by name or symbol
  • Historical price, market cap, and volume data
  • OHLC (Open, High, Low, Close) candlestick data
  • Local coin cache with refresh capability

use cases of CoinGecko Server?

  1. Retrieving real-time cryptocurrency prices and market data.
  2. Analyzing historical price trends for investment decisions.
  3. Integrating cryptocurrency data into applications using OpenAI.

FAQ from CoinGecko Server?

  • What is required to use CoinGecko Server?

You need to install the server, create a .env file with your CoinGecko API key, and configure it with your application.

  • Can I use CoinGecko Server with OpenAI?

Yes! CoinGecko Server is compatible with OpenAI Function Calling, allowing you to retrieve data through OpenAI's API.

  • Is there a limit on API usage?

Yes, please refer to the CoinGecko Pro API documentation for current rate limits and usage guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
crazyrabbitLTC
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago