[See what's new in the

Kick Changelog](/content/changelog/index.html)

For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). This page is also available as [Markdown](https://docs.kick.co/ai/mcp/connectors/connect-perplexity.md).

#### What You'll Need

- A Perplexity Pro or Enterprise account
- A Kick account with access to at least one workspace

**Tip**: Log in to your Kick account in your browser before starting. This makes the authorization step faster.

#### Connect Perplexity to Kick

Perplexity supports custom remote connectors in supported plans.

**Step 1: Open Connectors Settings**

1. Open **Account settings**  
2. Go to **Connectors**  
3. Click **\+ Custom connector**

**Step 2: Configure the Kick Connector**

1. Choose **Remote** if asked for a connector type  
2. Enter `Kick` as the name  
3. Enter the Kick MCP URL: `https://use.kick.co/mcp`  
4. Set **Transport** to **Streamable HTTP**  
5. Choose authentication method:  
   - **OAuth** — Recommended for standard Kick login  
   - **API Key** — For token-based authentication  
   - **None** — For read-only public access (rarely used)  
6. Review the custom connector risk acknowledgement  
7. Click **Add**

**Step 3: Authorize the Connection**

1. Click the **Kick connector card** to authorize it  
2. Sign in to your Kick account if prompted  
3. Choose your permissions and workspace access  
4. Click **Authorize**

**Step 4: Enable Kick in a Conversation**

Once authorized, enable Kick before using it in a conversation.

1. Start a new conversation in Perplexity  
2. Enable the connector from the prompt or tools area  
3. The Kick connector should appear as available

#### Verify Your Connection

Test that everything is working by starting a conversation with Kick enabled and asking:

```
List the Kick tools you can use and confirm the active workspace.
```

Perplexity should respond with available tools (like `transactions_query`, `reports_query`, `context_browse`) and your active workspace name.

#### Troubleshooting

**Can't Add Custom Connectors**  
**Admin-controlled**: Organization admins may control whether members can add custom connectors.

**Solution**: Contact your organization admin and ask them to enable custom connectors or add Kick MCP for your organization.

**Authorization Failed**  
The authorization didn't complete successfully.

1. Go to Account settings → Connectors  
2. Remove the Kick connector  
3. Add it again and complete the authorization flow  
4. Make sure you click **Authorize** on the Kick authorization page

**Wrong Workspace Showing**  
Your Kick account has access to multiple workspaces. Tell Perplexity which workspace you want to use:

```
Please switch to the [workspace name] workspace.
```

#### **Data Privacy and Security**

- **Your data stays in Kick**: Perplexity requests data through the MCP connection but doesn't store your Kick data permanently
- **Workspace permissions apply**: Perplexity can only access workspaces you already have permission to view in Kick
- **You control access**: You can disconnect Kick at any time from the Connectors settings
- **Confirmation required for changes**: Write operations require your explicit approval before execution

#### Next Steps

Now that you're connected:

1. Try a sample query: "List my workspaces" or "What tools can you use?"
2. Ask complex financial questions and get cited, verified answers from your Kick data
3. Check out the [Kick MCP Use Case Library](https://docs.kick.co/ai/mcp/mcp-use-case-library) for advanced use cases

Last updated 18 days ago