> ## Documentation Index
> Fetch the complete documentation index at: https://ara-90a60a07.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Grokbot

> Help Grok Bot connect to Reason using the public MCP endpoint, if its client supports remote MCP and OAuth.

Give your Grok Bot a software engineer. Reason provides a public MCP endpoint for compatible clients. Grok Bot's remote MCP support and a working connection have not yet been verified; check its supported connection methods before starting.

<img src="https://mintcdn.com/ara-90a60a07/456PgXr6TotXinZm/images/integrations/grokbot-connection.webp?fit=max&auto=format&n=456PgXr6TotXinZm&q=85&s=8726dbfe2efbc6a73984f88c8372a652" alt="A bot and Reason connected by a single line." width="1440" height="480" className="rounded-2xl" data-path="images/integrations/grokbot-connection.webp" />

## Connect in three steps

Reason's public MCP URL:

```text wrap theme={null}
https://mcp.reasonmachines.com/mcp
```

<Steps>
  <Step title="Check support and request a connection">
    Ask Grok Bot to check whether its client supports a remote MCP server over Streamable HTTP with OAuth. Copy the request below; do not assume a particular plugin, menu, or invocation is available.
  </Step>

  <Step title="Sign in and approve access">
    If supported, follow the client's connection flow. Complete Reason sign-in yourself, choose the intended workspace, and review the requested permissions before consenting. See [MCP setup](/docs/mcp).
  </Step>

  <Step title="Retrieve a test answer">
    Start a Reason Session with a harmless question and wait for the completed result. A connection or a started Session alone is not a successful test.
  </Step>
</Steps>

```text wrap theme={null}
Help me connect Grok Bot to Reason at https://mcp.reasonmachines.com/mcp if this client supports remote MCP over Streamable HTTP and OAuth. Check its documented capabilities first. Guide me through any sign-in and consent I need to complete; do not ask me to paste credentials into chat. If unsupported, explain what you found without inventing setup commands.
After authentication, start a Reason Session asking: "What is 2 + 2? Do not edit files, run commands, or change any external state." Wait for completion, retrieve the answer, and return the Session link and result. Do not report success until you have retrieved the result.
```

<Note>
  The URL is public, but it does not authorize access. A connection needs authentication and can use only its granted workspace permissions and scopes.
</Note>

## What happens next?

After the test succeeds, you can ask Reason questions about a connected repository or request a small fix. For code changes, ask for tests and a pull request without merging, then review the result and checks. Your repository's branch protection and required approvals still apply.

## More ways to connect

The details below are for an agent helping with setup or for a bot or adapter you control. They do not establish which connection methods Grok Bot supports.

<Tabs>
  <Tab title="For your agent">
    Copy this into your agent. It describes the goal without including any credentials.

    ```text wrap theme={null}
    Check this client's documented support for remote MCP over Streamable HTTP and OAuth before attempting setup. Use https://mcp.reasonmachines.com/mcp and the authentication guidance at https://docs.reasonmachines.com/docs/mcp. Do not guess UI steps, plugin names, or invocation commands.
    For a compatible OAuth client, use dynamic client registration without a client secret. Ask me to complete the browser sign-in, workspace choice, and permission consent. Never ask me to paste an API key or password into chat.
    Call getSelf to confirm the intended workspace and granted scopes. Follow the current tool schemas to createSession with this task: "What is 2 + 2? Do not edit files, run commands, or change any external state."
    Keep the returned Session ID, wait with getSession until it finishes, check its outcome, and retrieve the answer with listSessionMessages. Return the Session link and actual result. Starting a Session is not proof of success.
    If support, authentication, or result retrieval fails, report the exact incomplete step. Do not edit code, merge, or deploy as part of this setup test.
    ```
  </Tab>

  <Tab title="Advanced">
    These options require the corresponding capabilities in a bot or adapter you control; they are not verified Grok Bot setup paths.

    <AccordionGroup>
      <Accordion title="A bot that can run shell commands" icon="terminal">
        Set up [Reason Network](/docs/network) on the trusted computer running your bot. Use `reason network who` to find an agent, then replace the example address below with one from that list.

        ```bash wrap theme={null}
        reason network alice/api-claude "Explain the billing webhook retry policy. Do not change any files."
        ```

        The command waits for the answer. Pass user text as a separate process argument, not interpolated shell code.
      </Accordion>

      <Accordion title="A bot that supports remote MCP" icon="plug">
        Check your bot's documented capabilities first. For a compatible client, use `https://mcp.reasonmachines.com/mcp` with Streamable HTTP and follow [MCP setup](/docs/mcp) for authentication.

        Call `getSelf` to verify workspace access, then `createSession` with the task and intended repository. Keep the returned Session ID, use `getSession` to wait for completion, and check its `outcome`. Read the result with `listSessionMessages`; continue the same Session with `sendSessionMessage`. Follow each tool's current schema.
      </Accordion>

      <Accordion title="A custom HTTP adapter" icon="code">
        Use the [HTTP API](/api-reference/account/verify-credentials) when your bot supports neither option. Your server handles authentication, starts the Session, waits for its outcome, and returns the result. Keep credentials on the server and grant only the workspace access and scopes the integration needs.
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>

See [MCP setup](/docs/mcp) for supported authentication methods and troubleshooting.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.