ActionKit by Paragon + MCPOmni-Connect: 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 MCPOmni-Connect, 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 MCPOmni-Connect, 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 MCPOmni-Connect
• 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
• MCPOmni-Connect installed and configured
• Compatible operating system (Python 3.9+, Windows, macOS, Linux, Docker)

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 MCPOmni-Connect

1. Open MCPOmni-Connect 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 MCPOmni-Connect:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect
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

Command Not Found

Symptoms: mcpomni-connect: command not found, CLI not accessible

Cause: Package not installed or not in PATH

Solution:

• Verify installation: pip show mcpomni-connect
• Ensure Python scripts directory is in PATH
• Try running with python -m: python -m mcpomni_connect
• Reinstall: pip install --upgrade mcpomni-connect

Configuration File Not Found

Symptoms: FileNotFoundError: mcp_config.yaml, Config not loading

Cause: Config file missing or incorrect path

Solution:

• Verify config file exists at specified path
• Use absolute path: --config /full/path/to/mcp_config.yaml
• Check file name is exactly mcp_config.yaml (case-sensitive)
• Validate YAML syntax with yamllint or online validator

MCP Server Connection Failures

Symptoms: Server not responding, Connection timeout, Transport error

Cause: Invalid server configuration or transport issues

Solution:

• Verify transport type matches server capabilities (stdio, sse, http, docker, npx)
• For stdio: ensure command and args are correct
• For SSE/HTTP: verify URL is accessible and server is running
• For Docker: ensure Docker daemon is running and image exists
• Check environment variables are set (e.g., GITHUB_TOKEN)
• Test server manually outside MCPOmni-Connect

Agent Mode Not Working

Symptoms: Agent fails to execute task, Reasoning loop errors, Tool calls failing

Cause: Insufficient LLM configuration or tool access issues

Solution:

• Ensure LLM API key is configured (OpenAI, Anthropic, etc.)
• Verify agent has access to necessary MCP server tools
• Check task description is clear and actionable
• Review agent logs for detailed error messages
• Try simpler task first to verify agent functionality

Orchestrator Mode Failures

Symptoms: Plan execution fails, Step coordination errors, Agent communication issues

Cause: Invalid plan structure or agent dependencies

Solution:

• Verify plan steps are clearly defined and sequential
• Ensure each step can be completed with available tools
• Check inter-agent communication is working
• Review orchestrator logs for step-by-step execution details
• Test individual plan steps in agent mode first

Docker Transport Errors

Symptoms: Container not starting, Docker connection refused, Port binding errors

Cause: Docker configuration or runtime issues

Solution:

• Verify Docker is installed and running: docker ps
• Check Docker image exists: docker images
• Ensure ports are not already in use
• Review container logs: docker logs <container_name>
• Verify network configuration allows container communication

FastAPI Integration Issues

Symptoms: Import errors, Async execution failures, Endpoint not responding

Cause: Incorrect async configuration or FastAPI version mismatch

Solution:

• Use run_agent_async() for async FastAPI endpoints
• Ensure FastAPI version is compatible (0.100.0+)
• Verify MCPOmniClient is initialized outside request handlers
• Check async event loop configuration
• Review FastAPI logs for detailed error messages

ActionKit by Paragon not appearing in MCPOmni-Connect

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check ActionKit by Paragon installation
• Restart MCPOmni-Connect
• Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with MCPOmni-Connect:

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