intermediate⏱️ 27-37 minutes📅 Updated June 2026

Step-by-step guide to integrate ActionKit by Paragon MCP server with Amazon Q CLI. Includes saas integration hub and authentication management.

ActionKit by Paragon + Amazon Q CLI: 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 Amazon Q CLI, 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 Amazon Q CLI, 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 Amazon Q CLI
  • 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
  • Amazon Q CLI 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 Amazon Q CLI

  1. Install Amazon Q CLI

Download and install Q CLI for your platform

Visit: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html

  1. Authenticate

Set up authentication with AWS Builder ID or IAM Identity Center

q auth

Note: Follow interactive authentication flow

  1. Verify Installation

Test Q CLI installation and configuration

q doctor
  1. Install MCP Server

Install the MCP server you want to integrate

Note: Ensure server is accessible from command line

  1. Configure MCP Integration

Add MCP server configuration to Q CLI

Note: Use q config commands to set server parameters

  1. Test Integration

Verify MCP server works with Q CLI

q chat "Use ActionKit by Paragon to help me"

Configuration Details

Configure MCP servers through Q CLI commands:

# Configure MCP server integration
q config set mcp.servers.actionkit-by-paragon.command "git"
q config set mcp.servers.actionkit-by-paragon.args ""clone", "https://github.com/useparagon/paragon-mcp.git", "&&", "cd", "paragon-mcp", "&&", "npm", "install""
q config set mcp.servers.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""

# Verify configuration
q config list mcp.servers

Examples

Once configured, you can use ActionKit by Paragon in Amazon Q CLI:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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. Run q doctor to verify system health
  2. Start Q CLI chat session
  3. Ask Q to list available MCP tools
  4. Test specific ActionKit by Paragon functionality

Test commands:

q doctor

q chat

q config list mcp.servers

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

Installation Failed

Symptoms: Q command not found, Installation errors

Cause: Incomplete installation or PATH issues

Solution:

  • Verify installer completed successfully
  • Check PATH environment variable includes Q CLI
  • Try running q doctor for diagnostics
  • Reinstall using platform-specific method

Authentication Problems

Symptoms: Auth errors, Cannot connect to AWS services

Cause: Invalid credentials or network issues

Solution:

  • Run q auth to re-authenticate
  • Verify AWS Builder ID or IAM credentials
  • Check network connectivity to AWS
  • Ensure proper AWS permissions are set

MCP Server Not Found

Symptoms: Server command not found, MCP tools unavailable

Cause: Server not installed or not in PATH

Solution:

  • Verify MCP server installation
  • Check server executable permissions
  • Use absolute path in configuration
  • Test server independently with direct command

Configuration Errors

Symptoms: Config commands fail, Settings not persisting

Cause: Invalid configuration syntax or permissions

Solution:

  • Check Q CLI configuration file permissions
  • Verify configuration syntax is correct
  • Use q config list to review current settings
  • Report issues with q issue command

ActionKit by Paragon not appearing in Amazon Q CLI

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check ActionKit by Paragon installation
  • Restart Amazon Q CLI
  • Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with Amazon Q CLI:

  • Explore all ActionKit by Paragon capabilities through Amazon Q CLI
  • Check out other MCP servers that work with Amazon Q CLI
  • Join the MCP community for tips and support
  • Consider contributing to ActionKit by Paragon development

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with Amazon Q CLI

Need Help?

Join the MCP community for support and discussions

ActionKit by Paragon + Amazon Q CLI: MCP Setup Guide (2026)