Skip to content
English
Create Ticket Customer Portal
Spinify Academy
  • There are no suggestions because the search field is empty.

Connect Spinify MCP To Microsoft Copilot Studio

Use this guide to connect your Copilot Studio agent to the Spinify MCP server so your agent can call Spinify tools (competitions, leaderboards, notifications, and more) on behalf of a signed-in Spinify user.


This guide follows Microsoft’s Connect your agent to an existing MCP server flow, tailored for Spinify.

Before you start

You need:

Access to Microsoft Copilot Studio with permission to edit an agent

  • A Spinify account for the organization you want the agent to access
  • Network access from Power Platform to https://mcp.spinify.com (see Data policies if connectors are restricted in your tenant)

Spinify MCP uses Streamable HTTP transport, which Copilot Studio supports. Authentication is OAuth 2.0 with dynamic client registration and discovery.


Connection details

Use these values when you configure the tool:

Field

Value

Server name

Spinify

Server description

Spinify gamification tools for competitions, leaderboards, coaching insights, notifications, and org members. Use when users ask about Spinify contests, rankings, performance, or ringing the gong.

Server URL

https://mcp.spinify.com/mcp

Authentication

OAuth 2.0 → Dynamic discovery

Do not use API key auth or “None.” Spinify requires a signed-in user via OAuth.

Connect with the MCP onboarding wizard

1. Open the wizard

  1. In Copilot Studio, open your agent.
  2. Go to Tools.
  3. Select Add a tool → New tool → Model Context Protocol.

The MCP onboarding wizard opens.

2. Enter Spinify server details

Fill in the wizard fields:

  1. Server name: Spinify
  2. Server description: use the description from the table above (or a short variant). Copilot uses this text to decide when to call Spinify at runtime, so keep it clear and specific.
  3. Server URL: https://mcp.spinify.com/mcp

3. Configure OAuth (Dynamic discovery)

  1. Set the authentication type to OAuth 2.0.
  2. Set OAuth type to Dynamic discovery.

Spinify advertises OAuth metadata at:

  • https://mcp.spinify.com/.well-known/oauth-authorization-server
  • https://mcp.spinify.com/.well-known/oauth-protected-resource

With Dynamic discovery, Copilot Studio discovers those endpoints and registers itself automatically. You do not need to enter Client ID, Client secret, Authorization URL, or Token URL manually.

  1. Select Create.
  2. Select Next when prompted.

4. Create a connection and add the tool

  1. On Add tool, select Create a new connection (or pick an existing Spinify connection if you already have one).
  2. Complete the Spinify sign-in / consent flow when prompted.
  3. Select Add to agent.

Your agent can now call Spinify MCP tools after a successful connection.

Verify the connection

  1. Open your agent’s Test pane (or chat with the agent where it is published).
  2. Sign in / connect if Copilot asks you to authenticate with Spinify.
  3. Try prompts such as:
    • “What competitions am I in on Spinify?”
    • “Show me the leaderboard for my active competition.”
    • “Any Spinify notifications for me?”

If tools fail with auth errors, reconnect the tool from Tools, create a new connection, and complete OAuth again.

What agents can do with Spinify

Available tools depend on the signed-in user’s Spinify license (Player vs Admin). Typical capabilities include:

  • List active competitions and performance
  • Fetch competition leaderboards
  • Read notifications
  • List org members
  • Ring the gong
  • Admin: org competitions, coaching reports, user competition summaries, coaching widgets

Exact tool availability is determined at runtime for the authenticated user.

Troubleshooting

Symptom

What to check

Wizard cannot reach the server

Confirm Server URL is exactly https://mcp.spinify.com/mcp (include /mcp).

OAuth / Dynamic discovery fails

Confirm https://mcp.spinify.com/.well-known/oauth-authorization-server is reachable from your network/browser.

Connection created but tools return 401

Create a new connection and complete Spinify sign-in again; expired or missing tokens cause this.

Agent never calls Spinify

Improve the Server description and add topics/instructions that mention Spinify competitions, leaderboards, etc.

Blocked by tenant policy

Ask your Power Platform admin to allow the MCP / custom connector under DLP (see below).

For Microsoft’s general MCP connection steps and auth options, see the official Copilot Studio MCP guide.

Data policies

Copilot Studio reaches MCP servers through Power Platform connectors. If your organization uses data loss prevention (DLP) policies, an admin may need to allow this custom MCP connector before agents can use Spinify.

What’s next

  • Today: customers and partners create this connection with the MCP onboarding wizard (this guide).
  • Coming soon: an official Spinify connector in the Microsoft connector directory for a one-click add experience.

If you need help after following this guide, contact Spinify Support.