Skip to main content
Access the official remote MCP server for fcontext market data.

Overview

Your AI assistant can use the fcontext MCP server to access authenticated, metered market data through your fcontext account. The first version exposes tools for realtime quotes, static instrument data, calculated quote indexes, candlesticks, market news, finance calendars, and top movers. The remote MCP endpoint is:

Authentication

The MCP server uses OAuth 2.1. When an interactive MCP client connects for the first time, it redirects you to sign in and approve market-data access. No API key is needed for MCP clients. The authorization server is:
MCP access tokens are JWTs bound to the MCP resource audience:
Tokens must include the market_data scope.
API keys are for the HTTP Market Data API at https://openapi.fcontext.com/api/market-data. MCP clients should use OAuth unless you are building your own server-side integration.

Getting Started

Choose a client that supports remote MCP servers and add the fcontext endpoint:
Add a remote MCP server with this URL:
Complete the OAuth sign-in flow when Codex prompts you, then enable the server for chats that need market data.

Agent Skills

Install the Financial Context skill package so Codex, Claude Code, or another agent can discover the supported workflows and choose the right MCP or CLI calls.
The skill package does not replace MCP authentication. Keep the MCP server connected with OAuth so tool calls can use your Financial Context account and market_data scope.

MCP Tools

Once connected, your AI assistant can call these tools: Tool calls use your fcontext account for access, billing, and usage analytics, matching the HTTP Market Data API.

Example Usage

After connecting, try asking your AI assistant:
  • “What is Apple’s latest quote?”
  • “Show me one month of daily candlesticks for Nvidia.”
  • “What are today’s top US market movers?”
  • “Find recent news for Tesla.”
  • “Check upcoming finance calendar events for this week.”
  • “Compare static information for AAPL.US and MSFT.US.”

Troubleshooting