Marketstack

Provides access to Marketstack data through MCP tools for market data, references, and instruments.
  • typescript

1

GitHub Stars

typescript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "matteoantoci-mcp-marketstack": {
      "command": "node",
      "args": [
        "/path/to/mcp-marketstack/build/index.js"
      ],
      "env": {
        "MARKETSTACK_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

You have a Marketstack MCP Server that exposes Marketstack API endpoints as MCP tools, letting you query financial data from MCP-compatible agents and systems with simple, consistent tooling and caching for performance.

How to use

Start the server in your environment and connect an MCP client to discover and run the available tools. The server exposes data sources such as market data, reference data, and financial instruments, and supports introspection so your agents can learn input schemas and capabilities automatically.

How to install

Prerequisites you need before installing the server are: Node.js version 18 or later and npm (comes with Node.js). You also need a Marketstack API key to access the data.

Install dependencies and build the server:

npm install
npm run build

Using the MCP runner with stdio transport

Configure your MCP client to run the Marketstack MCP Server as a local stdio process. The client will launch the server and pass the API key through the environment.

Example MCP settings entry you can use in your MCP runner (adjust the path to your actual build output and replace YOUR_API_KEY_HERE):

"marketstack": {
  "transportType": "stdio",
  "command": "node",
  "args": [
    "/path/to/mcp-marketstack/build/index.js"
  ],
  "env": {
    "MARKETSTACK_API_KEY": "YOUR_API_KEY_HERE"
  }
  // ... other optional settings ...
}

Notes about usage and behavior

The server implements an in-memory Least Recently Used (LRU) cache to speed up responses and respect API rate limits. Each tool has its own Time To Live (TTL) configured to suit how often the corresponding Marketstack data should be refreshed.

Security and keys

Keep your Marketstack API key secure. Do not expose it in shared environments or logs. Provide it only through your MCP runner’s environment configuration for the stdio setup.

Troubleshooting

If you encounter connection issues, verify that the Marketstack API key is correctly provided to the server via the MCP runner and that Node.js is available in your execution environment. Check that the server has started and is listening for MCP connections, and consult the client logs for any introspection errors.

Notes

The server offers distinct MCP tools under three broad categories: Market Data, Reference Data, and Financial Instruments. Each tool advertises its input schemas and capabilities via MCP introspection so your agents can discover how to query and combine data from Marketstack effectively.

Available tools

marketData

Access market data endpoints such as end-of-day and intraday prices via dedicated MCP tools.

referenceData

Query reference data endpoints including tickers, exchanges, and currencies.

financialInstruments

Retrieve information about financial instruments, securities, and related entities.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational