Grok

Connect

Grok supports custom MCP connectors, and Nimply's MCP server works with them out of the box:

1. Go to grok.com/connectors.
2. Click New Connector → Custom.
3. Enter the server URL:

   https://mcp.nimply.io/mcp

4. Complete the authentication step — you'll be redirected to Nimply to log in, pick a workspace, and approve permissions (standard OAuth, nothing to copy).

Once connected, the Nimply tools are available in your Grok conversations alongside the built-in connectors.

For Grok Business and Enterprise, a team admin must provision the connector first before members can use it.

Grok Build plugin

For the Grok Build CLI there is an official Nimply plugin (github.com/nimply/grok-plugin) that bundles the MCP server with a skill teaching Grok the Nimply workflow. It is submitted to the xAI plugin marketplace; once listed, install it with:

grok plugin install nimply --trust

Until then, clone the repo and load it directly:

git clone https://github.com/nimply/grok-plugin.git
grok --plugin-dir ./grok-plugin

On first use Grok opens Nimply's authorization page (or press i on the server in the /mcps modal). Sign in, choose a workspace, approve the permissions.

Grok API & Grok Build (manual)

xAI also supports remote MCP tools in its API (native SDK, OpenAI-compatible Responses API, and the Voice Agent API) and in the Grok Build CLI. Point them at the same server URL with an API-key header (Authorization: Bearer nim_live_..., created in Nimply → Settings → Developers) — the pattern in Any MCP client applies unchanged.

Try it

• "List my Nimply channels and draft a post announcing tomorrow's livestream for each."
• "How did last week's posts perform? Queue a follow-up on the best one."

Troubleshooting

• Connector fails to add — the server must be reachable from the internet; https://mcp.nimply.io/mcp is public, so double-check the URL was entered exactly (including the /mcp path).
• Authentication loop — make sure you complete the workspace selection step in the Nimply consent screen; the connector is scoped to that one workspace.
• Tools missing on a team plan — Business/Enterprise workspaces need an admin to provision the connector before it appears for members.