intermediate⏱️ 19-29 minutes📅 Updated June 2026

Step-by-step guide to integrate Adfin MCP server with Amazon Q CLI. Includes credit control management and invoice creation and management.

Adfin + Amazon Q CLI: Complete MCP Integration

Adfin is a MCP server that The only platform you need to get paid - all payments in one place, invoicing and accounting reconciliations with Adfin..

When integrated with Amazon Q CLI, you can:

  • Monitor and manage customer credit status and payment tracking
  • Create individual invoices with customizable details
  • Upload and process multiple PDF invoices simultaneously

This guide provides step-by-step instructions to set up Adfin in Amazon Q CLI, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

  • Adfin will be fully integrated and operational
  • You can use Adfin tools directly in Amazon Q CLI
  • All Adfin capabilities will be available for your workflows
  • Access to 5 different tools

Prerequisites

Before starting, ensure you have:

  • Adfin account email address
  • Adfin account password
  • Amazon Q CLI installed and configured
  • Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install Adfin

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 Adfin to help me"

Configuration Details

Configure MCP servers through Q CLI commands:

# Configure MCP server integration
q config set mcp.servers.adfin.command "adfin"
q config set mcp.servers.adfin.args ""
q config set mcp.servers.adfin.env ""ADFIN_EMAIL": "[email protected]",
        "ADFIN_PASSWORD": "your-secure-password""

# Verify configuration
q config list mcp.servers

Examples

Once configured, you can use Adfin in Amazon Q CLI:

Credit Control Status Check

Review overall credit control status for all customers

Ask Amazon Q CLI: "Give me a credit control status check for all our customers"

Expected Result: Comprehensive report showing customer payment status, overdue amounts, and credit risks

Create New Invoice

Generate an invoice for a specific customer with custom terms

Ask Amazon Q CLI: "Create a new invoice for 60 GBP for Abc Def that is due in a week"

Expected Result: Invoice created with customer details, amount, and 7-day payment terms

Bulk Invoice Upload

Process multiple PDF invoices from a directory

Ask Amazon Q CLI: "Upload all pdf invoices from the invoices folder from my Desktop"

Expected Result: All PDF invoices processed, validated, and uploaded to Adfin system

Payment Reconciliation

Match received payments with outstanding invoices

Ask Amazon Q CLI: "Reconcile the payment of £1,250 received today with our outstanding invoices"

Expected Result: Payment matched to appropriate invoices with reconciliation details recorded

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 Adfin functionality

Test commands:

q doctor
q chat
q config list mcp.servers

Troubleshooting

Common Issues

Authentication Failed

Symptoms: Login errors, Invalid credentials messages, 401 Unauthorized

Cause: Incorrect ADFIN_EMAIL or ADFIN_PASSWORD

Solution:

  • Verify email and password are correct in Adfin web interface
  • Check for typos in environment variables
  • Ensure credentials are not expired or locked
  • Reset password if necessary through Adfin portal

UV Package Manager Not Found

Symptoms: Command not found errors, uv command fails

Cause: UV package manager not installed or not in PATH

Solution:

  • Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh
  • Restart terminal to update PATH
  • Verify installation: uv --version
  • For Windows: use PowerShell installation script

PDF Invoice Processing Fails

Symptoms: Upload errors, PDF parsing failures, Invalid file format

Cause: Corrupted PDFs, unsupported format, or file permissions

Solution:

  • Verify PDFs are valid and readable
  • Check file permissions allow read access
  • Ensure PDFs contain text (not just images)
  • Try uploading files individually to isolate issues

Claude Desktop Configuration Error

Symptoms: MCP server not detected, Configuration syntax errors

Cause: Invalid JSON syntax or incorrect configuration structure

Solution:

  • Validate JSON syntax in claude_desktop_config.json
  • Ensure proper nesting of mcpServers configuration
  • Check file is in correct location for Claude Desktop
  • Restart Claude Desktop after configuration changes

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

Adfin not appearing in Amazon Q CLI

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check Adfin installation
  • Restart Amazon Q CLI
  • Check logs for error messages

Next Steps

Now that Adfin is integrated with Amazon Q CLI:

  • Explore all Adfin 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 Adfin 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

Adfin + Amazon Q CLI: MCP Setup Guide (2026)