# Archera MCP Server

The Archera MCP Server connects your AI assistant to your Archera account using the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), giving it direct access to your cloud commitments, cost data, and optimization recommendations. Archera hosts and manages the remote MCP server with OAuth authentication.

**MCP server URL:** `https://mcp.archera.ai/mcp`

## Authentication

The Archera MCP Server uses OAuth Authorization Code with PKCE. MCP clients that support Dynamic Client Registration can register themselves automatically during setup.

Most clients start a browser-based Archera login when you connect to or start the MCP server. Claude Code is different: add the server first, then run `/mcp` inside Claude Code to authenticate.

If your MCP client asks you to manually provide a `client_id`, update the client or contact Archera support.

## Set up your client

Select your client below for setup instructions. All clients should connect to `https://mcp.archera.ai/mcp` and authenticate with your existing Archera login.

### Claude Code

Run the following command in your terminal:

```
claude mcp add --transport http --scope user archera https://mcp.archera.ai/mcp
```

Then open Claude Code and run:

```
/mcp
```

Select the `archera` server and follow the browser login flow. Once you approve access, the server is available in future Claude Code sessions. The `--scope user` flag makes the server available across projects; drop it if you want the server configured only for the current project.

### OpenAI Codex

Run the following command in your terminal:

```
codex mcp add archera --url https://mcp.archera.ai/mcp
```

Verify the server is configured:

```
codex mcp list
```

### Claude Desktop

Open Claude Desktop, then go to **Settings** -\> **Connectors**.

1. Click **Add connector** or **+** -\> **Add custom connector**.

2. If prompted for a connector type, choose **Custom** -\> **Web**.

3. Name the connector `Archera`.

4. Enter the connector URL: `https://mcp.archera.ai/mcp`

5. Click **Add**, then click **Connect** to authenticate with Archera.

### Cursor

Go to **Cursor** -\> **Settings** -\> **Cursor Settings** -\> **MCP** and add the server. You can also edit your `mcp.json` directly:

```
{
  "mcpServers": {
    "archera": {
      "type": "http",
      "url": "https://mcp.archera.ai/mcp"
    }
  }
}
```

### Gemini CLI

Run the following command in your terminal:

```
gemini mcp add archera https://mcp.archera.ai/mcp --transport http --scope user
```

### Cline

Open the Cline panel in VS Code, then open **MCP Servers** from the panel menu.

1. Select the **Remote Servers** tab.

2. Enter server name `archera`.

3. Enter server URL `https://mcp.archera.ai/mcp`.

4. Select **Streamable HTTP** as the transport type.

5. Click **Add Server**.

### Zed

Open the Agent Panel's settings view and click **Add Custom Server**, or add the server directly to your Zed settings:

```
{
  "context_servers": {
    "archera": {
      "url": "https://mcp.archera.ai/mcp"
    }
  }
}
```

### VS Code (GitHub Copilot)

Open the Command Palette with `CMD+Shift+P`, select **MCP: Add Server**, choose **HTTP**, and enter:

```
https://mcp.archera.ai/mcp
```

### Windsurf

Open the Cascade panel, select the **MCPs** icon, or go to **Windsurf Settings** -\> **Cascade** -\> **MCP Servers**. Add a custom MCP server with this configuration:

```
{
  "mcpServers": {
    "archera": {
      "serverUrl": "https://mcp.archera.ai/mcp"
    }
  }
}
```

### Warp

Go to **Settings** -\> **Agents** -\> **MCP servers** -\> **\+ Add** and select **Streamable HTTP or SSE Server (URL)**. Enter the following:

```
{
  "mcpServers": {
    "archera": {
      "url": "https://mcp.archera.ai/mcp"
    }
  }
}
```

### Amp

**VS Code Extension:** Add the server via the Amp VS Code extension settings, or update your `settings.json`:

```
"amp.mcpServers": {
  "archera": {
    "url": "https://mcp.archera.ai/mcp"
  }
}
```

## Example prompts

Once connected, try these prompts to get started:

### Visibility

- What commitment plans do I have active right now?
- Show me my Reserved Instance and Savings Plan coverage across all AWS accounts
- Which of my commitments are expiring in the next 60 days?
- What's my current on-demand spend versus committed spend?

### Analysis

- Where am I most over- or under-committed?
- Show me EC2 utilization and coverage for the past 30 days
- Which accounts have the lowest commitment coverage?
- Are there any unused reservations I should be aware of?

### Optimization

- What savings opportunities does Archera see for my environment?
- Generate a commitment plan recommendation for my production AWS account
- How much could I save by converting my top on-demand spend to Savings Plans?
- Compare my commitment efficiency this quarter versus last quarter.

## Available tools

The Archera MCP server gives your AI assistant access to:

- **Commitment management** View and manage your full portfolio of Reserved Instances, Savings Plans, and Archera Insured Commitments across all linked cloud accounts and services. Check status, term lengths, payment options, and renewal dates.
- **Coverage & utilization** Analyze how well your existing commitments are being used. Identify underutilized reservations, coverage gaps by service or region, and accounts where on-demand spend is higher than it should be.
- **Recommendations & planning** Generate commitment plans and savings recommendations based on your actual usage patterns. Model different scenarios, including term length, payment type, and coverage targets, to find the right balance of savings and flexibility for your organization.
- **Spend & forecasting** Query historical cost data broken down by account, service, region, or commitment type. Get projected spend estimates based on current commitments and usage trends.
- **Account management** View linked cloud accounts, their coverage summaries, and commitment activity across your Archera organization.

## Troubleshooting

- **Auth not completing in Claude Code** Run `/mcp` inside Claude Code, select the `archera` server, and choose the authentication option. If the browser does not open automatically, copy the URL from the terminal and paste it manually. If your client uses a local callback server, make sure the callback port is not blocked by a firewall or VPN.
- **Client asks for a client ID** Make sure your MCP client supports OAuth Dynamic Client Registration. If the client still requires a manually issued client ID, update the client or contact support@archera.ai.
- **Reconnecting or switching accounts** In Claude Code, type `/mcp`, select the `archera` server, and choose **Clear authentication**. Then re-run the setup command to trigger a fresh login.
- **Missing tools or data** Ensure your Archera account has the necessary permissions and that authentication completed successfully. Try disconnecting and reconnecting the MCP server.
- **Connection issues** Verify the server URL is correct: `https://mcp.archera.ai/mcp`. Check that your network can reach `mcp.archera.ai` and `api.archera.ai`.