globaldatafeeds-mcp
An MCP server that exposes GlobalDataFeeds (GFDL) Indian market data — NSE, BSE, MCX, NFO, currency and indices — to any AI assistant (Claude, Cursor, VS Code Copilot, etc.).
You bring your own key. This server ships with no API key. Each user supplies their own GlobalDataFeeds access key through their client's config. Get a key from https://globaldatafeeds.in.
Tools
Quotes: get_last_quote, get_last_quote_short, get_last_quote_array, get_snapshot ·
History: get_history, get_history_after_market, get_exchange_snapshot ·
Discovery: get_exchanges, search_instruments, get_instruments, get_instrument_types,
get_products, get_expiry_dates, get_option_types, get_strike_prices ·
Derivatives: get_option_chain, get_option_greeks ·
Analytics: get_top_gainers_losers, get_volume_shockers ·
Account: get_server_info, get_limitation, get_market_messages, get_exchange_messages,
get_holidays.
Configuration
The server reads these environment variables:
| Variable | Required | Description |
|---|---|---|
GDF_API_KEY |
yes | Your personal GFDL access key. |
GDF_BASE_URL |
no | Your GFDL endpoint. Defaults to the shared test server. |
GDF_LOG |
no | Set to 0 to disable request logging. |
Connect it to your AI client
Each client passes your own key via an env block — the key never lives in the package.
Claude Desktop
Settings → Developer → Edit Config:
{
"mcpServers": {
"globaldatafeeds": {
"command": "uvx",
"args": ["globaldatafeeds-mcp"],
"env": {
"GDF_API_KEY": "YOUR_OWN_KEY",
"GDF_BASE_URL": "https://your-gfdl-endpoint:port"
}
}
}
}
Cursor
~/.cursor/mcp.json — same shape as above ("mcpServers" with the env block).
VS Code (Copilot)
.vscode/mcp.json — prompts for the key so it's never written to the file:
{
"inputs": [
{ "type": "promptString", "id": "gdf-key", "description": "GFDL API Key", "password": true }
],
"servers": {
"globaldatafeeds": {
"type": "stdio",
"command": "uvx",
"args": ["globaldatafeeds-mcp"],
"env": { "GDF_API_KEY": "${input:gdf-key}" }
}
}
}
Restart the client after editing its config.
Local development
uv sync
cp .env.example .env # put your key in .env
uv run mcp dev server.py # opens the MCP Inspector
License
MIT
Metadata
Release files for globaldatafeeds-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| globaldatafeeds_mcp-0.2.0.tar.gz | 6.2 kB | Without provenance | Details for globaldatafeeds_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| globaldatafeeds_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for globaldatafeeds_mcp-0.2.0-py3-none-any.whl |
Total release size: 13.2 kB
Release files / globaldatafeeds_mcp-0.2.0.tar.gz
| Download URL | globaldatafeeds_mcp-0.2.0.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
791b81b48af368a5590675e3935b594a8a60196571477492798feb501f2a4eb2
|
|
BLAKE2b-256 checksum How to use checksums |
d0d7c2402a2e71a5e22d7ab094fa1712d7047b4941be4bfffe49e34265c15384
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.15
|
Release files / globaldatafeeds_mcp-0.2.0-py3-none-any.whl
| Download URL | globaldatafeeds_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cde7af9c099a216ffc5921b082ce9ee08a8997492cf3c2d59b806523a45cfc60
|
|
BLAKE2b-256 checksum How to use checksums |
d965b7426ab4c5b001b7d1e10ee48b0f87a02eb8ebe09ad804d7335b62b755ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.15
|
Security for globaldatafeeds-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.