Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Stock Tracker what's the current price of AAPL?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides real-time stock price tracking with an interactive dashboard.
Or install manually: Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to uvx mcp-stock-tracker. Click "Add Extension".
Add to your MCP client configuration:
{
"mcpServers": {
"stock-tracker": {
"command": "uvx",
"args": ["mcp-stock-tracker"],
"env": {
"ALPHA_VANTAGE_API_KEY": "your-api-key-here"
}
}
}
}Related MCP server: Stocks MCP Server
This server requires an Alpha Vantage API key to fetch stock data.
Sign up for a free API key (25 requests/day)
Premium tiers with higher limits available at https://www.alphavantage.co/premium/
Real-time stock quotes via Alpha Vantage API
Interactive web dashboard for tracking multiple stocks
Auto-refresh every 30 seconds
Visual price change indicators (green/red)
Track price, volume, and daily high/low
Tool | Description |
| Fetch real-time stock data for a symbol |
Resource | Description |
| Interactive dashboard UI |
git clone https://github.com/DOsinga/mcp_app_stocks.git
cd mcp_app_stocks
pip install -e ".[dev]"MIT License
Get real-time stock quote for a symbol
Args: symbol: Stock ticker symbol (e.g., AAPL, MSFT, GOOGL)
Returns: Dictionary containing stock quote data including price, change, volume, etc.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavioral traits. It states the tool returns 'real-time' data, which implies a read operation, but does not explicitly confirm it is safe (no side effects) or mention any rate limits, authentication needs, or error conditions. The disclosure is insufficient for a tool that likely interacts with an external API.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a well-structured docstring with Args and Returns sections. It is concise (few sentences) yet informative, with no redundant or irrelevant content. Every sentence adds value, and the structure aids quick parsing by an AI agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (single parameter, no output schema, no siblings), the description is partially complete. It clearly defines the purpose and parameter, but lacks usage guidance and behavioral transparency. For a minimal viable description, it meets the basics but has clear gaps that could be filled.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Despite 0% schema coverage, the description adds substantial meaning to the only parameter: 'symbol: Stock ticker symbol (e.g., AAPL, MSFT, GOOGL)'. It clearly explains the domain and provides examples. This compensates well for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get real-time stock quote for a symbol'. The verb 'Get' and resource 'stock quote' are specific, and the scope is defined. Since there are no sibling tools, no differentiation is needed. The description is direct and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool or when not to. There are no alternatives mentioned, and no context about prerequisites or limitations (e.g., which exchanges are supported). The agent receives no help in deciding whether to invoke this tool over hypothetical others.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined for retrieving a stock quote.
The single tool name follows a clear verb_noun pattern (get_stock_quote), which is consistent and readable. However, with only one tool, pattern consistency across multiple tools cannot be fully assessed.
One tool is insufficient for a stock tracker. Users would expect additional functionality such as symbol lookup, historical data, or portfolio management, making the count feel overly minimal.
The tool surface is severely incomplete. A stock tracker should at least include listing available symbols or fetching historical prices, but only a single quote retrieval is provided.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Alpha Vantage MCP — Stock market data, fundamentals, and earnings
Live market data, financial analysis, and portfolio research tools across 10,000+ tickers.
Real-time news with bias scoring, live market data, and AI-powered options pricing
Live US options chains with Greeks and IV, a screener, SQL, and FMP fundamentals.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DOsinga/mcp_app_stocks'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
