# Connect custom AI tools

#### What You'll Need

* An MCP-compatible AI tool or IDE
* A Kick account with access to at least one workspace

#### Standard Connection Details

Use these values when configuring Kick MCP in any compatible client:

| Field              | Value                                                                   |
| ------------------ | ----------------------------------------------------------------------- |
| **Name**           | `Kick`                                                                  |
| **MCP server URL** | `https://use.kick.co/mcp`                                               |
| **Transport**      | Streamable HTTP, HTTP, or Remote MCP, depending on the client's wording |
| **Authentication** | OAuth when available, otherwise API key or bearer token                 |
| **Bearer header**  | `Authorization: Bearer kick_pat_...`                                    |

***

#### Connection Steps

The exact steps vary by client, but the general pattern is:

**Step 1: Find MCP or Connector Settings**

Look for settings related to:

* MCP servers
* Custom connectors
* Remote servers
* Tools or integrations

Common locations:

* Settings → Connectors
* Settings → Tools & MCP
* Settings → Integrations
* Preferences → Extensions

**Step 2: Add the Kick Server**

1. Click **Add server**, **Add connector**, or similar
2. Enter the connection details from the table above
3. Choose **OAuth** for authentication if available
4. Save or add the configuration

**Step 3: Authorize (OAuth) or Add Token**

**If using OAuth:**

1. A browser window will open to Kick's authorization page
2. Sign in to your Kick account if prompted
3. Choose your permissions and workspace access
4. Click **Authorize**

**If using bearer token:**

1. Generate a personal access token in Kick (Settings → API)
2. Copy the token (it starts with `kick_pat_`)
3. Paste it in the authentication field in your MCP client

**Step 4: Restart or Reconnect**

After adding the server:

1. Restart the client application, or
2. Reconnect to reload the MCP server list

***

#### Verify Your Connection

Test that everything is working by asking your MCP client:

```
List the Kick tools you can use. Identify which ones are read-only, then confirm the active workspace before looking up any client data.
```

The client should respond with:

* A list of available Kick tools (like `transactions_find`, `reports_profit_loss_get`, `workspaces_list`)
* Confirmation of which tools are read-only
* The name of your active workspace

***

#### Common Authentication Methods

**OAuth (Recommended)**

OAuth automatically handles authorization through your browser. Most modern MCP clients support this method.

**Advantages:**

* No manual token management
* Automatic token refresh
* Easier revocation

**When to use:** Choose OAuth if your client supports it.

**Bearer Token / API Key**

Bearer tokens are personal access tokens generated in Kick and manually added to your MCP client.

**Advantages:**

* Works in clients without OAuth support
* More granular access control
* Useful for automation

**When to use:** Choose bearer token if OAuth isn't available or you need token-based authentication.

To generate a bearer token:

1. Log in to Kick
2. Go to Settings → API
3. Click **Generate MCP token**
4. Copy the token (starts with `kick_pat_`)
5. Store it securely — it won't be shown again

***

#### Troubleshooting

**Connection Failed or No Tools Showing**

The server configuration didn't load successfully.

1. Verify the MCP server URL is exactly: `https://use.kick.co/mcp`
2. Check that authentication is configured correctly
3. Restart or reconnect the client
4. Check client documentation for MCP-specific requirements

**Authorization Failed (OAuth)**

The authorization didn't complete successfully.

1. Make sure you're logged in to your Kick account
2. Complete the full authorization flow
3. Click **Authorize** on the Kick authorization page
4. Try disconnecting and reconnecting the server

**Invalid Token (Bearer Token)**

The personal access token isn't working.

1. Verify the token was copied correctly (no extra spaces)
2. Check that the token hasn't expired in Kick settings
3. Generate a new token if needed
4. Make sure the bearer header format is: `Authorization: Bearer kick_pat_...`

**Wrong Workspace Showing**

Your Kick account has access to multiple workspaces. Tell the client which workspace you want to use:

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

***

#### Next Steps

Now that you're connected:

1. Try a sample query: "List my workspaces" or "What tools can you use?"
2. Explore reports by asking Claude to generate financial reports for your clients
3. Check out the [Kick MCP Use Case Library](/developers/kick-mcp/mcp-use-case-library.md) for advanced use cases


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kick.co/developers/kick-mcp/connectors/connect-custom-ai-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.