Connecting Noibu to Grok

Last updated: October 21, 2026

Noibu connects to Grok through two components: the MCP connector (which gives Grok access to live Noibu data) and Skills (which teach Grok how to run Noibu analyses). Both are required for Grok to run a Noibu analysis end-to-end.

Prerequisites

  • A Grok account with access to Connectors (paid SuperGrok / Business / Enterprise typically required for custom MCP connectors)

    • On Grok Business / Enterprise, a team admin may first need to allow the custom server in the admin console to allow team members to connect to Noibu’s MCP

      • Connectors → Other / Custom + URL

  • A Noibu account with valid login credentials (used for the OAuth step)

1. Configure the Noibu MCP connector

Noibu’s MCP server is hosted (not a local command). Use the public URL.

  1. Go to https://grok.com/connectors (or the Connectors / Manage Connectors section inside the Grok app).

  2. Click New Connector → Custom.

  3. Enter the MCP server URL:text

    <https://mcp.noibu.com/mcp>

  4. Save / continue. Grok will discover the tools exposed by the server.

2. Authenticate with Noibu (OAuth)

Noibu’s MCP server uses OAuth (browser login), not a static bearer token.

  • After adding the connector, Grok will prompt you to authenticate (or you can trigger it from the Connectors UI).

  • Approve the login in the browser window that opens.

  • Sign in with your Noibu credentials.

Once complete, the Noibu connector should show as authenticated / connected.

If the browser does not open or authentication fails, double-check that the URL is exactly https://mcp.noibu.com/mcp.

3. Install the Noibu skills

Skills give Grok structured, repeatable workflows (store health, checkout analysis, product analysis, accessibility, etc.). They come from Noibu’s official plugin in Anthropic’s marketplace, and Grok mirrors them straight from the current plugin.

In a Grok chat, paste this prompt:

Fetch the current Noibu plugin from the Anthropic marketplace (https://claude.com/plugins/noibu, source: https://github.com/Noibu/ai-plugin) and mirror every skill in it so it works in Grok. Create the full set of adapted Noibu skills, one for each skill in the plugin. If a Noibu skill already exists, replace it with the latest version from the plugin. Only use the skills from the current plugin, not an older or downloaded copy. When you're done, list every skill you created and confirm the count matches the plugin.

Grok may ask a follow-up question about creating a full set of adapted Noibu skills. If it does, reply in the same chat with:

Create the full set of adapted Noibu skills for Grok

This installs (or creates) the core skills, including:

  • build-business-context

  • checkout-analysis

  • product-analysis

  • querying-noibu-data

  • segment-analysis

  • store-pulse

  • tech-diagnosis

  • accessibility-audit

  • ab-test-opportunity-finder

Tip: After the skills are installed, run the build-business-context skill first for any new store. It creates a business-context file so later analyses are grounded in your specific store instead of generic ecommerce assumptions.

Keeping the skills up to date: When Noibu adds or updates a skill, run the same prompt again. Grok replaces the existing skills with the latest versions and adds any new ones.

Why there’s no skills file to download: Noibu updates its skills in the Claude plugin regularly, so a downloadable copy attached to this guide would soon be out of date. Noibu doesn’t offer a separate Grok plugin today, so the prompt above pulls the skills directly from the current plugin instead. That way you always get the latest version.

4. Test the connection

  1. Start a new conversation (or reload Grok).

  2. Confirm the Noibu connector appears under Connectors and is authenticated.

  3. Test with a simple analysis, for example:

    • “Run store-pulse on yourdomain.com”

    • “How is the store doing in the last 24 hours?”

    • “Run a checkout analysis”

    • “Run an accessibility audit”

Grok should now be able to call Noibu tools and follow the skill workflows.

Optional: Grok Build CLI path

If you use Grok Build (xAI’s terminal coding agent), you can also configure the MCP connector via the CLI or config file.

Add via CLI:

Bash

grok mcp add --transport http noibu <https://mcp.noibu.com/mcp>

Or declare in ~/.grok/config.toml:

toml

[mcp_servers.noibu]
url ="<https://mcp.noibu.com/mcp>"

Then authenticate (Grok will open a browser on first use) and verify with:

Bash

grok mcp list
# or
grok mcp doctor noibu

This path is optional and intended for developers already working in the terminal. Most users should use the web Connectors flow above.

Troubleshooting

  • “Noibu data connection isn’t available” / tools missingYou almost always need to complete (or re-do) the OAuth authentication step for the MCP connector.

  • Custom connectors require a paid planFree-tier Grok accounts generally cannot add custom MCP connectors.

  • OAuth / redirect errorsMake sure the URL is exactly https://mcp.noibu.com/mcp. If a browser window never appears, try authenticating again from the Connectors UI or re-adding the connector.

  • “No bearer token configured”This is expected. Noibu uses OAuth, not a static bearer token.

  • Skills not triggeringConfirm the skills were created successfully via the mirror prompt above and that querying-noibu-data is available (it is the required reference for all Noibu tool calls). Start a new chat after the skills are installed.

  • Business / Enterprise admin lockAn admin may need to pre-approve the custom MCP server URL before individual users can connect it.

Next steps

  • Run the build-business-context skill for your store.

  • Try the other skills: store-pulse, checkout-analysis, product-analysis, segment-analysis, tech-diagnosis, accessibility-audit, etc.

  • Optionally connect GitHub (or other tools) so Grok can turn diagnoses into pull requests or tickets.