# Amazon EventBridge Bus MCP for AI Agents AI Agent Connect > Amazon EventBridge Bus MCP. It lets your AI agent send events to a specific AWS EventBridge Bus without giving it broad AWS permissions. It's built for secure, event-driven workflows where your agent needs to trigger downstream actions like Lambda functions or webhooks. ## Overview - **Category:** industry-titans - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_EJsR41kflFjj09HRgMFBXTMCKvAuFVuhHgBcOdPN/ai-agent-connect - **Tags:** event-driven, aws, serverless, message-bus, orchestration, security-scoping ## Description The Amazon EventBridge Bus MCP gives your AI agent a dedicated way to push events to a single AWS bus. Most people worry about giving an AI agent too much power over their cloud account, but this tool solves that by sticking to the principle of least privilege. Instead of wide-open permissions, your agent gets a narrow lane to dispatch specific payloads. You can use it to kick off complex workflows, like starting a data processing job or notifying a third-party service. It's a core piece of infrastructure for anyone building event-driven systems who needs their agent to act as a reliable message producer. You can find this and other high-quality connections in the Vinkius catalog to keep your agent's capabilities scoped and secure. ## Tools ### put_events Sends custom JSON events to your chosen bus. It lets your agent trigger downstream actions like Lambdas or webhooks with specific metadata. ## Prompt Examples **Prompt:** ``` Tell the system to start the daily data sync. ``` **Response:** ``` I've dispatched the **DataSyncStarted** event to your EventBridge Bus. Your ETL pipeline should begin processing the latest batch now. ``` **Prompt:** ``` Notify the team that the backup finished. ``` **Response:** ``` Done. I've put a **BackupCompleted** event into the bus. This will trigger the notification webhook you have set up. ``` **Prompt:** ``` Trigger the user onboarding flow for ID 550. ``` **Response:** ``` I've sent the **UserOnboarding** event with the user ID 550. The downstream Step Function will now handle the account setup. ``` ## Capabilities ### Dispatch custom JSON events Send specific payloads to trigger AWS Lambda functions. ### Start Step Function executions Trigger complex workflows via EventBridge rules. ### Trigger third-party webhooks Let your agent notify external services with custom data. ### Send Source and DetailType metadata Attach specific identifiers to every event for better tracking. ### Maintain zero-trust security Keep your AWS account safe by scoping access to a single bus. ## Use Cases ### Triggering a data cleanup An engineer tells the agent to start the nightly cleanup, and the agent uses put_events to fire a Lambda. ### Notify the team that the backup finished A customer service agent confirms a sign-up and sends a UserCreated event to trigger a welcome email sequence. ### Automated auditing A security pro asks the agent to run the audit, which puts an AuditStarted event into the bus for the pipeline to pick up. ### Webhook notifications A developer wants the agent to notify a Slack channel when a file is uploaded, using the bus to hit a webhook. ## Benefits - Strict security with the Amazon EventBridge Bus MCP because it limits your agent to a single bus instead of your whole AWS account. - Faster workflow execution by using put_events to trigger Step Functions immediately. - Better observability since every event sent via put_events includes specific Source and DetailType tags. - Reduced risk of accidental deletions because the Connector doesn't have permissions to delete or modify your infrastructure. - Simplified integration for third-party webhooks by letting the agent handle the JSON payload construction. ## How It Works The bottom line is you get a secure, one-way bridge for your agent to trigger AWS workflows without opening up your entire cloud account. 1. Connect your MCP-compatible client to the Amazon EventBridge Bus MCP. 2. Provide the ARN for the specific EventBus you want the agent to access. 3. Ask your agent to trigger an action, and it'll handle the event dispatch. ## Frequently Asked Questions **Can the Amazon EventBridge Bus MCP trigger my AWS Lambda functions?** Yes, it does exactly that. By sending an event to the bus, it triggers any Lambda or Step Function you've already associated with that bus's rules. **Is the Amazon EventBridge Bus MCP safe for production?** Yes, it's designed for security. It follows the principle of least privilege by only allowing the agent to put events on one specific bus, rather than giving it full access to your AWS account. **How does the Amazon EventBridge Bus MCP handle different types of data?** You can send custom JSON payloads. The agent will format the data into the correct DetailType and Source fields so your downstream services can read it easily. **Can I use the Amazon EventBridge Bus MCP to trigger third-party webhooks?** Absolutely. If you have an EventBridge rule set up to hit a URL, this Connector provides the trigger to start that process. **Does the Amazon EventBridge Bus MCP work with my existing AWS setup?** Yes, as long as you have an EventBridge Bus already configured. You just need to point the Connector to that specific bus. **What happens if my agent sends a malformed event?** The Connector handles the dispatch. If the JSON doesn't meet the requirements of your bus rules, the AWS service will catch it, keeping your architecture stable. **Why limit the agent to a single bus?** To enforce zero-trust security. An autonomous agent shouldn't be able to inject events into arbitrary event buses across your organization. **Can the agent receive events with this tool?** No. EventBridge is designed for routing. To receive events back to an agent, you should route the EventBridge Rule to an SQS Queue and use the Amazon SQS Queue MCP. **What is the 'default' bus?** Every AWS account has a 'default' event bus. If you haven't created a custom bus, you can simply type 'default' during configuration.