ActionKit by Paragon + Microsoft Copilot Studio: Complete MCP Integration

ActionKit by Paragon is a MCP server that Connect to 130+ SaaS integrations (e.g. Slack, Salesforce, Gmail) with Paragon’s ActionKit API..

When integrated with Microsoft Copilot Studio, you can:

• Connect to 130+ SaaS applications via ActionKit API
• Handle OAuth and API authentication for integrations
• Execute custom OpenAPI action definitions

This guide provides step-by-step instructions to set up ActionKit by Paragon in Microsoft Copilot Studio, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• ActionKit by Paragon will be fully integrated and operational
• You can use ActionKit by Paragon tools directly in Microsoft Copilot Studio
• All ActionKit by Paragon capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• Node.js 22.14.0
• npm
• Paragon account
• Paragon project identifier from dashboard
• RS256 JWT signing key for authentication
• Microsoft Copilot Studio installed and configured
• Compatible operating system (Web Browser, Microsoft 365)

Installation

Step 1: Install ActionKit by Paragon

Install using npm:

git clone https://github.com/useparagon/paragon-mcp.git && cd paragon-mcp && npm install

Verify installation:

npm run start

Configuration

Step 2: Configure Microsoft Copilot Studio

1. Enable Generative Orchestration

Generative Orchestration must be enabled in your Copilot Studio environment to use MCP

Visit: https://learn.microsoft.com/en-us/microsoft-copilot-studio/agent-extend-action-mcp

Note: This is a prerequisite - MCP will not work without it

2. Access Copilot Studio

Log in to Microsoft Copilot Studio with appropriate permissions to create and configure agents

Visit: https://copilotstudio.microsoft.com

Note: Requires organizational access or trial subscription

3. Navigate to Connectors

In Copilot Studio, go to the Connectors section where you can add new integrations

Note: Location may vary based on interface updates

4. Create MCP Connector

Click "Add Connector" and select "Model Context Protocol (MCP)" from the available connector types

Note: Use the YAML schema template provided by Copilot Studio

5. Configure {server_name} Connection

Fill in the YAML schema with {server_name} server details including command, arguments, and environment variables

git

Note: Copilot Studio dynamically reflects changes as tools and resources are updated on the MCP server

6. Add Tools to Agent

Once connected, add the MCP server tools and resources to your specific agent through the Copilot Studio UI

Note: Currently supports Tools and Resources (Prompts not yet supported)

7. Test Agent Capabilities

Test your agent to verify it can access and use the {server_name} tools correctly

Configuration Details

Connect MCP server to Microsoft Copilot Studio:

Step 1: Create YAML Connector Schema

In Copilot Studio, navigate to the connectors section and create a new MCP connector using the YAML schema template:

# MCP Connector Configuration for ActionKit by Paragon
name: ActionKit by Paragon-mcp-connector
description: Connect to 130+ SaaS integrations (e.g. Slack, Salesforce, Gmail) with Paragon’s ActionKit API.

mcp_server:
  command: git
  args: "clone", "https://github.com/useparagon/paragon-mcp.git", "&&", "cd", "paragon-mcp", "&&", "npm", "install"
  env: "PROJECT_ID": "your-project-id",
        "SIGNING_KEY": "your-private-key-content",
        "SIGNING_KEY_PATH": "./keys/private-key.pem",
        "LIMIT_TO_INTEGRATIONS": "google-calendar,slack,salesforce",
        "PORT": "8080",
        "MCP_SERVER_URL": "https://your-server.com"

Step 2: Add to Agent

Once connected, add the MCP server's tools and resources to your Copilot Studio agent through the UI.

Examples

Once configured, you can use ActionKit by Paragon in Microsoft Copilot Studio:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask Microsoft Copilot Studio: "Schedule a team standup for tomorrow at 9 AM and send a Slack notification to the dev-team channel"

Expected Result: Calendar event created and Slack message sent with meeting details

Create Sales Lead

Add new lead to Salesforce from customer inquiry

Ask Microsoft Copilot Studio: "Create a new lead in Salesforce for John Doe from Acme Corp with email [email protected]"

Expected Result: Lead record created in Salesforce with contact information and follow-up tasks

Email Campaign Follow-up

Send follow-up emails via Gmail for marketing campaign

Ask Microsoft Copilot Studio: "Send a follow-up email to all prospects who opened our product demo email last week"

Expected Result: Targeted emails sent to qualified prospects with personalized content

Multi-Platform Data Sync

Sync customer data between HubSpot and Salesforce

Ask Microsoft Copilot Studio: "Update all HubSpot contacts that were modified today in our Salesforce CRM"

Expected Result: Contact records synchronized with latest information across both platforms

Testing Your Setup

1. Launch Microsoft Copilot Studio
2. Verify ActionKit by Paragon is available in the tools list
3. Test basic ActionKit by Paragon functionality

Troubleshooting

Common Issues

JWT Authentication Failed

Symptoms: 401 Unauthorized errors, Invalid token messages

Cause: Incorrect SIGNING_KEY or expired credentials

Solution:

• Verify SIGNING_KEY matches private key from Paragon dashboard
• Ensure key is in correct RS256 format
• Check PROJECT_ID is correct for your account
• Regenerate keys if necessary

Integration Not Available

Symptoms: Service not found errors, Integration disabled messages

Cause: Integration not enabled in Paragon project or LIMIT_TO_INTEGRATIONS restriction

Solution:

• Enable required integrations in Paragon dashboard
• Remove or update LIMIT_TO_INTEGRATIONS environment variable
• Verify integration is available in your Paragon plan
• Check integration-specific requirements

User Authorization Required

Symptoms: OAuth flow errors, Permission denied messages

Cause: User has not authorized the integration or scope issues

Solution:

• Guide user through OAuth authorization flow
• Check required scopes for the integration
• Verify callback URLs are configured correctly
• Re-authorize if tokens are expired

Server Connection Timeout

Symptoms: Connection timeouts, SSE endpoint not responding

Cause: Server not running or network connectivity issues

Solution:

• Start server with npm run start
• Verify PORT is not in use by another service
• Check firewall settings allow connections
• Test endpoint with curl: curl http://localhost:3001/health

Generative Orchestration Not Available

Symptoms: MCP option not visible, Cannot add MCP connectors

Cause: Generative Orchestration is not enabled for your environment

Solution:

• Contact your Microsoft 365 administrator
• Enable Generative Orchestration in tenant settings
• Verify your subscription includes Copilot Studio with MCP support
• Check Microsoft Learn documentation for enablement steps

MCP Connector Connection Failed

Symptoms: Connector shows "Disconnected" status, Tools not available to agent

Cause: MCP server not accessible or configuration error

Solution:

• Verify the MCP server command is correct and accessible
• Check all required environment variables are set
• Test the MCP server independently outside Copilot Studio
• Review YAML schema for syntax errors
• Check network connectivity and firewall rules

Tools Not Appearing in Agent

Symptoms: Connector connected but tools missing, Agent cannot invoke MCP tools

Cause: Tools not added to agent or synchronization issue

Solution:

• Manually add tools to agent through Copilot Studio UI
• Refresh connector to sync latest tools from MCP server
• Verify tools are published on the MCP server
• Check agent configuration includes the MCP connector

MCP Server Tools Update Not Reflected

Symptoms: New tools not appearing, Old tools still visible after removal

Cause: Copilot Studio cache or sync delay

Solution:

• Disconnect and reconnect the MCP connector
• Wait a few minutes for dynamic sync to occur
• Manually refresh the connector in Copilot Studio
• Restart the MCP server if possible

ActionKit by Paragon not appearing in Microsoft Copilot Studio

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check ActionKit by Paragon installation
• Restart Microsoft Copilot Studio
• Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with Microsoft Copilot Studio:

• Explore all ActionKit by Paragon capabilities through Microsoft Copilot Studio
• Check out other MCP servers that work with Microsoft Copilot Studio
• Join the MCP community for tips and support
• Consider contributing to ActionKit by Paragon development

Need Help?

• Search for ActionKit by Paragon documentation
• Check the Microsoft Copilot Studio MCP guide
• Join the MCP community discussions