# Planning re:Invent with your AI agent

AWS lets you connect an AI assistant to the re:Invent session catalog and your attendee schedule. You can ask it to find talks about the things you are working on, compare sessions, and put together a schedule with time to get between venues.

This guide explains how to do that with Claude Code, Codex, or Kiro using the AWS Events MCP server. MCP is the connection that gives your agent access to the event's tools and data. After setup, planning happens in your conversation with the agent.

You will need a re:Invent 2026 registration, your AWS Builder ID, and Claude Code, Codex, or Kiro installed on your computer. Reading this guide is free and requires no account.

## 1. Connect your agent to AWS Events

### Claude Code

Run this in your terminal, then start a new Claude Code session:

```bash
claude mcp add --transport http --scope user awsevents \
  https://api.awsevents.com/mcp \
  --callback-port 8484 \
  --client-id 7vmom55m1qstvq8i71ph127bfq
```

### Codex

With Node.js 22 or newer installed, add this to `~/.codex/config.toml`. Keep your existing settings; if you already have an `awsevents` entry, replace just that entry. Then restart Codex.

```toml
[mcp_servers.awsevents]
command = "npx"
args = [
  "-y", "mcp-remote@0.14.3",
  "https://api.awsevents.com/mcp", "8976",
  "--host", "127.0.0.1",
  "--static-oauth-client-info",
  '{"client_id":"7vmom55m1qstvq8i71ph127bfq"}',
  "--static-oauth-client-metadata",
  '{"scope":"openid email events/access"}',
  "--authorize-param", "identity_provider=AWSBuilderID",
  "--auth-timeout", "180"
]
startup_timeout_sec = 180
```

This uses the third-party, open-source [mcp-remote bridge](https://github.com/punkpeye/mcp-remote) to handle AWS's required sign-in callback. It runs locally and stores authorization on your computer. Complete AWS sign-in in the browser on that same computer within three minutes. This configuration is shared by local Codex clients; see [Codex MCP setup](https://developers.openai.com/codex/mcp/). The bridge handles OAuth; sign in through its browser flow. Authentication through the attendee's account is required to verify schedule access.

### Kiro

Open the command palette and choose **Kiro: Open user MCP config (JSON)**. Add this configuration to `~/.kiro/settings/mcp.json`, save, and reload the window. If servers are already configured, merge the `awsevents` entry into the existing `mcpServers` object.

```json
{
  "mcpServers": {
    "awsevents": {
      "url": "https://api.awsevents.com/mcp",
      "oauth": {
        "clientId": "7vmom55m1qstvq8i71ph127bfq",
        "redirectUri": "http://127.0.0.1:8976",
        "oauthScopes": ["openid", "email", "events/access"]
      }
    }
  }
}
```

Keep the callback port and client ID as shown. AWS uses these values to complete sign-in.

## 2. Sign in with your AWS Builder ID

In your conversation with the agent, send:

```text
List AWS events.
```

Your client opens an AWS sign-in page when it starts or first connects. Sign in with the Builder ID associated with your event registration, then return to the conversation. If you already signed in while setting up Codex, continue here. Ask the agent to confirm that it can see re:Invent 2026 and read your schedule.

## 3. Tell your agent what you want to attend

Discuss what you are working on, what you want to learn, and how busy you want your days to be. This prompt gives the agent a starting point:

```text
Help me plan AWS re:Invent 2026 using the awsevents tools.

Read my current schedule, then ask me about my interests, experience, preferred session types, must-see talks, and time for breaks or meeting people.

Suggest an itinerary with no overlapping sessions and realistic travel time between venues. Explain why you picked each session and offer alternatives where useful.

Show me any favorites, reservations, cancellations, or personal-time blocks you propose. Make only the changes I approve. Afterwards, read my schedule again and tell me what was saved and what needs attention.
```

Keep refining the proposal in conversation. You can ask for more hands-on workshops, a quieter afternoon, or a different session at the same venue.

## If you get stuck

- If sign-in does not complete, check the callback port and client ID against step 1. Keep Kiro's redirect URI exactly as shown.
- If Codex times out, finish sign-in on the same computer and restart Codex. Close any other client using callback port 8976 during sign-in. Check Node.js with `node --version`.
- If your schedule is unavailable, check your event registration and that you are using the right Builder ID.
- If a reservation does not save, read the schedule again and check the result for that session. Availability and booking windows are controlled by AWS.

[Official AWS Events MCP documentation](https://docs.aws.amazon.com/events/latest/devguide/mcp-server.html) has current setup details and service behavior.

## When to use this guide

Use this guide to help a person connect a supported client, discover relevant re:Invent sessions, or prepare an itinerary. Plan My re:Invent provides instructions; AWS provides authentication, event data, and schedule operations. Read before proposing edits, get explicit approval for schedule changes, and verify per-session outcomes.

Updated 1 October 2026.

made with 🧡 by [mza](https://www.linkedin.com/in/themza)