Advanced Setup | AI & MCP | Kick Docs

For most accountants, the MCP Quickstart covers what you need. Use this page when you're connecting an AI client other than Claude or ChatGPT, when your client requires a JSON config file, or when you need the full reference on PATs, OAuth scopes, and workspace selection.

Config-file setup

Use this section when your client requires a JSON config or when an admin is preparing a repeatable setup.

Cursor

Add Kick to ~/.cursor/mcp.json or a project .cursor/mcp.json:

{
    "mcpServers": {
        "kick": {
            "url": "https://use.kick.co/mcp",
            "headers": {
                "Authorization": "Bearer kick_pat_replace_me"
            }
        }
    }
}

Reload Cursor after changing MCP configuration.

Claude Desktop or Claude Code

If your Claude plan supports remote custom connectors, prefer the UI flow in the MCP Quickstart. For config-file clients, point the server at the hosted endpoint with bearer authentication:

{
    "mcpServers": {
        "kick": {
            "url": "https://use.kick.co/mcp",
            "headers": {
                "Authorization": "Bearer kick_pat_replace_me"
            }
        }
    }
}

Restart Claude after changing the configuration.

Generic MCP clients

Point the client at https://use.kick.co/mcp with bearer authentication:

Authorization: Bearer kick_pat_...

PATs and OAuth scopes

Kick MCP supports two authentication methods.

PAT bearer header

For PAT-based clients, send the token as a bearer header:

Authorization: Bearer kick_pat_...

Important: Keep PATs out of prompts, source control, and shared docs. Revoke any token you suspect has been exposed.

OAuth scopes

OAuth-capable clients can discover Kick's protected resource metadata at:

https://use.kick.co/.well-known/oauth-protected-resource

Kick MCP has two kinds of tools, each with its own OAuth scope:

• Read-only tools: mcp:read scope. Used for tool discovery and any call that only looks up data.
• Write tools: mcp:write scope. Used for any call that creates or updates data. Kick previews the change before confirming it.

Workspace selection

Workspace-scoped MCP tools can receive workspaceId in tool arguments.

Workspace-bound PATs auto-inject their bound workspace. The backend injects a default workspaceId only when the credential resolves to exactly one workspace. User-scoped PATs and OAuth tokens should pass workspaceId explicitly.

Find available tools

Use the tool list shown by your AI client as the source of truth. Available Kick tools can vary by token scope, workspace permissions, enabled features, and client cache state.

Common ways to inspect tools:

• Open the client's MCP, tools, or connector panel and look for the Kick server.
• Use a client command such as /mcp list or MCP: List Servers.
• Ask a read-only prompt:

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

If a tool was recently added or renamed, restart or reconnect the MCP client so it reloads the tool list.

Common tool examples

These are not a complete list. Use your client's tool list for the up-to-date names available to your credential.

• context_browse: list workspaces and entities the credential can access.
• context_resolve: resolve a workspace, entity, or ledger by name.
• transactions_query: search, inspect, or summarize transactions.
• reports_query: run profit and loss, balance sheet, trial balance, and other reports.
• activity_query: list recent activity and audit logs.

Kick MCP tools use portable lower-snake-case names.

Safety

• Use read-only access for lookup and reporting.
• Use write access only when the workflow needs it.
• Confirm workspace and entity IDs before using an assistant on client data.
• Treat assistant output as a draft until an accountant reviews it.

For deeper safety detail, see → Permissions and Security. For setup verification and example prompts, see → MCP Quickstart.