ActionKit by Paragon + Roo Code: 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 Roo Code, 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 Roo Code, 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 Roo Code
• 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
• Roo Code installed and configured
• Compatible operating system (Windows, macOS, Linux)

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 Roo Code

1. Locate your configuration file:

   • Windows: %USERPROFILE%\.roo\mcp_settings.json
   • macOS: ~/.roo/mcp_settings.json
   • Linux: ~/.roo/mcp_settings.json

2. Add server configuration:

{
  "mcpServers": {
    "actionkit-by-paragon": {
      "command": "npx",
      "args": ["-y", "actionkit-by-paragon"],
      "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"
      }
    }
  }
}

3. Restart Roo Code

Completely quit and restart Roo Code to load the new configuration.

Examples

Once configured, you can use ActionKit by Paragon in Roo Code:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask Roo Code: "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 Roo Code: "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 Roo Code: "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 Roo Code: "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. Start a new conversation in Roo Code
2. Ask Roo Code to list available tools
3. Try using ActionKit by Paragon functionality

Test prompts:

• "Type @ and verify ActionKit by Paragon appears in the tools list"
• "Ask: "Use ActionKit by Paragon to help with my task""
• "Check Roo Code output panel for server connection status"

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

MCP Server Not Connecting

Symptoms: Server not appearing in tools list, Connection timeout, MCP tools unavailable

Cause: Incorrect configuration or server not starting

Solution:

• Verify mcp_settings.json syntax is correct
• Check that Node.js and npx are installed and in PATH
• View Roo Code output panel for error messages
• Test server command manually in terminal: npx -y {server_id}
• Ensure environment variables are properly set

Permission Denied Errors

Symptoms: Cannot execute commands, File access denied, Terminal commands blocked

Cause: Roo Code requires explicit permission for file and command operations

Solution:

• Review and approve permission requests when prompted
• Check VS Code workspace trust settings
• Enable necessary permissions in Roo Code settings
• Verify file and folder permissions on your system

API Key or Model Issues

Symptoms: Authentication failed, Model not responding, No AI completions

Cause: AI model API key not configured or invalid

Solution:

• Verify API key is correctly set in Roo Code settings
• Check API key has sufficient credits/quota
• Test with a different AI model provider
• Review Roo Code output panel for API error details

Custom Mode Not Working with MCP

Symptoms: MCP tools not available in custom mode, Mode cannot access server

Cause: Custom mode configuration does not include MCP tool permissions

Solution:

• Edit custom mode configuration to include MCP tools
• Add "Use MCP" to available tools in mode definition
• Ensure mode has appropriate permissions for external tools
• Test with default mode first to verify MCP server works

Extension Conflicts

Symptoms: Roo Code not responding, VS Code performance issues, Unexpected behavior

Cause: Conflicts with other AI coding extensions

Solution:

• Disable other AI coding extensions (Cline, Continue, etc.)
• Restart VS Code after disabling conflicting extensions
• Check VS Code extension logs for conflict errors
• Use only one AI coding assistant extension at a time

ActionKit by Paragon not appearing in Roo Code

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check ActionKit by Paragon installation
• Restart Roo Code
• Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with Roo Code:

• Explore all ActionKit by Paragon capabilities through Roo Code
• Check out other MCP servers that work with Roo Code
• 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 Roo Code MCP guide
• Join the MCP community discussions