beginner⏱️ 22-32 minutes📅 Updated June 2026

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

ActionKit by Paragon + Sourcegraph Cody: 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 Sourcegraph Cody, 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 Sourcegraph Cody, 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 Sourcegraph Cody
  • 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
  • Sourcegraph Cody installed and configured
  • Compatible operating system (VS Code Extension, JetBrains Extension)

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 Sourcegraph Cody

  1. Open Sourcegraph Cody 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 Sourcegraph Cody:

Schedule Team Meeting

Create a Google Calendar event and notify team via Slack

Ask Sourcegraph Cody: "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 Sourcegraph Cody: "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 Sourcegraph Cody: "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 Sourcegraph Cody: "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 Sourcegraph Cody
  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

Tools Not Available

Symptoms: Cody does not see the connected tools

Cause: Incorrect config path or JSON syntax error

Solution:

  • Verify path is exactly ~/.config/cody/mcp_servers.json
  • Check JSON validity
  • Check Cody output logs in VS Code Output panel

ActionKit by Paragon not appearing in Sourcegraph Cody

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check ActionKit by Paragon installation
  • Restart Sourcegraph Cody
  • Check logs for error messages

Next Steps

Now that ActionKit by Paragon is integrated with Sourcegraph Cody:

  • Explore all ActionKit by Paragon capabilities through Sourcegraph Cody
  • Check out other MCP servers that work with Sourcegraph Cody
  • 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 Sourcegraph Cody

Need Help?

Join the MCP community for support and discussions

ActionKit by Paragon + Sourcegraph Cody: MCP Setup Guide (2026)