# Use Impreza with Grok

Source: https://docs.imprezahost.com/use-with-grok.html

The MCP server is `https://mcp.imprezahost.com/mcp`. It speaks Streamable HTTP. The `.onion` address is not for the grok.com connector or for Grok Build. Both require a public HTTPS URL.

What Grok sees in a tool call (server names, domains, and the text a tool returns) reaches xAI.

## Custom connector on grok.com

1. In Connectors, choose Custom.
2. Paste `https://mcp.imprezahost.com/mcp`.
3. Finish the login. Grant only the `read` scope. If Grok asks you to sign in again for a higher scope, decline. The read scope is the restriction.
4. Do not paste an API key. This connector does not take one.

## Grok Build

Add the server:

```
grok mcp add --transport http impreza https://mcp.imprezahost.com/mcp
```

The public Grok Build page documents the client table in `~/.grok/config.toml` as a header plus `url`. It does not document an `allowed_tools` key there. Do not treat that key as the restriction. Paste this table:

```toml
[mcp_servers.impreza]
url = "https://mcp.imprezahost.com/mcp"
```

That page was read on 31 October 2026. It does not document `allowed_tools` in this file. That key appears on the Remote MCP tool of the Responses API, which is a different product.

If your Grok Build version accepts `allowed_tools` inside that table, you may add these six read tools:

`impreza_list_servers`, `impreza_list_apps`, `impreza_list_deployments`, `impreza_privacy_report`, `impreza_list_invoices`, `impreza_topup_status`.

That line is optional. Confirm the tools the client actually shows with `/mcps`.

The restriction that holds is the OAuth `read` scope on the Impreza server. Grant only `read`. The server refuses a tool that asks for a higher scope. A tool that spends balance or opens a charge asks for a higher scope, and `impreza_topup_payment` asks for `manage`.

Authentication is the server's OAuth, the same account login as the grok.com connector. There is no token to paste into the file. A server that requires OAuth opens the browser on first use, and Grok stores the tokens in `~/.grok/mcp_credentials.json`. In the TUI, `/mcps` then `i` starts that login.

## What stays out

These tools spend balance or open a charge. The plugin does not use them, and with the `read` scope the server refuses them:

`impreza_order_vps`, `impreza_upgrade_service`, `impreza_vps_resize`, `impreza_register_domain`, `impreza_topup`, `impreza_topup_payment`, `impreza_pay_invoice`, `impreza_domain_transfer`, `impreza_domain_id_protection`.

## Related

The other assistants use the same hosted server. See [Connect an AI tool](/tutorials/ai-mcp-integration.html).