by byul-ai
mcp-byul: Access real-time financial data via the Byul API — breaking economic news, Fear & Greed Index, and a global ec
Provides real-time financial data via the Byul API including breaking economic news, Fear & Greed Index, and economic calendar events.
mcp-byul is an official MCP server published by byul-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. mcp-byul: Access real-time financial data via the Byul API — breaking economic news, Fear & Greed Index, and a global ec It is categorized under finance, developer tools.
You can install mcp-byul in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
mcp-byul is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Strong directory entry: mcp-byul surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, mcp-byul benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend mcp-byul for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend mcp-byul for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated mcp-byul against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend mcp-byul for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
mcp-byul has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: mcp-byul surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: mcp-byul surfaces stars and publisher context so we could sanity-check maintenance before adopting.
mcp-byul is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 57
Compliant with the latest Model Context Protocol (MCP) specification.
@byul/mcp is a stdio-based MCP server that proxies the Byul REST API. It exposes a small set of MCP tools and a resource that forward requests to Byul endpoints and return the original JSON response, plus a short article-count summary string.
BYUL_API_KEY environment variableBYUL_API_KEY=byul_xxxxxxxxxxxxx npx -y @byul/mcp
Register this server as an MCP provider in your LLM client. The client will launch the server via stdio and communicate using JSON-RPC over stdin/stdout.
@docs for the full spec)
news_fetch → proxies GET /news with filters: limit, cursor, sinceId, minImportance, q, symbol, startDate, endDate@docs for the full spec)
byul://news{?limit,cursor,sinceId,minImportance,q,symbol,startDate,endDate}Each response contains:
news_fetchlimit (number, optional) – number of articles (1-100)cursor (string, optional) – pagination cursor from previous pagesinceId (string, optional) – return articles created after this IDminImportance (number, optional) – minimum importance (1-10)q (string, optional) – search querysymbol (string, optional) – stock symbol (e.g., AAPL)startDate (string, optional) – ISO 8601 start timestamp (UTC)endDate (string, optional) – ISO 8601 end timestamp (UTC)Fetch top 5 news articles about AAPL from the past week
BYUL_API_KEY environment variable only. Do not hardcode credentials in code or configs.~/.cursor/mcp.json or project .cursor/mcp.json:
{
"mcpServers": {
"byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": { "BYUL_API_KEY": "byul_xxxxxxxxxxxxx" }
}
}
}
claude mcp add -e BYUL_API_KEY=byul_xxxxxxxxxxxxx --scope user byul npx -- -y @byul/mcp
{
"mcpServers": {
"byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": { "BYUL_API_KEY": "byul_xxxxxxxxxxxxx" }
}
}
}
claude_desktop_config.json:{
"mcpServers": {
"byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": { "BYUL_API_KEY": "byul_xxxxxxxxxxxxx" }
}
}
}
.vscode/mcp.json:{
"mcpServers": {
"byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": { "BYUL_API_KEY": "byul_xxxxxxxxxxxxx" }
}
}
}
windsurf_mcp.json:{
"mcpServers": {
"mcp-server-byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": {
"BYUL_API_KEY": "byul_xxxxxxxxxxxxx"
}
}
}
}
~/.gemini/settings.json:
{
"mcpServers": {
"byul": {
"command": "npx",
"args": ["-y", "@byul/mcp"],
"env": { "BYUL_API_KEY": "byul_xxxxxxxxxxxxx" }
}
}
}
If the mcpServers object does not exist, create it. This package supports stdio (local) transport only.
Missing API key
Missing BYUL_API_KEY environment variableBYUL_API_KEY in your environment before launching the serverCorporate proxy / firewall
npx must reach the registry to download @byul/mcp on first run; configure your proxy settings accordinglyWindows / WSL path and env
$env:BYUL_API_KEY = "byul_xxxxxxxxxxxxx"
npx -y @byul/mcp
Transport scope
Compliant with the latest Model Context Protocol (MCP) specification.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.