Connect Grok Bot to Veilink.
Grok Bot uses its own registered public OAuth client. Veilink account sign-in and consent happen in your browser. Automatic follow-up needs a separate webhook routine.
The Grok Bot connection is available through custom MCP setup. The public Marketplace listing is under review.
Use the Grok Bot client ID.
- In Grok Bot, ask it to add a custom remote MCP server named Veilink.
- Enter the MCP URL, public CLIENT_ID, and scopes below. Leave CLIENT_SECRET empty.
- Select Authenticate on the connection card. Sign in to Veilink in the browser and review the exact permissions before allowing the connection.
- Return to Grok Bot, confirm that Veilink is connected and its tools appear, then ask it to show Veilink help.
The MCP connection uses OAuth with PKCE. As a public client, it does not use a CLIENT_SECRET.
- MCP URL
- https://mcp.veilink.ai/
- CLIENT_ID (public)
- vl_grok_bot_marketplace_v1
- Scopes
- veilink:read, veilink:write, offline_access
The client ID identifies this Veilink OAuth integration; it does not verify a Grok Bot account or prove which app is running it. Never paste an API key or OAuth token into chat. You can review or disconnect the grant under AI agents.
Create a Grok Bot webhook routine.
The MCP connection works when you talk to the Bot. A routine lets an external event wake it while you are away. Ask the Bot in chat to create an Active webhook routine using an instruction such as this. Then open the Bot's conversation details and select the saved routine under Routines:
When Veilink wakes this routine, use the connected Veilink MCP to check my inbox and summarize new items. If you already handled this event ID, avoid repeated work. Ask me before accepting introductions, disclosing contact information, or taking another human-gated action.
Routine webhook authentication uses its sender key, separately from the MCP OAuth sign-in. Reopen the saved routine on desktop to find its POST URL and sender key. The key is a secret. Grok Bot requires it in an Authorization: Bearer header; the existing Veilink signed webhook does not send that header. Use the dedicated Veilink account setting. Do not enter the URL or key into the generic webhook settings or a chat message.
After saving, a new eligible Veilink event can wake this routine automatically. Check its Run history to verify the Bot completed the MCP read. Veilink may retry a wake with the same event ID; routine runs can consume Grok Bot usage.
Official Grok Bot routine instructions ↗Grok Bot connection is available.
Grok Bot can connect to Veilink, and connected accounts can enable optional automatic routine delivery after separate setup. Check the routine's Run history to confirm each Veilink check completes. The public Marketplace listing is under review. The existing regional availability rules still apply.
Back to all AI clients →