🔗 MCP API

Introduction

Use the FinFeedAPI Flat Files MCP server to discover buckets, browse exchange prefixes, and enumerate downloadable flat files through self-describing tools.

Flat Files API MCP

The FinFeedAPI Flat Files API is available through a hosted Model Context Protocol (MCP) server at https://mcp.flatfiles.finfeedapi.com/mcp. It exposes a compact set of self-describing tools for browsing buckets and file paths from MCP clients such as Cursor, Claude Desktop, or custom agent runtimes.

Use your regular FinFeedAPI API key in the X-APIKey header.

What is available through MCP?

The Flat Files MCP server currently exposes 2 tools:

AreaWhat you can do
Bucket discoveryList the storage buckets available to your API key and inspect owner metadata.
Prefix and object discoveryBrowse exchange prefixes, dataset folders, and concrete .csv.gz objects using S3-style listings.

Typical discovery flow

Most integrations follow this order:

  1. Call storage_list_buckets to find the available bucket, typically finfeedapi.
  2. Call storage_list_objects with bucket: "finfeedapi" to enumerate top-level exchange prefixes such as E-IEXG/ or E-XWAR/.
  3. Call storage_list_objects again with a deeper prefix such as E-IEXG/ to discover dataset families like T-OHLCV+TP-1DAY/.
  4. Drill into a dataset prefix such as E-IEXG/T-OHLCV+TP-1DAY/ to enumerate actual files such as D-20161212.csv.gz.
  5. Use the discovered object key with the regular Flat Files S3 API when you want to download the file contents.

Live-tested notes

  • The current MCP listing returns one accessible bucket named finfeedapi.
  • Root-level object listing returns folder-style values in commonPrefixes, while contents remains empty until you browse a concrete dataset prefix.
  • Live examples currently include exchange prefixes such as E-IEXG/, E-XWAR/, E-XHKG/, and many others.
  • E-IEXG/ currently exposes T-OHLCV+TP-1SEC/, T-OHLCV+TP-1MIN/, and T-OHLCV+TP-1DAY/.
  • E-XWAR/ currently exposes T-OHLCV+TP-1DAY/.
  • A live file key observed through MCP is E-IEXG/T-OHLCV+TP-1DAY/D-20161212.csv.gz.

What MCP is best for

This MCP server is best suited for:

  • Interactive discovery of available exchanges and dataset prefixes
  • Agent workflows that need to inspect bucket structure before building download paths
  • Enumerating object metadata such as file key, last modification time, and size

If you need to download the file bytes, continue with the standard S3 API after discovering the object key through MCP.

Start here

Getting Started

Configure an MCP client, authenticate requests, and run your first bucket and object listings.

Tool Reference

Full reference for the Flat Files MCP tools, parameters, response shape, and usage patterns.

Service StatusGitHub SDK

Flat Files API

Access historical market data through our S3-compatible Flat Files API, Snowflake integration, and data type documentation.

Getting Started

Connect your MCP client to the FinFeedAPI Flat Files MCP server and start browsing buckets, prefixes, and object metadata.

On this page

Flat Files API MCPWhat is available through MCP?Typical discovery flowLive-tested notesWhat MCP is best forStart here