Connecting Noibu to Perplexity Computer

Last updated: October 21, 2026

This guide is for Perplexity org admins. Follow it once to make Noibu available to everyone in your Perplexity organization. By the end, the Noibu connector and the Noibu skills will be added to your org, and your team will have the steps to add them to their own accounts.

Noibu connects to Perplexity through two components: the Noibu connector (MCP) gives Perplexity access to live Noibu data, and the Noibu skills teach Perplexity how to run Noibu analyses. The admin sets up both.

How the rollout works

The rollout has two separate layers, and both need to be done:

  1. Admin (once, for the whole org). Adds the Noibu connector and the 9 Noibu skills to the org.

  2. Each member (once, takes a minute). Clicks + on the Noibu connector and signs in with their Noibu login, then clicks + on each of the 9 Noibu skills under Organization skills.

Admin setup makes the connector and skills available to the org. Nothing is added to a member's account until they click +. Step 3 has the member steps to share with your team.

Important: Noibu skills only run inside a Perplexity Computer task. A regular Perplexity Search thread can't run skills, and calls to the Noibu connector there can fail with "Something went wrong." Ask your team to start a Computer task whenever they want a Noibu analysis.

Before you start

You'll need:

  • A Perplexity Enterprise org with access to Computer.

  • An admin role that includes Connector permissions (to add org-scoped connectors) and Manage organization skills. Check both in org settings under People → Roles & Permissions.

  • A Noibu account with valid login credentials, used to test the connector.

Step 1: Add the Noibu connector for the whole org

Noibu's MCP server is hosted, so there's nothing to install locally.

  1. Open your Perplexity org settings. In the left sidebar, under Customize, click Connectors. It is not under the Organization tab itself.

  2. Click + Custom connector (top right) and choose Remote.

  3. Fill in the form:

    • Name: Noibu

    • MCP Server URL: https://mcp.noibu.com/mcp

    • Authentication: OAuth. Leave Client ID and Client Secret blank.

    • Transport: Streamable HTTP

    • Network access: Public

  4. Tick I understand custom connectors can introduce risks and click Add.

  5. Click the Noibu connector and sign in with your Noibu login to confirm it works.

  6. Share it with the organization and choose to have each member sign in themselves. Each person then only sees the Noibu domains their own Noibu account already has access to.

  7. Confirm Noibu appears in the Access list on this page. It may take a little while to show up for members.

Important: Add the connector from org settings, not from your personal Settings → Connectors. A connector you add personally is private to you and won't appear in the org Access list.

Step 2: Add the Noibu skills for the whole org

Skills give Perplexity structured, repeatable workflows, like store health checks, checkout analysis, product analysis, accessibility audits and A/B test ideas. They come from Noibu's official plugin in Anthropic's marketplace. Perplexity Computer pulls them straight from the current plugin, adapts them to run on Computer, and saves them to your org.

The plugin currently has 9 skills. Check that all 9 end up under Organization skills.

  1. Start a new Perplexity Computer task and paste:

Fetch the current Noibu plugin from the Anthropic marketplace (https://claude.com/plugins/noibu, source: https://github.com/Noibu/ai-plugin) and mirror its skills into my organization's skill library. Adapt every skill in the plugin to run on Perplexity Computer and save each one directly at org scope, not to my personal skills. If a Noibu skill is already in the org library, 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 saved and confirm the count matches the plugin.

  1. Check that Computer reports 9 skills saved to the organization.

  2. If a skill couldn't be saved because one with the same name already exists, delete the old copy (personal or org) on the Skills page and ask Computer to save that skill again. A skill saved to your personal Skills page (or My Skills) only goes to your account, and a personal copy with the same name can block the org copy.

Once saved, these 9 skills appear for every member on the Computer Skills page under Organization skills, with a + next to each:

  • querying-noibu-data (the required reference for every Noibu call)

  • build-business-context

  • store-pulse

  • checkout-analysis

  • product-analysis

  • segment-analysis

  • tech-diagnosis

  • accessibility-audit

  • ab-test-opportunity-finder

Keeping the skills up to date

When Noibu adds or updates a skill, run the same prompt again. Computer replaces the existing skills with the latest versions and adds any new one, which appears under Organization skills as soon as it's saved. Let your team know to click + on the new skill.

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 Perplexity plugin today, so the prompt above pulls the skills directly from the current plugin instead. That way your org always gets the latest version.

Step 3: Share the member steps with your team

Admin setup makes Noibu available, but nothing is added to a member's account until they click +. Share these steps with your team. Each member only does this once.

Add the Noibu connector

  1. In Perplexity, go to Settings → Connectors.

  2. Search for Noibu.

  3. Click + (or Add) on the Noibu connector.

  4. Sign in with your Noibu login in the window that opens and approve access.

Noibu now shows as connected. You'll only see the Noibu stores your Noibu account already has access to.

Add the 9 Noibu skills

  1. Open Perplexity Computer and go to the Skills page.

  2. Click the Organization skills tab.

  3. Click + on each of the 9 Noibu skills.

  4. Each + turns into a ✓ once the skill is added. Check the Installed skills tab: all 9 should be there. Don't skip querying-noibu-data, since every other Noibu skill relies on it.

Run a skill with /

  1. Start a new Perplexity Computer task.

  2. In the message box, type / followed by the skill name, then add your store domain and question. Typing / opens a list of your installed skills, so you can pick one instead of typing the full name.

  3. Send the message. Computer runs that skill directly.

Examples (use your exact Noibu domain):

  • /store-pulse www.yourstore.com

  • /tech-diagnosis www.yourstore.com give me the top opportunities

  • /checkout-analysis www.yourstore.com where are shoppers dropping off?

  • /ab-test-opportunity-finder www.yourstore.com

  • /build-business-context www.yourstore.com (run this first for each new store)

Plain questions such as "How is my store doing today?" also work, since Computer picks a matching skill on its own. Using / is the most reliable way to run a specific skill.

Step 4: Verify the rollout

  1. In org settings, check that Noibu is in the connector Access list and all 9 Noibu skills are listed under Customize → Skills → Organization skills.

  2. Do the member steps yourself (Step 3), then start a new Perplexity Computer task and run a quick test with your exact Noibu domain, for example /store-pulse www.yourstore.com.

  3. The answer should use live Noibu data. If it does, the org is set up.

Run the build-business-context skill once for each store. It saves a business context profile to Noibu, so later analyses are grounded in that store instead of generic ecommerce assumptions.

Optional: Let Noibu skills open GitHub pull requests

Skills like tech-diagnosis and accessibility-audit can push a fix branch and open a pull request. Computer always shows you the branch, files and title and waits for your confirmation. It never merges.

If your GitHub org has OAuth app restrictions: Perplexity connects to GitHub as an OAuth App, so it can't reach a restricted org's private repositories until a GitHub org owner approves it. This is different from Claude's GitHub connector, which is a GitHub App installed on the org.

  1. On GitHub, go to Settings → Applications → Authorized OAuth Apps → Perplexity.

  2. Under Organization access, click Request next to the org.

  3. A GitHub org owner approves it under the org's Settings → Third-party access → OAuth app policy.

Approval is org-wide, not per repository. To limit Perplexity to one repository, the org must allow fine-grained personal access tokens scoped to that repository, with Contents and Pull requests set to read and write.

Troubleshooting

  • Skills don't run, or you see "Something went wrong". The request was run in a regular Search thread. Start a Perplexity Computer task instead.

  • "[API_CLIENTS_ERROR] Only organization admins can create org-scoped connectors", even though you're an admin. Check that your role has the connector permissions under People → Roles & Permissions, then sign out and back in, or ask another admin to try. If none of these work, contact Perplexity support.

  • Fewer than 9 Noibu skills under Organization skills. Run the Step 2 prompt again. If a skill was saved to someone's personal Skills page, delete that copy first.

  • Skills exist but don't trigger. The member probably hasn't clicked + on them. Have them open Skills → Organization skills, click + on any Noibu skill without a ✓, and check all 9 (including querying-noibu-data) are under Installed skills. Also make sure they're in a Perplexity Computer task, and run the skill directly with /.

  • Noibu can't find the store. Use the exact domain registered in Noibu, for example www.carsncards.com, not carsandcards.com. Noibu doesn't auto-correct typos.

  • The Noibu connector is missing for members. Make sure it was added from org settings (Step 1) and appears in the Access list. It may take a little while to show up.

  • A member sees "Noibu data connection isn't available". That member hasn't connected Noibu yet. Have them follow the member steps to add the Noibu connector (Step 3).

  • GitHub returns "Could not resolve to a Repository" or a 403 on an org repository. The GitHub org has OAuth app restrictions. See the optional GitHub section above.

  • Live page checks fail. If the storefront is password-protected, Computer's browser can't open product pages. The analysis falls back to Noibu data and the theme code.

Perplexity reference documentation

If you run into issues not covered in this guide, reach out to your Noibu contact or email support@noibu.com.