Alpaca + Grok Bot

How to connect Alpaca to Grok Bot

Connect Alpaca to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Alpaca tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects Alpaca to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in Alpaca with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Grok Bot with your Agent200 API key. Your Alpaca account is connected through managed OAuth: you approve access once on Alpaca's own page, and Agent200 keeps the connection working.

Connector
Alpaca
Works with
Grok Bot ยท Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
7 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Alpaca enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Alpaca account. They approve access once, on Alpaca's own page.
  • Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

Connect Alpaca to Grok Bot

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Alpaca and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Open the custom connector form

    In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.

  3. 3

    Step 3: Fill in the server and your key

    Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header: Authorization with the value Bearer followed by your key. Leave Client ID empty, then choose Add plugin.

    Add a custom connector
    MCP: Grok Bot custom connector form
    Name:          Agent200
    Type:          Remote HTTPS
    Server URL:    https://api.agent200.com/mcp/
    HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
  4. 4

    Step 4: Attach Agent200 in a chat

    In a Bot chat, type @ and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

  5. 5

    Step 5: Connect your Alpaca account

    The first time you ask Grok Bot for something in Alpaca, Agent200 returns an authorization link. Open it and approve access on Alpaca's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

Test your connection

Run one request to check everything is wired up.

Ask

What is my buying power on Alpaca

What should come back

  • A result from that user's own Alpaca account.
  • Behind the scenes, Grok Bot calls alpaca_get_account.

If you get an authorization link instead, the user has not connected Alpaca yet. Show them the link, then run the request again.

Get your API key

Create a key in the Agent200 dashboard. It reaches Alpaca and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Alpaca to Grok Bot.

Agent brief
Goal: connect Alpaca to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/alpaca/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Alpaca is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. The first Alpaca request returns an authorization link if the user has not connected Alpaca yet: show it to them and continue once they have approved access on Alpaca's own page.
5. Check it works with this request: "What is my buying power on Alpaca"
   What should come back:
   - A result from that user's own Alpaca account.
   - Behind the scenes, Grok Bot calls `alpaca_get_account`.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Alpaca, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/alpaca/framework/grok-bot.md

Alpaca tools Grok Bot can call

  • Get the account

    Read
    alpaca_get_account

    Read the account's buying power, cash and equity.

  • List positions

    Read
    alpaca_list_positions

    List the open positions.

  • List orders

    Read
    alpaca_list_orders

    List open and past orders.

  • Get latest quote

    Read
    alpaca_get_latest_quote

    Get the latest bid and ask for a symbol.

  • List assets

    Read
    alpaca_list_assets

    List the assets that can be traded.

  • Place an order

    Write
    alpaca_create_order

    Place a market, limit or stop order.

  • Cancel an order

    Write
    alpaca_cancel_order

    Cancel an open order.

How it works

  1. 01

    You ask Grok Bot

    In your own words, for something in Alpaca.

  2. 02

    Grok Bot picks a tool

    It sees the Alpaca tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Alpaca connection, within the tools and scopes your project allows.

  4. 04

    Grok Bot answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Alpaca account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Alpaca enforces what its API grants.

Troubleshooting

The server cannot be saved, or shows Disabled by team admin

Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.

Calls fail on a team with a network allowlist

If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.

The connector shows Needs auth, or tools return 401

Check the Authorization header is exactly Bearer, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.

The Bot cannot see the Alpaca tools

Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.

Grok Bot shows a Alpaca authorization link

You have not connected Alpaca yet, or the connection needs to be approved again. Open the link, approve access on Alpaca's own page, then ask Grok Bot again.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Alpaca and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Alpaca the access the task needs.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.

Use Alpaca with another framework

200 OK

Alpaca, connected to Grok Bot.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)