Tools and spending caps for Grok Bot agents

A Grok Bot connects to Tillpad the same way any client does: the public MCP URL with your tp_ key, or the HTTP API. Tillpad isn't an official Grok Bot partner. For people running Grok Bot agents. Pro is $9 a month. Checked October 2026.

What the key can do

With a tp_ key the Bot can store files and notes, search them, open a receive-only inbox, and run scheduled HTTPS calls. The spending cap is enforced on the Tillpad account and on the key. The client does not raise it.

MCP is https://tillpad.dev/mcp over streamable HTTP. Send Authorization: Bearer and the tp_ key. The server card at /.well-known/mcp/server-card.json lists bearer as the only scheme. OAuth discovery on this host returns 404, so there is no Tillpad OAuth client id to enter.

{
  "url": "https://tillpad.dev/mcp",
  "headers": {
    "Authorization": "Bearer tp_…"
  }
}

What Grok Bot's own docs say

Cursor's Grok Bot security doc says Bots reach remote MCP servers from Cursor's servers, so a private or localhost URL is not enough. Tillpad's MCP URL is public HTTPS (Grok Bot security).

The Grok Bot teams doc says there is no separate Grok Bot connector list. Members find permitted connectors under Connect apps. Admins choose servers on the Team Marketplace from the dashboard Plugins and MCPs page (Grok Bot for teams). If the team turns on Apply to MCP servers, the remote host also has to match the network allowlist. That switch is documented on the security page, and the same page says it is separate from MCP settings for the Cursor editor.

Grok Bot's docs don't yet show where to add a custom server, so we haven't guessed. Use the URL and header in any custom MCP connector you have, or call the HTTP API.

Call the HTTP API

Grok Bot's overview says each Bot has a terminal on its cloud computer (Grok Bot). Try these requests. Replace tp_… with a real key from an active Pro account.

curl -s -H "Authorization: Bearer tp_…" "https://tillpad.dev/api/budget"

curl -s -X PUT "https://tillpad.dev/api/memory/facts/preference" \
  -H "Authorization: Bearer tp_…" \
  -H "Content-Type: application/json" \
  -d '{"value":"Prefers email before noon."}'

Other clients

The same URL and key are documented for Claude, ChatGPT, Cursor, and LangChain. Editor mcp.json configures Cursor, not Grok Bot.

Questions people ask

Is Tillpad an official Grok Bot integration?

No. There is no partnership and no Tillpad-built Grok Bot plugin. You connect the public MCP server or call the HTTP API with a Tillpad key.

Does the spending cap change because the caller is a Grok Bot?

No. The cap is on the Tillpad account and the API key. get_usage and GET /api/budget report the same numbers for every client.