Skip to main content

Expose AWS budgets API operations to AI agents via MCP server

Workflow preview

Workflow preview
100%
Expose AWS budgets API operations to AI agents via MCP server preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...

Best for

  • DevOps automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.httprequesttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Ashby.

Original n8n.io source

1.1 Workflow description

Title
Expose AWS budgets API operations to AI agents via MCP server
Workflow name
Expose AWS budgets API operations to AI agents via MCP server

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?

Join the community

Complete MCP server exposing 23 AWS Budgets API operations to AI agents.

⚑ Quick Setup

  1. Import this workflow into your n8n instance
  2. Credentials Add AWS Budgets credentials
  3. Activate the workflow to start your MCP server
  4. Copy the webhook URL from the MCP trigger node
  5. Connect AI agents using the MCP URL

πŸ”§ How it Works

This workflow converts the AWS Budgets API into an MCP-compatible interface for AI agents.

β€’ MCP Trigger: Serves as your server endpoint for AI agent requests β€’ HTTP Request Nodes: Handle API calls to https://budgets.amazonaws.com β€’ AI Expressions: Automatically populate parameters via $fromAI() placeholders β€’ Native Integration: Returns responses directly to the AI agent

πŸ“‹ Available Operations (23 total)

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Createbudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.CreateBudget:

Creates a budget and, if included, notifications and subscribers.

<important>

Only one of BudgetLimit or PlannedBudgetLimits can be present in the syntax at one time. Use the syntax that matches your case. The Request Syntax section shows the BudgetLimit syntax. For PlannedBudgetLimits, see the Examples section.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Createbudgetaction (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.CreateBudgetAction: Creates a budget action.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Createnotification (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.CreateNotification: Creates a notification. You must create the budget before you create the associated notification.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Createsubscriber (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.CreateSubscriber: Creates a subscriber. You must create the associated budget and notification before you create the subscriber.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Deletebudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DeleteBudget:

Deletes a budget. You can delete your budget at any time.

<important>

Deleting a budget also deletes the notifications and subscribers that are associated with that budget.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Deletebudgetaction (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DeleteBudgetAction: Deletes a budget action.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Deletenotification (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DeleteNotification:

Deletes a notification.

<important>

Deleting a notification also deletes the subscribers that are associated with the notification.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Deletesubscriber (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DeleteSubscriber:

Deletes a subscriber.

<important>

Deleting the last subscriber to a notification also deletes the notification.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudget:

Describes a budget.

<important>

The Request Syntax section shows the BudgetLimit syntax. For PlannedBudgetLimits, see the Examples section.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetaction (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetAction: Describes a budget action detail.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetactionhistories (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetActionHistories: Describes a budget action history detail.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetactionsforaccount (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetActionsForAccount: Describes all of the budget actions for an account.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetactionsforbudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetActionsForBudget: Describes all of the budget actions for a budget.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetnotificationsforaccount (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetNotificationsForAccount: Lists the budget names and notifications that are associated with an account.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgetperformancehistory (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgetPerformanceHistory: Describes the history for DAILY, MONTHLY, and QUARTERLY budgets. Budget history isn't available for ANNUAL budgets.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describebudgets (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeBudgets:

Lists the budgets that are associated with an account.

<important>

The Request Syntax section shows the BudgetLimit syntax. For PlannedBudgetLimits, see the Examples section.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describenotificationsforbudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeNotificationsForBudget: Lists the notifications that are associated with a budget.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Describesubscribersfornotification (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.DescribeSubscribersForNotification: Lists the subscribers that are associated with a notification.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Executebudgetaction (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.ExecuteBudgetAction: Executes a budget action.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Updatebudget (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.UpdateBudget:

Updates a budget. You can change every part of a budget except for the budgetName and the calculatedSpend. When you modify a budget, the calculatedSpend drops to zero until Amazon Web Services has new usage data to use for forecasting.

<important>

Only one of BudgetLimit or PlannedBudgetLimits can be present in the syntax at one time. Use the syntax that matches your case. The Request Syntax section shows the BudgetLimit syntax. For PlannedBudgetLimits, see the Examples section.

</important>

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Updatebudgetaction (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.UpdateBudgetAction: Updates a budget action.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Updatenotification (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.UpdateNotification: Updates a notification.

πŸ”§ #X-Amz-Target=Awsbudgetservicegateway.Updatesubscriber (1 endpoints)

β€’ POST /#X-Amz-Target=AWSBudgetServiceGateway.UpdateSubscriber: Updates a subscriber.

πŸ€– AI Integration

Parameter Handling: AI agents automatically provide values for: β€’ Path parameters and identifiers β€’ Query parameters and filters β€’ Request body data β€’ Headers and authentication

Response Format: Native AWS Budgets API responses with full data structure

Error Handling: Built-in n8n HTTP request error management

πŸ’‘ Usage Examples

Connect this MCP server to any AI agent or workflow:

β€’ Claude Desktop: Add MCP server URL to configuration β€’ Cursor: Add MCP server SSE URL to configuration β€’ Custom AI Apps: Use MCP URL as tool endpoint β€’ API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

β€’ Zero Setup: No parameter mapping or configuration needed β€’ AI-Ready: Built-in $fromAI() expressions for all parameters β€’ Production Ready: Native n8n HTTP request handling and logging β€’ Extensible: Easily modify or add custom logic

> πŸ†“ Free for community use! Ready to deploy in under 2 minutes.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Setup Instructions

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Workflow Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - AWS Budgets MCP Server

Type / Role
@n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices
Version 1

Block 4 - Creates a budget and, if included, notifications a

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 5 - Grid Note 1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Creates a budget action.

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 7 - Grid Note 2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Creates a notification. You must create the budget

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 9 - Grid Note 3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Creates a subscriber. You must create the associat

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 11 - Grid Note 4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Deletes a budget. You can delete your budget at an

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 13 - Grid Note 5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Deletes a budget action.

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 15 - Grid Note 6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Deletes a notification. Deleting a notification al

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 17 - Grid Note 7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Deletes a subscriber. Deleting the last subscriber

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 19 - Grid Note 8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Describes a budget. The Request Syntax section sho

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 21 - Grid Note 9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Describes a budget action detail.

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 23 - Grid Note 10

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Describes a budget action history detail.

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Showing the first 24 of 49 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Expose AWS budgets API operations to AI agents via MCP server
Complexity advanced
Nodes 49
Categories DevOps, AI Chatbot
Author David Ashby
Published 01 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5499/5499.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Expose AWS budgets API operations to AI agents via MCP server do?

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps, AI Chatbot use case.