ActionKit by Paragon + mcphub.nvim: 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 mcphub.nvim, 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 mcphub.nvim, 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 mcphub.nvim
• 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
• mcphub.nvim installed and configured
• Compatible operating system (Neovim)

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 mcphub.nvim

1. Locate your configuration file:

   • Windows: %LOCALAPPDATA%\mcphub\servers.json
   • macOS: ~/.config/mcphub/servers.json
   • Linux: ~/.config/mcphub/servers.json

2. Add server configuration:

{
  "mcpServers": {
    "actionkit-by-paragon": {
      "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"
      }
    }
  }
}

3. Restart mcphub.nvim

Completely quit and restart mcphub.nvim to load the new configuration.

Examples

Once configured, you can use ActionKit by Paragon in mcphub.nvim:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask mcphub.nvim: "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 mcphub.nvim: "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 mcphub.nvim: "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 mcphub.nvim: "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 mcphub.nvim
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

Servers not showing in :McpHub

Symptoms: Empty server list, Configuration not loaded

Cause: Incorrect configuration file path or JSON syntax error

Solution:

• Verify servers.json exists in ~/.config/mcphub/ or .vscode/mcp.json in project root
• Check JSON syntax for errors (trailing commas, missing quotes)
• Run :checkhealth mcphub to diagnose issues

Tool execution fails

Symptoms: Error message when AI tries to use tool, No response

Cause: Server command failed or environment variables missing

Solution:

• Check server logs in :McpHub
• Verify "command" path is correct and executable
• Ensure required environment variables are set in the config

Chat plugin not recognizing tools

Symptoms: AI says it cannot perform the action, Tools not listed in chat

Cause: Integration issue with the specific chat plugin

Solution:

• Ensure you are using a supported version of the chat plugin
• Check mcphub.nvim documentation for plugin-specific setup instructions
• Restart Neovim to reload the integration

ActionKit by Paragon not appearing in mcphub.nvim

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check ActionKit by Paragon installation
• Restart mcphub.nvim
• Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with mcphub.nvim:

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