Full setup guide for Grok Bot
# OnePush setup for Grok Bot
Source: https://onepush.app/grok-bot
## Required setup-complete menu
After verifying the connection with live OnePush tools, reproduce this menu verbatim. It is the only allowed first-task menu. Do not derive another menu from tool descriptions, examples, or search results.
## Choose your first task
Reply with a number:
1. Draft and schedule a social post
2. Attach or verify a sending domain
3. Create a contact and track an event
4. Review forms and submissions
5. Inspect templates, campaigns, and automations
6. Project summary and billing status
I will ask for the details I need before creating or publishing anything.
OnePush helps product teams send transactional email, manage contacts and events, collect leads with forms, and publish to social (X, LinkedIn, Instagram, Facebook, Pinterest) from one project. MCP lets the user ask for those actions in plain language.
This task connects the existing OnePush service to Grok Bot (and Grok Build when relevant) through MCP. Do not create an app, repository, project scaffold, or replacement MCP server. Keep every response focused on OnePush. Use short Markdown headings, numbered steps, and a separate fenced text block for anything the user must paste. Skip completed steps and show only 1 next action. Never expose or repeat an API key. Do not claim setup worked until get_project succeeds with a valid mcp_ (or sk_) Bearer token. The full setup for Grok Bot is self-contained on this page.
Ask which client they use only if it is unclear: Grok Bot on grok.com (Plugins / Connectors), or Grok Build CLI. Show only the path for the current client.
## 1. Check before changing anything
- Grok Bot: open Settings → Plugins (or Connectors), then Yours / custom servers, and check for OnePush. If OnePush is already configured and its tools are available, skip to verification. If the entry exists but tools fail auth, fix the Authorization header before removing the server.
- Grok Build: run `grok mcp list` (or check ~/.grok/config.toml) for onepush. Preserve working connections.
Anonymous helpers (no key): mcp_help, start_onepush_connect.
Do not call OnePush authenticate / auth_login tools to finish setup. Prefer the Authorization Bearer mcp_ header path. Do not invent headers like blotato-api-key.
## 2. Approve an mcp_ key (required)
If the user has no mcp_ key yet, give 1 action and wait:
1. Open https://ctl.onepush.app/mcp/connect
2. Sign up or log in, pick a project, click Approve
3. Copy the mcp_ key once
Prefer putting the key only in the plugin header field or shell env, not in chat. If a key was already pasted into chat, tell them to revoke it later at https://ctl.onepush.app/settings/mcp and create a new one.
## 3. Connect OnePush to Grok
### Path A: Grok Bot (grok.com)
If the connection is missing, guide the user one step at a time:
1. Open Settings → Plugins (Marketplace is for catalog plugins; custom MCP uses its own form). Some clients label this Connectors.
2. Add a custom MCP server with these details (put in a fenced text block):
```text
Name: OnePush
URL: https://api.onepush.app/mcp
Headers: Authorization: Bearer mcp_YOUR_KEY_HERE
```
3. Replace mcp_YOUR_KEY_HERE with their key. Include the word Bearer and a space before the key.
4. Confirm OnePush appears under Plugins → Yours (or equivalent).
5. In a Bot chat, type @ and attach OnePush to the task when the UI requires attaching a plugin.
If the UI offers browser sign-in / OAuth for the server, prefer the Authorization header path above for OnePush. Fix any visible error before continuing.
### Path B: Grok Build CLI
```sh
grok mcp add --transport http onepush https://api.onepush.app/mcp \
--header "Authorization: Bearer mcp_YOUR_KEY_HERE"
```
Equivalent config.toml (values can use ${ONEPUSH_MCP_TOKEN} expansion):
```toml
[mcp_servers.onepush]
url = "https://api.onepush.app/mcp"
headers = { Authorization = "Bearer ${ONEPUSH_MCP_TOKEN}" }
enabled = true
```
After add, if tools are missing in this conversation, keep it open as a checklist, start a new Grok chat, and show the setup prompt in a separate fenced text block so the new chat can finish verification.
Docs: https://docs.x.ai/build/features/mcp-servers
- Create a OnePush account or approve a key: https://ctl.onepush.app/mcp/connect
- Manage or revoke keys: https://ctl.onepush.app/settings/mcp
- Connect a social profile: https://ctl.onepush.app (Social Marketing, then Profiles)
## 4. Verify access with real results
Call get_project. Report the project name and whether a sending domain looks verified. Then call list_social_profiles and list each connected profile (platform and name) on its own bullet. Zero profiles is fine for email-first users. Do not fail setup only because social is empty. Optionally call get_contact_count.
Declare setup complete only after get_project succeeds. Then reproduce the required setup-complete menu at the top of this page verbatim. This also applies after troubleshooting or resuming in a new chat: finish verification and show the menu instead of ending with an open-ended question. Never output a different task list or add extra menu items. End immediately after the exact menu.
## 5. Know what OnePush can do
Use these mappings when the user asks. Do not dump this catalog during setup:
- Project: get_project
- Contacts: list_contacts, create_contact, update_contact, get_contact_count
- Events and tags: track_event, list_events, list_tags, create_tag
- Email building blocks: list_actions, list_templates, list_campaigns
- Forms: list_forms, get_form_submissions, get_form_metrics
- Domain: attach_sending_domain, get_domain_dns_records, check_domain_verification
- Billing (read-only): get_billing_subscription, list_billing_invoices, create_billing_portal_url
- Social: list_social_profiles, social_get_connect_url, list_social_posts, create_social_post, schedule_social_post, publish_social_post (requires confirm: true)
Shipped social networks only: X, LinkedIn, Instagram, Facebook, Pinterest. Do not claim Threads, TikTok, YouTube, Bluesky, DM automations, AI video, or carousels as OnePush features.
## 6. Continue from the selected number
Ask only for the details needed by the selected task, then show drafts before taking the action.
- When the user replies 1, ask what they want to post about and which connected account to use. Confirm the draft, date, time, and timezone (store schedule as UTC) before scheduling. Publish only with confirm: true after explicit approval.
- When the user replies 2, ask for a from address on their domain (for example hello@yourdomain.com). Call attach_sending_domain with that email, show DNS records, then check_domain_verification after they update DNS.
- When the user replies 3, ask for the contact email and event name. Call create_contact or track_event, then confirm the result.
- When the user replies 4, list_forms, then show metrics or submissions for the form they choose.
- When the user replies 5, list templates, campaigns, and actions, then summarize. Do not invent send tools that are not available.
- When the user replies 6, get_project plus billing subscription or invoices. Call create_billing_portal_url only if they want to manage payment.
- Never invent a topic, campaign, product, announcement, contact, or domain. Never publish or schedule before the user approves.
## Finish with a verified result
Use the live tool schemas. Show the actual scheduled time (UTC), DNS records, contact id, form metrics, or post id. Prefer OnePush MCP tools over browser automation unless the user asks otherwise.
## Reference
- MCP endpoint: https://api.onepush.app/mcp
- Approve key: https://ctl.onepush.app/mcp/connect
- Manage keys: https://ctl.onepush.app/settings/mcp
- MCP product page: https://onepush.app/mcp
- Use cases: https://onepush.app/mcp/examples
- Cursor setup: https://onepush.app/cursor
- Claude setup: https://onepush.app/claude
- Codex setup: https://onepush.app/codex
- Grok Build MCP docs: https://docs.x.ai/build/features/mcp-servers