Use Moby with Grok
Your agent runs through Grok, and you manage it from your phone.
Your AI agent trades Solana tokens, including memes, majors and tokenized stocks (xStocks on Solana, like TSLAx), with your USDC, inside the limits you set.
Availability of tokenized stocks (xStocks on Solana, like TSLAx) can vary by region.
AI Trading on Base, BNB Chain and Robinhood Chain is coming soon.
This Grok setup is the Grok piece of agentic trading on Moby. The Moby app is where you set limits and revoke a key.
The Grok app can add a custom MCP URL. Its docs do not show how to pass Moby's bearer key. The xAI API documents that as the authorization parameter. Other clients: Codex and Claude Code.
Connect Grok to the Moby MCP server
-
Create a key in the Moby app
Download Moby. Open the Agent tab, tap Connect, and create a key. The key starts with moby_agent_. It links Grok to your Moby account. It is an agent API key, not a wallet private key. Do not paste it into chat. You can revoke it in the app.
-
Read what the Grok app documents
The Grok connector docs say connectors are available to all Grok users. For a custom MCP server, go to grok.com/connectors, click New Connector, then select Custom, enter the MCP server URL, and complete any required authentication. The server must be reachable on the public internet. Those docs do not describe a field for a static Authorization header. Moby has no sign-in flow. The header Moby expects is Authorization: Bearer moby_agent_... with your key in place of the placeholder. Use the xAI API or Grok Build, below, to send it.
On Grok Business and Enterprise, a team admin adds the connector first. The connector-management docs say to open the cloud console, then Grok Business, then Connectors, click Add Connector, select Other, and enter the MCP server URL. Those docs also stop at required authentication. They do not document the bearer header.
-
Send the key with the xAI API
Remote MCP tools are a tool on the xAI API. POST the JSON to https://api.x.ai/v1/responses. The request header is Authorization: Bearer followed by your XAI_API_KEY. That is the xAI API key, not the Moby key. The tool type is mcp. server_url is https://mcp.moby.win/mcp. server_label is moby. Set authorization to the Moby key only, with no Bearer prefix. The placeholder is moby_agent_... The remote MCP docs say this token is set in the Authorization header. The xAI cookbook says authorization reaches the server as Authorization: Bearer followed by that token. The examples on the remote MCP page use the model grok-4.7. The docs allow Streaming HTTP and SSE. Leave allowed_tools empty to load every Moby tool.
Body for POST https://api.x.ai/v1/responses. Placeholder only. Do not put Bearer inside authorization.
{ "model": "grok-4.7", "input": "What is in my Moby wallet? Do not trade.", "tools": [ { "type": "mcp", "server_url": "https://mcp.moby.win/mcp", "server_label": "moby", "authorization": "moby_agent_..." } ] }Same fields in the xAI SDK. The docs import mcp from xai_sdk.tools.
from xai_sdk.tools import mcp mcp( server_url="https://mcp.moby.win/mcp", server_label="moby", authorization="moby_agent_...", )The same page says require_approval and connector_id are not supported. Do not copy those fields from another vendor's example.
-
Or add the server in Grok Build
Grok Build is the grok CLI, not the Grok app. The MCP servers guide shows grok mcp add --transport http with --header for a static bearer token. Export MOBY_API_KEY as the key itself, then run the command in the block. Grok expands ${MOBY_API_KEY} in headers in ~/.grok/config.toml, so the file can keep the variable. Run grok mcp list to confirm the server. In the Grok Build TUI, /mcps opens the MCP tab.
Documented Grok Build command. The shell expands MOBY_API_KEY. Placeholder only.
grok mcp add --transport http moby https://mcp.moby.win/mcp --header "Authorization: Bearer ${MOBY_API_KEY}"Or ~/.grok/config.toml. The guide says ${VAR} in headers expands at load time.
[mcp_servers.moby] url = "https://mcp.moby.win/mcp" headers = { "Authorization" = "Bearer ${MOBY_API_KEY}" }
Docs: Grok connectors, connector management, remote MCP tools, the database-over-MCP cookbook, and Grok Build MCP servers. The remote MCP page also lists the xAI SDK and the Speech to Speech API as clients of this tool.
Link your account and set limits
You set your agent's limits on max per trade, daily buy volume and market-cap range from the Moby app, and Moby checks them server-side on every buy. The agent trades Solana only, funded with USDC. There are no withdrawals through MCP.
The key from the Agent tab, Connect, is what links Grok to your Moby account. On first connect, Grok should call get_my_trading_profile and follow the onboarding on the agents page. Revoke the key there to turn it off. A profile saved by Grok cannot raise the app limits.
Install a Grok Build skill
The Grok connector docs for grok.com do not describe a skill folder. Grok Build does. It discovers skills in .grok/skills from the current directory up to the repo root, in ~/.grok/skills, in an enabled plugin, and in extra paths under config.toml. A skill is a folder with a SKILL.md file. The name defaults to the folder name. Invoke it with /moby-knowledge. Grok Build also reads ~/.agents/skills and Claude Code skill folders with no extra setup. Docs: Skills, plugins, and marketplaces.
Moby Knowledge is Moby's reference for how the agent works. To keep that as a Grok Build skill, save this folder as ~/.grok/skills/moby-knowledge/SKILL.md.
Grok Build skill folder. name and description are the frontmatter fields in the Grok Build skills guide.
---
name: moby-knowledge
description: Use when researching or trading Solana tokens with Moby in Grok Build. Follow the Moby agent docs and the limits set in the app.
---
Read https://moby.win/agents.md and https://moby.win/marketplace/moby-knowledge/ and follow them. Trade Solana only, funded with USDC, inside the limits set in the Moby app. There are no withdrawals through MCP.Moby Starter Strategies ship with the Moby MCP connector. They are not a separate skill folder. After the server is connected, ask Grok to list Moby's starter strategies and recommend one. Pick a card, or say what to change, before it runs one.
Before a buy, use the rug-check skill. get_token_trade_brief is the one-call pre-buy read.
Example prompts
These prompts stay on Solana. A buy spends USDC only after you say yes. Nothing here promises a result.
Check risk before a buy
Check the risk of this Solana token before I buy it with USDC. Tell me if I should skip it.
Scan smart money
Scan Solana smart-money flows. List tokens tracked wallets are buying. Do not buy anything.
Guarded buy
If this Solana token fits my limits, prepare a buy of 10 USDC. Name the token, the contract, and the amount, and wait for my yes.
FAQ
Can the Grok app add a custom MCP server?
The Grok connector docs say yes. Go to grok.com/connectors, click New Connector, then Custom, and enter the server URL. Those docs say to complete any required authentication. They do not document a field for a static Authorization header. Moby has no sign-in flow. It accepts only that header. Use the xAI API authorization field, or the Grok Build CLI, to send the key.
How does the xAI API send the Moby key?
Put the key, without the word Bearer, in the authorization field of a tool whose type is mcp. The remote MCP docs say that token is set in the Authorization header. The xAI cookbook says it reaches the server as Authorization: Bearer followed by the token. The URL is https://mcp.moby.win/mcp. The placeholder is moby_agent_... POST the request to https://api.x.ai/v1/responses.
Is it safe to let Grok trade?
Limits are set in the Moby app and enforced server-side on every buy. There are no withdrawals through MCP. Crypto is risky. The agent trades Solana only, funded with USDC, and a buy spends real funds.
Manage it from your phone
Set the limits in the Moby app, then come back to Grok. All download options.
More on Moby: agentic trading, all agents, Codex, Claude Code, the Agent Marketplace, the Moby MCP listing, and the rug-check skill.