planmyreinvent.com
2026

Planning re:Invent with your AI agent

AWS now 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’re working on, compare sessions, and put together a schedule with time to get between venues.

This page shows you how to do that with Claude Code, Codex, or Kiro. The connection uses the AWS Events MCP server. MCP is the way your agent gets access to the event’s tools and data. Once it’s connected, you do the planning in your usual conversation with your agent.

You’ll need a re:Invent 2026 registration, your AWS Builder ID, and Claude Code, Codex, or Kiro installed on your computer.

Connect your agent to AWS Events

This adds the event tools to your agent. Choose the application you use:

Claude Code

Open your terminal and run this command. Then start a new Claude Code session.

Terminal
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.

~/.codex/config.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 open-source mcp-remote bridge to handle AWS’s sign-in callback. It runs on your computer and opens AWS sign-in in your browser. Complete sign-in on the same computer within three minutes. The configuration is shared by local Codex clients; see Codex MCP setup.

Kiro

In Kiro, open the command palette and choose Kiro: Open user MCP config (JSON). Add the configuration below, save the file, and reload the window. If you already have servers configured, add the awsevents entry inside your existing mcpServers object.

~/.kiro/settings/mcp.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.

Sign in with your AWS Builder ID

In your conversation with the agent, send this message:

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, you can continue here. Ask the agent to confirm that it can see re:Invent 2026 and read your schedule.

Tell your agent what you want to attend

Now you can talk through what you want from the event. Tell your agent what you’re working on, what you’d like to learn, and how busy you want your days to be. This prompt gives it a starting point:

Message to your agent

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 the conversation going as you look over the plan. You might ask for more hands-on workshops, a quieter afternoon, or a different session at the same venue. Your agent can revise the proposal with you.

If you get stuck

Sign-in isn’t completing? Check that the callback port and client ID match step 1. In Kiro, keep the redirect URI exactly as shown.

Codex timed out? Finish sign-in in the browser on the same computer, then restart Codex. Close any other client using callback port 8976 during sign-in. Run node --version in your terminal to check that Node.js is installed.

You’re signed in, but your schedule is unavailable? Check your event registration and that you’re using the right Builder ID.

A reservation didn’t save? Ask your agent to read your schedule again and check the result for that session. Availability and booking windows are controlled by AWS.

The AWS Events documentation has the current setup details and service behavior.