What is the key difference between Aa and Letswork?

Aa belongs to the Developer Tools category with local stdio execution, while Letswork belongs to the Developer Tools category with local stdio execution.

How do I install Aa or Letswork in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Aa and Letswork free or paid?

Aa operates under a Free / Open Source model (No auth required). Letswork operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Aa lists 13 tools with 0 views and 0 GitHub stars. Letswork lists 14 tools with 0 views and 0 GitHub stars.

Can I use both Aa and Letswork together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Aa vs Letswork

In-depth architectural comparison of the Aa and Letswork MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Developer Tools · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

Letswork

Developer Tools · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Verdict Summary: Choose Aa if you need specialized Developer Tools tools running via a local process. Choose Letswork if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Aa when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: get_account_summary, get_loyalty_points_progress, get_profile_details.

Explore Aa Details

Choose Letswork when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: list_files, read_file, write_file.

Explore Letswork Details

Feature & Specification Comparison

Specification	A Aa Developer Tools	L Letswork Developer Tools
Summary
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Aa Tools (13)

get_account_summary

Name, AAdvantage #, mile balance, status, cobranded card, business memberships

get_loyalty_points_progress

LP YTD, last-year totals, tier thresholds, next-status delta

get_profile_details

DOB, partners list, sales city, mile expiration, million-miler stats

get_mile_activity

Mile/LP transaction history (date range, paginated, searchable)

get_upcoming_trips

Reservations with record locators

get_reservation_by_locator

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Aa Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aa": {
      "command": "uvx",
      "args": [
        "aa-mcp-server"
      ]
    }
  }
}

Letswork Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "letswork": {
      "command": "uvx",
      "args": [
        "letswork"
      ]
    }
  }
}

Frequently Asked Questions

Aa is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Letswork belongs to Developer Tools using local stdio subprocess. Select Aa when you need capabilities focused on developer tools and Letswork when you require tools for developer tools.