Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http cftc-cot 'https://gateway.pipeworx.io/cftc-cot/mcp'{
"mcpServers": {
"cftc-cot": {
"type": "http",
"url": "https://gateway.pipeworx.io/cftc-cot/mcp"
}
}
}@pipeworx/mcp-cftc-cotclaude mcp add cftc-cot -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-cftc-cot@0.2.1{
"mcpServers": {
"cftc-cot": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-cftc-cot@0.2.1"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-cftc-cot
CFTC Commitment of Traders (COT) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
search_markets | Find CFTC Commitment of Traders (COT) futures markets by name. Use this first to get the exact market_and_exchange_names and contract_code that latest_report and report_history require. Keyless. e.g. "crude oil", "gold", "E-MINI S&P", "bitcoin", "euro", "corn". |
latest_report | Most recent weekly COT positioning for one futures market. Pass the exact market_and_exchange_names from search_markets, e.g. "CRUDE OIL, LIGHT SWEET-WTI - NEW YORK MERCANTILE EXCHANGE" or "GOLD - COMMODITY EXCHANGE INC.". Returns open interest plus long/short/net for non-commercial (≈ speculators: managed money / large traders), commercial (≈ hedgers / producers), and non-reportable (small traders), with this week's changes. Keyless. |
report_history | Weekly net-position time series for one futures market (non-commercial net, commercial net, open interest), most recent first. Pass the exact market_and_exchange_names from search_markets. Useful for trend / sentiment shifts over time. Keyless. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"cftc-cot": {
"url": "https://gateway.pipeworx.io/cftc-cot/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/cftc-cot/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/cftc_cot_search_markets \
-H 'Content-Type: application/json' \
-d '{"query":"crude oil"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/cftc_cot_search_markets. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"cftc-cot": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cftc-cot"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-cftc-cotIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Cftc Cot data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Cftc Cot?
CFTC Commitment of Traders (COT) MCP.
How do I install Cftc Cot?
It runs as a remote server. In Claude Code: claude mcp add --transport http cftc-cot 'https://gateway.pipeworx.io/cftc-cot/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Cftc Cot need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Cftc Cot open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Cftc Cot?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.