home / mcp / coinstats mcp server
Provides access to CoinStats market data, portfolio tracking and news via an MCP server.
Configuration
View docs{
"mcpServers": {
"coinstatshq-coinstats-mcp": {
"command": "npx",
"args": [
"-y",
"@coinstats/coinstats-mcp"
],
"env": {
"COINSTATS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}The CoinStats MCP Server lets you connect your MCP clients to CoinStats API data, enabling access to cryptocurrency market data, portfolio tracking, and news through a lightweight, configurable server. It supports running as a local process or via container and requires an API key from CoinStats to authenticate requests.
You can connect MCP clients to the CoinStats MCP Server in two main ways: running the server locally with NPX or using Docker. In both cases you must provide your CoinStats API key to authorize requests.
NPX method pulls and runs the MCP package on demand. The environment must supply your CoinStats API key.
Docker method runs the official MCP image in a container. Pass your CoinStats API key as an environment variable to authenticate. Use the method you prefer and ensure the API key is kept secure.
If you are using a client configuration file, you can enable the server by including one of these standard configurations. The following examples show the required command and environment for each method.
NPX configuration (inline JSON) demonstrates how to reference the CoinStats MCP Server in your client configuration. Replace <YOUR_API_KEY> with your actual API key.
{
"mcpServers": {
"coinstats-mcp": {
"command": "npx",
"args": [
"-y",
"@coinstats/coinstats-mcp"
],
"env": {
"COINSTATS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Docker configuration shows how to run the MCP server in a container. Replace <YOUR_API_KEY> with your actual CoinStats API key.
{
"mcpServers": {
"coinstats-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"COINSTATS_API_KEY",
"coinstats/coinstats-mcp"
],
"env": {
"COINSTATS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}