Setup

Connect your Productised workspace to Claude in under two minutes — sign in once, no keys to manage.

The Claude Connector is hosted at https://mcp.productised.ai/mcp. Setup uses OAuth 2.0 — the same one-click sign-in flow Claude uses for Google Drive, Notion, and GitHub. You sign in to Productised once in a popup, click Authorise, and you're connected. No keys to copy, no config files to edit.

Don't have a Productised account yet? Sign up first at app.productised.ai. It takes 30 seconds — you just need an email. Then come back here to connect Claude.

Connect Claude.ai (browser)

This is the path for most users.

Open Claude.ai → Settings → Connectors

Click Settings in the sidebar, then Connectors, then Add custom connector.

Enter the connection details

Fill in:

Name: Productised
URL: https://mcp.productised.ai/mcp

Leave any API-key field blank. Click Connect.

Claude opens a Productised sign-in popup. If you're already signed in to app.productised.ai in another tab, it'll recognise you and skip straight to the authorise step. Otherwise, enter your Productised email and password.

Authorise Claude

Productised shows what Claude is requesting access to (your workspace — read products, leads, brand, write changes). Click Authorise. The popup closes.

Start a new Claude chat

Open a new conversation. Claude now has access to your 64 Productised tools. Try:

"List my Productised products"

You'll see a 🔧 icon next to the tool call and a structured response. You're connected.

The OAuth token Claude received is automatically refreshed and revocable at any time — see Security & privacy.

Connect Claude Desktop

Claude Desktop uses a JSON config file rather than the in-app connector UI, so the setup is slightly different. Two options — OAuth (recommended) or an API key.

Claude Desktop now supports OAuth-flow MCP servers via its connector picker — exactly like Claude.ai.

Open Claude Desktop → Settings → Connectors

⌘ + , to open Settings, then Connectors in the sidebar, then Add custom connector.

Enter the URL

Name: Productised
URL: https://mcp.productised.ai/mcp

Click Connect.

A browser window opens for Productised sign-in and authorise. Then it redirects back to Claude Desktop, which confirms the connection.

Start chatting

A 🔌 icon in the chat input bar confirms the connection. Open a new conversation — your tools are live.

If you prefer the manual route (older Claude Desktop, scripted setup, headless environments), use an API key in the config file.

Get your API key

In Productised: Settings → API → Keys → Create new key. Name it (e.g. "Claude Desktop") and copy it immediately — it's only shown once.

Edit the config file

In Claude Desktop, Settings (⌘,) → Developer → Edit Config. Paste:

{
  "mcpServers": {
    "productised": {
      "url": "https://mcp.productised.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key you copied. If you already have other MCP servers in the file, add the "productised" block inside the existing "mcpServers" object.

Restart Claude Desktop

Save the file and fully quit Claude Desktop (⌘+Q, not just close the window). Reopen it. The 🔌 icon confirms the connection.

Connect Claude Code / Anthropic API

The same MCP endpoint works with the Anthropic SDK, Claude Code, and any MCP-compatible client. Add to your client's MCP config:

{
  "mcpServers": {
    "productised": {
      "url": "https://mcp.productised.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Get your API key from Productised → Settings → API → Keys. The connector implements the Streamable HTTP transport (the current MCP standard) and is fully compatible with the Anthropic SDK's MCP support.

How the OAuth flow works (background)

You don't need to understand this to use the connector, but if you're curious:

Claude sends an unauthenticated request to https://mcp.productised.ai/mcp
The server responds with 401 Unauthorized and a WWW-Authenticate header pointing to the connector's OAuth metadata
Claude reads the metadata and discovers the Productised authorisation server at https://app.productised.ai/oauth/authorize
Claude opens the authorise URL in a popup, you sign in (if needed) and click Authorise
Productised redirects back to Claude with an authorisation code (PKCE-protected)
Claude exchanges the code for an access token at https://app.productised.ai/oauth/token
Claude uses the access token for every subsequent tool call

Tokens are scoped to your workspace, refreshable, and revocable at any time from Productised Settings → API → Connected apps.

Next: build something

You're connected. Spend two minutes building a real product.

Your first conversation

Six prompts that take roughly 60 seconds each to get a feel for what the connector can do.

Build a product end-to-end

From a sentence to a live AI product — what to say, what Claude does, what you get back.

Troubleshooting setup

The OAuth popup didn't appear / Claude says "couldn't authenticate"

Usually the popup blocker. Allow popups for claude.ai, then click Connect again. If you're still stuck, see Troubleshooting.

I'm signed in to Productised but the connector still asks me to log in

You may be signed in to a different account than the one you want to connect. Sign out of app.productised.ai, sign back in as the right account, then retry the connector flow.

I want to use a different account on the same Claude

Open Settings → Connectors, click ⋯ → Remove on the existing Productised connector, then add it again — the sign-in popup gives you a chance to pick the right account.

My organisation blocks third-party connectors in Claude.ai

If Claude.ai's custom connectors are blocked by your admin, use the Claude Desktop API-key route instead — it doesn't require enabling browser custom connectors.

Was this page helpful?