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

1. Open MCPHub (mcp.nvim) 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 MCPHub (mcp.nvim):

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask MCPHub (mcp.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 (mcp.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 (mcp.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 (mcp.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 (mcp.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

Plugin Not Loading or Command Not Found

Symptoms: :MCPHub command not recognized, Plugin not appearing in :PlugStatus, No errors but plugin inactive

Cause: Plugin not properly installed or configuration error

Solution:

• Verify plugin is added to plugin manager configuration
• Run plugin manager install command (:PackerInstall, :PlugInstall, or Lazy auto-install)
• Check for errors in :messages after sourcing config
• Ensure dependencies (plenary.nvim, nui.nvim) are installed
• Restart Neovim completely

MCP Server Won't Start

Symptoms: Server status shows "Error", Red indicator on server, Server immediately stops after starting

Cause: Invalid server configuration or missing dependencies

Solution:

• Verify npx is installed and in PATH: npx --version
• Check MCP server package exists: npx -y @modelcontextprotocol/server-filesystem --help
• Review server configuration in setup() - verify command and args
• Check server logs in MCPHub interface for detailed error messages
• Ensure required environment variables are set (e.g., GITHUB_TOKEN)
• Test server manually in terminal: npx -y @modelcontextprotocol/server-filesystem /path

UI Not Displaying Correctly

Symptoms: Blank window, Garbled text, Layout issues, Missing borders

Cause: Terminal or Neovim rendering issues

Solution:

• Verify Neovim version is 0.9 or higher: nvim --version
• Try different border style in ui.border config ("single", "double", "rounded")
• Check terminal supports Unicode and 256 colors
• Update nui.nvim dependency to latest version
• Test with different colorscheme to rule out theme conflicts

Integration with Avante/CodeCompanion Not Working

Symptoms: AI assistant not seeing MCP tools, Tool calls failing, Integration not recognized

Cause: Integration not enabled or incompatible versions

Solution:

• Verify integration is enabled in config: integrations.avante = true
• Ensure Avante.nvim/CodeCompanion.nvim is installed and loaded
• Check versions are compatible - update both plugins to latest
• Restart Neovim after enabling integration
• Check :checkhealth for integration-specific warnings

Marketplace Not Loading

Symptoms: :MCPHubMarketplace shows empty list, Network error in marketplace, Timeout loading servers

Cause: Network connectivity issues or marketplace service unavailable

Solution:

• Verify internet connectivity
• Check firewall allows HTTPS connections
• Try again later if marketplace service is temporarily down
• Review proxy settings if behind corporate firewall
• Check :messages for detailed network error messages

Project-Local Config Not Loading

Symptoms: .mcphub.json ignored, Project servers not appearing, Only global config loaded

Cause: Config file location or format issues

Solution:

• Verify .mcphub.json is in project root (same directory as .git)
• Check JSON syntax is valid using jsonlint or similar tool
• Ensure file name is exactly .mcphub.json (case-sensitive)
• Restart Neovim after creating/modifying project config
• Check file permissions are readable

ActionKit by Paragon not appearing in MCPHub (mcp.nvim)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check ActionKit by Paragon installation
• Restart MCPHub (mcp.nvim)
• Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with MCPHub (mcp.nvim):

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