connect cursor.md
Connect Cursor
What You'll Need
- Cursor IDE installed
- A Kick account with access to at least one workspace
{% hint style="info" %} Tip: Log in to your Kick account in your browser before starting. This makes the authorization step faster. {% endhint %}
Connect your account
Cursor supports remote MCP servers through its Tools & MCP settings.
Step 1: Open MCP Settings
- Open Cursor Settings
- Go to Tools & MCP
- Click Add new MCP server
Step 2: Configure the Kick Server
- Copy and paste the code below:
{
"mcpServers": {
"kick-mcp": {
"url": "https://use.kick.co/mcp",
"headers": {
"Authorization": "Bearer {YOUR_PAT}"
}
}
}
}
- Replace {YOUR_PAT} with the token you issued from Kick's Connectors page
- Click Save (cmd+s)
Step 3: Verify the Connection
- Check that Kick appears as connected in the MCP tools list under Cursor Settings
- In a Cursor conversation, ask:
List the Kick tools you can use and confirm the active workspace.
Cursor should respond with available tools (like transactions_query, reports_query, context_browse) and your active workspace name.
Authentication Options
Cursor supports two authentication methods for Kick MCP:
OAuth (Recommended)
Automatically redirects you to authorize Kick access through your browser. Choose this if your firm uses standard Kick login.
Bearer Token
Uses a personal access token generated in Kick. Choose this if your firm requires token-based authentication or you need more granular access control.
To use bearer token authentication:
- Generate a personal access token in Kick (Settings → API)
- Copy the token
- In Cursor's MCP server settings, paste the token in the authentication field
Troubleshooting
Kick Not Appearing in Tools List
The server configuration didn't load successfully.
- Go back to Cursor Settings → Tools & MCP
- Verify the MCP server URL is correct:
https://use.kick.co/mcp - Save the configuration again
- Restart Cursor
Authorization Failed
The authentication didn't complete successfully.
- Check that you're logged in to your Kick account
- Try disconnecting and reconnecting the server
- If using bearer token, verify the token is still valid in Kick settings
Wrong Workspace Showing
Your Kick account has access to multiple workspaces. Tell Cursor which workspace you want to use:
Please switch to the [workspace name] workspace.
Data Privacy and Security
- Your data stays in Kick: Cursor requests data through the MCP connection but doesn't store your Kick data permanently
- Workspace permissions apply: Cursor can only access workspaces you already have permission to view in Kick
- You control access: You can disconnect Kick at any time from the Tools & MCP settings
- Confirmation required for changes: Write operations require your explicit approval before execution
Next Steps
Now that you're connected:
- Try a sample query: "List my workspaces" or "What tools can you use?"
- Explore reports by asking Cursor to generate financial reports for your clients
- Check out the Kick MCP Use Case Library for advanced use cases
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, and the optional goal query parameter:
GET https://docs.kick.co/ai/mcp/connectors/connect-cursor.md?ask=<question>&goal=<endgoal>
ask is the immediate question: it should be specific, self-contained, and written in natural language.goal is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.