beginner⏱️ 22-32 minutes📅 Updated June 2026

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

ActionKit by Paragon + Amp: 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 Amp, 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 Amp, 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 Amp
  • 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
  • Amp installed and configured
  • Compatible operating system (macOS, Linux, Windows (WSL))

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 Amp

  1. Locate your configuration file:

  2. Add server configuration:

Configure MCP servers in VS Code/Cursor settings.json:

```json
{
  "amp.mcpServers": {
    "playwright": {
      "command": "npx",
      "args": ["-y", "@playwright/mcp@latest", "--headless", "--isolated"]
    },
    "semgrep": {
      "url": "https://mcp.semgrep.ai/mcp"
    },
    "sourcegraph": {
      "url": "${SRC_ENDPOINT}/.api/mcp/v1",
      "headers": {
        "Authorization": "token ${SRC_ACCESS_TOKEN}"
      }
    },
    "linear": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.linear.app/sse"]
    }
  }
}

Or add servers via CLI:

# Add HTTP-based server
amp mcp add sourcegraph --header "Authorization=token your-token" https://sourcegraph.example.com/.api/mcp/v1

# Add SSE-based server
amp mcp add linear https://mcp.linear.app/sse

# OAuth login for authenticated servers
amp mcp oauth login my-server \
  --server-url https://example.com/.api/mcp/v1 \
  --client-id your-client-id \
  --client-secret your-client-secret \
  --scopes "openid,profile,email"


3. **Restart Amp**

Completely quit and restart Amp to load the new configuration.



## Examples

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

### Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

**Ask Amp:** "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 Amp:** "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 Amp:** "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 Amp:** "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 Amp
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

#### MCP Server Not Connecting

**Symptoms:** Server not appearing in tools, Connection timeout, Authentication errors

**Cause:** Invalid configuration, missing credentials, or network issues

**Solution:**
- Verify server URL and command are correct
- Check environment variables are set properly
- For OAuth servers, run amp mcp oauth login
- Review amp logs for error messages

#### Tool Execution Fails

**Symptoms:** MCP tools available but not working, Error messages during execution

**Cause:** Server dependencies missing or permission issues

**Solution:**
- Verify required environment variables are configured
- Check amp.permissions settings for tool restrictions
- Test MCP server independently
- Review server-specific documentation

#### Permission Denied

**Symptoms:** Tool blocked by permission system, Ask prompts for every action

**Cause:** Permission rules restricting MCP tool usage

**Solution:**
- Review amp.permissions in settings.json
- Add allow rules for trusted MCP servers
- Use amp permissions edit to modify rules

#### ActionKit by Paragon not appearing in Amp

**Symptoms:** Server not listed, Tools not available

**Cause:** Configuration or installation issue

**Solution:**
- Verify configuration syntax
- Check ActionKit by Paragon installation
- Restart Amp
- Check logs for error messages



## Next Steps

Now that ActionKit by Paragon is integrated with Amp:

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

## Need Help?

- Search for [ActionKit by Paragon documentation](https://www.mcpstack.org)
- Check the [Amp MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions

Related Resources

More Integrations

Explore other MCP servers that work with Amp

Need Help?

Join the MCP community for support and discussions

ActionKit by Paragon + Amp: MCP Setup Guide (2026)