Skip to content

Add Alpaca’s official MCP server to community servers list #2024

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

idsts2670
Copy link

Add Alpaca’s MCP server to community servers list


Description

This pull request adds Alpaca’s official MCP server to the community servers list in the README. It follows the existing format and styling so contributors can quickly find and leverage Alpaca’s server for algorithmic trading workflows.


Server Details

  • Server: GitHub
  • Changes to: README.md (third-party/community servers section)

Motivation and Context

Many traders and developers want a low-code way to interact with Alpaca’s Trading API directly from AI tools. By listing Alpaca’s MCP server here, we:

  • Surface a fully supported, developer-first integration for stocks and options trading.
  • Help newcomers discover how to analyze market data, build strategies, and place orders algorithmically using plain English.
  • Maintain consistency with other community entries, making it easy for AI platform/IDE users (Claude, VS Code, Cursor, etc.) to find and adopt this server.

How Has This Been Tested?

  • Verified that the README update renders correctly in GitHub’s Markdown preview.
  • Confirmed that the link points to the correct repository (alpaca-mcp-server).
  • Ran a sample query via Claude Desktop and Cursor against Alpaca’s MCP server to ensure all the endpoints respond (e.g., "Get current account balance").

Breaking Changes

  • None. This is purely a documentation update; no MCP client configuration changes are required.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation update (adds new server listing)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the [MCP Protocol Documentation](https://modelcontextprotocol.io)
  • My changes follow MCP security best practices
  • I have updated the server’s README accordingly
  • I have tested this with an LLM client (e.g., Claude Desktop)
  • My code (or docs) follows the repository’s style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling (N/A for docs)
  • I have documented all environment variables and configuration options (N/A for docs)

Additional context

This entry should appear alphabetically under the “Community Servers” section, immediately after any server whose name begins with “Al…” (e.g., “Alloy”). If this section grows, it may be helpful to split servers by category (e.g., “Finance,” “Productivity”) in the future.

idsts2670 added 3 commits June 5, 2025 11:58
Add Alpaca's MCP server to community servers list
Add Alpaca MCP server to community servers list in README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant