connect microsoft copilot.md

Connect Microsoft Copilot

Copilot Studio vs. Consumer Copilot

This guide is for Copilot Studio only. To give your team Kick access through a conversational AI interface, you must:

  1. Build an agent in Copilot Studio (this guide)
  2. Publish it to your organization
  3. Team members then use your custom agent

What Is Copilot Studio?

Microsoft Copilot Studio is a low-code platform for building custom AI agents (copilots) for your organization. Unlike consumer-facing Microsoft Copilot in Edge or Windows, Copilot Studio lets you create specialized agents that connect to your firm's data and tools.

Use Copilot Studio to:

This guide shows you how to connect your Copilot Studio agent to Kick's MCP server so your custom copilot can access accounting data.


What You'll Need

{% hint style="info" %} Tip: Log in to your Kick account in your browser before starting. This makes the authorization step faster. {% endhint %}


Connect Kick MCP to Your Agent

Step 1: Create or Open Your Agent

  1. Go to Copilot Studio
  2. Create a new agent or open an existing one
  3. In the agent editor, go to Settings

Step 2: Add the Kick MCP Server

  1. In Settings, navigate to MCP servers or Connectors
  2. Click Add MCP server
  3. Complete the connection form:
    • Name: Kick
    • MCP server URL: https://use.kick.co/mcp
    • Transport: Choose Remote MCP or Streamable HTTP (depending on available options)
    • Authentication: Select OAuth if available, otherwise API Key or Bearer token
  4. Click Add or Save

Step 3: Authorize the Connection

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:
    • Read & write — Full access (write operations require approval in the agent)
    • Read-only — View-only access
  4. Choose workspace access:
    • All my workspaces — Access all current and future workspaces
    • Selected organizations — Choose specific organizations
    • Selected workspaces — Choose specific workspaces
  5. Click Authorize

If using Bearer Token:

  1. Generate a personal access token in Kick (Settings → API)
  2. Copy the token (starts with kick_pat_)
  3. Paste it in the authentication field in Copilot Studio
  4. Save the configuration

Step 4: Configure Agent Tools

After adding the Kick MCP server:

  1. Go to your agent's Actions or Tools settings
  2. Enable the Kick tools you want your agent to access
  3. Configure tool permissions:
    • Read-only tools — Always available
    • Write tools — May require confirmation prompts

Step 5: Test Your Agent

  1. Open the Test your agent panel
  2. Ask your agent:
List the Kick tools you can use and confirm the active workspace.

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


Publish Your Agent

Once you've configured and tested the Kick connection:

  1. Click Publish in the agent editor
  2. Choose where to publish:
    • Your organization — Available to all members
    • Specific teams or groups — Limited distribution
    • External — Share outside your organization (requires admin approval)
  3. Confirm publication

Team members can now use your custom agent to access Kick data through conversation.


Example Agent Prompts

Once your agent is connected to Kick, team members can ask it:

The agent will pull live data from Kick and, for write operations, ask for confirmation before making changes.


Agent Configuration Tips

Set Default Workspace

Configure your agent to default to a specific workspace:

  1. In agent settings, add a system prompt
  2. Include: "Always use the [workspace name] workspace unless the user specifies otherwise"

Require Approval for Write Operations

Ensure write operations require explicit user confirmation:

  1. Go to agent Actions settings
  2. For each write tool (like transactions_act, rules_act), enable Requires confirmation
  3. Configure confirmation prompts for clarity

Add Context About Your Firm

Give your agent context about your firm's processes:

  1. Add a knowledge source with your firm's accounting policies
  2. Include client naming conventions
  3. Document common workflows

This helps the agent provide more relevant, firm-specific responses.


Troubleshooting

MCP Server Won't Connect

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. Try removing and re-adding the server
  4. Check Copilot Studio service status

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 token format starts with kick_pat_

Agent Can't Access Kick Tools

Tools aren't appearing in the agent's available actions.

  1. Go to agent Actions or Tools settings
  2. Verify Kick tools are enabled
  3. Republish the agent after enabling tools
  4. Test in the agent editor before publishing

Wrong Workspace Showing

Your Kick account has access to multiple workspaces. Configure the agent to specify:

  1. Add a system prompt: "Use the [workspace name] workspace"
  2. Or tell the agent in conversation: "Switch to [workspace name] workspace"

Security and Permissions

Data Access

Confirmation Requirements

Token Management


Data Privacy


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 your Copilot Studio agent to generate financial reports for your clients
  3. Check out the Kick MCP Use Case Library for advanced use cases

Need More Help?