How to Use the Amazon EventBridge Bus MCP in Claude Code

Q: What are the required parameters for sending an event to Amazon EventBridge Bus with Claude Code?

You need to provide the source, detail-type, and detail for the event. You can pass these as command-line flags. The detail can be a JSON string or you can use @- to read it from stdin, which is useful for piping.

Pipe events directly to your Amazon EventBridge Bus from any script or CI/CD job using Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Amazon EventBridge Bus MCP to Claude Code

Create your Vinkius account to connect Amazon EventBridge Bus to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Amazon EventBridge Bus with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Send Events from the Command Line

The `put_events` tool lets you send custom events to EventBridge right from your terminal. No SDKs, no wrestling with auth libraries. It's a single command to push an event. Integrate it into a shell script to report on a cron job's status. Or call it from a GitHub Action to signal a deployment has finished. You get a simple, reliable way to push events into your AWS environment from anywhere you can run a script.

Compose Headless Automation

This isn't about chatting with an agent; it's about headless execution. You can pipe data from another command directly into Claude Code to construct and send an event. It's a composable building block for your automation pipelines. For example: `cat build-log.json | claude mcp run amazon-eventbridge-bus-mcp put_events --source "ci.build" --detail-type "build-status" --detail @-`. This command reads a file and pipes its content as the event detail. It's designed for scripting.

A Secure MCP Server for Your CI/CD

You get one endpoint and one token from Vinkius. That's all you need to add to your environment secrets. This MCP Server handles the connection and is strictly scoped to a single EventBus, minimizing your security footprint. Forget about managing AWS keys in your CI runners. The MCP architecture abstracts that away. Your scripts just tell Claude Code what event to send, and Vinkius handles the secure connection to AWS on the backend. It's simpler and much safer.

Setup guide

Set up Amazon EventBridge Bus MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see amazon-eventbridge-bus-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Amazon EventBridge Bus transactions." It will automatically discover and invoke the available Amazon EventBridge Bus tools.

Terminal

claude mcp add --transport http amazon-eventbridge-bus-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Amazon EventBridge Bus MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "amazon-eventbridge-bus-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Amazon EventBridge Bus. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Amazon EventBridge Bus now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Amazon EventBridge Bus MCP in Claude Code

First, add your Vinkius MCP token as a secret in your repository. Then, in your workflow YAML, add a step to install Claude Code and run the `claude mcp run` command with the `put_events` tool, passing your event data as arguments.

You need to provide the `source`, `detail-type`, and `detail` for the event. You can pass these as command-line flags. The `detail` can be a JSON string or you can use `@-` to read it from stdin, which is useful for piping.

The EventBus is defined when the MCP Server is configured by its administrator on Vinkius, which includes the region. The server connects to that specific, pre-configured bus, so you don't have to specify the region in your command.

This method simplifies authentication. You use one Vinkius token instead of managing AWS access keys, secret keys, and session tokens in your CI/CD environment. The permissions are also narrowly pre-scoped, which improves security.

Your event data is passed through an ephemeral, zero-trust server instance and is never stored or logged. The `put_events` tool only touches the event payload you provide. The entire transaction is stateless, and the V8 Isolate sandbox ensures your process is completely isolated from others.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript