ActionKit by Paragon + OpenSumi: 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 OpenSumi, 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 OpenSumi, 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 OpenSumi
• 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
• OpenSumi installed and configured
• Compatible operating system (Web (Browser-based), Electron Desktop, Container (Docker/K8s), Framework Integration)

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 OpenSumi

1. Open OpenSumi settings
2. Navigate to MCP server configuration
3. Add ActionKit by Paragon server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use ActionKit by Paragon in OpenSumi:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask OpenSumi: "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 OpenSumi: "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 OpenSumi: "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 OpenSumi: "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 OpenSumi
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

Dependency Installation Failures

Symptoms: Yarn/npm install errors, Missing packages, Version conflicts

Cause: Incompatible Node.js version or network issues

Solution:

• Ensure Node.js 16+ is installed
• Use yarn for standard installation, npm for lite version
• Clear package cache: yarn cache clean or npm cache clean --force
• Check network connectivity and proxy settings

Workspace Not Loading

Symptoms: Empty workspace, Files not showing, Permission errors

Cause: Incorrect workspace path or permissions

Solution:

• Verify MY_WORKSPACE environment variable is set correctly
• Check file system permissions for workspace directory
• Use absolute path for workspace location
• Default workspace is tools/workspace in repository

VSCode Extension Compatibility

Symptoms: Extension not loading, Extension errors, Missing features

Cause: Extension API incompatibility or missing dependencies

Solution:

• Verify extension is compatible with VSCode extension API used by OpenSumi
• Check extension documentation for known issues
• Try downloading extensions via yarn run download-extension
• Some extensions may require OpenSumi-specific adaptation

WebWorker Compilation Errors (Lite Version)

Symptoms: Compile-worker fails, Language service not working, Syntax highlighting broken

Cause: WebWorker build configuration issues

Solution:

• Run npm run compile-worker before starting
• Ensure all dependencies are installed correctly
• Check browser console for WebWorker loading errors
• Clear browser cache and rebuild

MCP Client Connection Failures

Symptoms: Cannot connect to MCP server, Tool discovery fails, MCP errors in console

Cause: MCP server not running or incorrect configuration

Solution:

• Verify MCP server is running and accessible
• Check MCP server URL in OpenSumi configuration
• Review MCP client integration code for errors
• Check browser/Electron console for detailed error messages

Electron App Not Starting

Symptoms: Electron window not opening, White screen, App crashes on launch

Cause: Electron build issues or IPC communication errors

Solution:

• Ensure Electron dependencies are installed correctly
• Check Electron version compatibility (15+)
• Review IPC communication setup in configuration
• Check Electron dev tools console for errors

ActionKit by Paragon not appearing in OpenSumi

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that ActionKit by Paragon is integrated with OpenSumi:

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