Grok Bot: connection and validation
Validation pending · Reviewed 2026-11-17
Hosted always-on assistant that reaches remote MCP servers through its custom connector screen: a Remote HTTPS server URL plus HTTP headers or an OAuth client. The connector path follows vendor documentation dated 2026-11-17 and is not live-verified by Praesidia.
Connect Grok Bot through its hosted connector
Create a workspace for Grok Bot Open Grok Bot setup · Start with the free sample
- Create your free workspace and verify your email. On the dashboard, run the local allow/block sample and inspect the saved audit and actual signing status. This requires no model or external target; it does not connect a client or create independently verified proof.
- Return to your saved Grok Bot setup and create its
managed-mcpinstallation. The setup page shows the Praesidia MCP server URL and a nonsecret environment file; nothing is installed on a host. Configuration starts read-only. - In Grok Bot open Connect apps, choose Add a custom connector, set Type to Remote HTTPS and paste the Praesidia MCP server URL. Add an HTTP header
Authorization: Bearerwith the creator’s scoped API key from the vendor’s secret field, or supply a registered OAuth client ID and secret, then choose Add plugin. Enterprise workspaces need an administrator to allow the connector under Plugins & MCPs. - Load the creator’s scoped API credential only in the vendor’s secret or header field, never in a prompt or shared workflow. Run the one-use connection challenge from any shell with the same credential. Recorded credential proof does not attest a target effect.
- Make one harmless managed call from the assistant and inspect the server-returned action bound to this installation. A connector that shows the tools is not execution evidence.
The connector path follows the vendor’s public documentation as of 2026-11-17; Praesidia has not run a live acceptance against it. Tool calls transit the vendor’s hosted backend under the vendor’s terms and region. Free setup remains available; registered protected HTTP execution requires Enterprise approval workflows, enabled proof.actions, and the appropriate role and scopes. Advanced proof reads are a separate entitlement. Payments are currently unavailable. Provider usage may have separate charges.
Connection acceptance comes before a coverage claim
This distribution profile is separate from native runtime enforcement. Check the exact client version, transport, authentication, and tool surface with the operator. No marketplace listing or automatic interception is implied.
No tested installation recipe is recorded for this profile yet. Use the checklist below to prepare an evaluation; do not infer compatibility from an MCP label alone.
- Configure a dedicated test connection with minimum scopes. Never paste a runtime secret into a public workflow or repository.
- Discover the tools and allow only the intended tool set. Confirm the exact transport supported by your installed client.
- Make one harmless managed call. Check denial and revoked credentials; a client that continues after a failed policy hook does not enforce that hook.
- Inspect the action ID in Praesidia. Report whether the test covered a managed call, native interception, or observation only.
- Only the explicit Praesidia MCP tools exposed over the connector are governed; native tools of the assistant and other connectors stay outside this boundary.
- Connector path per vendor documentation as of 2026-11-17; no Praesidia acceptance run exists yet, so no evidence grade is claimed.
- Needs a public HTTPS MCP endpoint. Teams plans enable custom connectors by default; Enterprise needs an administrator to allow them in the Plugins & MCPs policy.
- The vendor publishes no data-residency statement for connector traffic; tool calls transit the vendor's connector backend.
- One connector carries one creator credential. The assistant's chat identity does not establish a separate delegated Praesidia user.