ProvelyGrok connects to Provely through the MCP server, the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. Grok never holds the verifier credentials.
A person verified the Grok capabilities on 2026-09-08. Agent products change monthly. Re-verify before you build.
Source: integration profile grok · retrieved 2026-09-08
Which surfaces does Grok use?
| Surface | Support | Detail |
|---|---|---|
| MCP server | Supported | transport http |
| CLI | Supported | Runs through the shell tool of the agent. |
| SDK | Not supported | |
| REST API | Supported | Any HTTP call reaches the control plane. |
Which guidance files does Grok read?
Provely ships one Agent Skill for this host, so the agent knows to verify an outcome before it claims done. The renderer writes prompt fragment, tool schemas from one source. A new agent needs a profile, not core code.
Explain: each file, its path and its write mode
| Format | Path | Mode |
|---|---|---|
| prompt fragment | provely/prompt-fragment.md | fragment |
| tool schemas | provely/tool-schemas.json | fragment |
| CI gate workflow | .provely/ci/github-actions.yml | fragment |
How is a false completion claim blocked?
Guidance asks. A hook and the CI gate enforce. A host with neither still receives the verdict, and a person reads it before the work ships.
Explain: what each control does on this host
| Enforcement | Support | Detail |
|---|---|---|
| Advisory guidance | Supported | The instruction files state the rules for every agent. |
| Lifecycle hooks | Verify at implementation | No hook events stated. |
| CI gate | Supported | provely verify --wait fails the pipeline unless the verdict is VERIFIED. |
How do I connect Grok?
Connect Grok to Provely
- Install the CLI.Run
curl -fsSL https://provely.sh/install.sh | sh. On Windows, runirm https://provely.sh/install.ps1 | iex. Each script verifies the signed checksum before it installs the binary. - Register the MCP server.Add the Provely server. Use
provely mcpfor stdio, or the hosted HTTP server with a bearer token. The tools arebegin,verify,status, andreceipt. - Write the guidance files.Run
provely init --agent grok. It writesprovely/prompt-fragment.md(fragment),provely/tool-schemas.json(fragment),.provely/ci/github-actions.yml(fragment). The guidance carries one rule: a successful tool call is not completion. - Add the CI gate.Run
provely verify --wait <duration>in the pipeline. The step fails unless the verdict is VERIFIED. Exit codes: 0 VERIFIED, 2 PENDING, 3 FAILED, 4 CONTRADICTED, 5 UNVERIFIABLE, 1 error. - Report the verdict exactly as returned.VERIFIED: "The action is verified complete. Receipt: <id>." PENDING: "The action is accepted but not yet verified. Operation: <id>."
What else does the profile state?
- Verified 2026-09-08: the xAI API takes a remote MCP server as a tool: type "mcp", server_url, server_label, allowed_tools, authorization, and headers. The authorization value sets the Authorization header. Source: https://docs.x.ai/developers/tools/remote-mcp.
- Point the xAI API at the hosted MCP server https://api.provely.sh/mcp. The transport is HTTP, so this profile names no stdio transport for the API surface. A stdio host that embeds Grok runs
provely mcpunchanged. - Verified 2026-09-08: xAI function calling takes name, description, and parameters. Source: https://docs.x.ai/docs/guides/function-calling. The docs show the flat form. The rendered file uses the nested form of the OpenAI-compatible endpoint. Flatten each entry for the flat form.
- Verified 2026-09-08: xAI publishes the coding CLI Grok Build. Source: https://docs.x.ai/build/overview. The guidance file name and the hook events of Grok Build are not documented. The pages /build/hooks and /build/mcp-servers return 404. Do not guess them.
- Append the prompt fragment to the system prompt. Where no MCP host exists, call the CLI through the shell tool.
Grok keeps its action credentials, and no surface returns the verifier credentials to it. Read the credential boundary. An operation outlives the session that opened it. Read the API reference.
Which host versions does the profile cover?
>=1.0.0. The integrations team last verified the profile with xai-sdk 1.19.0 of 2026-08-18 on 2026-09-08 (PyPI); docs.x.ai reachable.