Connect
Optimize
Secure
Live 66 Actions
AWS Lambda MCP Server
for AI Agents
Connect your AI agent to StackOne's AWS Lambda MCP server and give it 66 MCP tools out of the box. Auth, tool execution, and security all managed.
AWS Lambda MCP Server
Built by 
StackOne
StackOne 
Coverage
66 Agent Actions
Create, read, update, and delete across AWS Lambda — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your AWS Lambda MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every AWS Lambda tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.
Prompt Injection Defense →
Performance
Max Agent Context. Min Cost.
Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every AWS Lambda call.
Tools Discovery →What is the AWS Lambda MCP Server?
A AWS Lambda MCP server lets AI agents read and write AWS Lambda data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's AWS Lambda MCP server ships with 66 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.
All AWS Lambda MCP Tools
Every action from AWS Lambda's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Alias
- Create Alias
Create an alias for a Lambda function version
- Get Alias
Retrieve details about a Lambda function alias
- Update Alias
Update the configuration of a Lambda function alias
- Delete Alias
Delete a Lambda function alias
Code Signing Configs
- Create Code Signing Config
Create a code signing configuration that defines trusted publishers and a signing policy
- List Code Signing Configs
List the code signing configurations in the AWS account and region
- Get Code Signing Config
Retrieve a code signing configuration by ARN
- Update Code Signing Config
Update an existing code signing configuration
- Delete Code Signing Config
Delete a code signing configuration
Function Code Signing Configs
- Get Function Code Signing Config
Retrieve the code signing configuration associated with a function
- Delete Function Code Signing Config
Remove the code signing configuration from a function
Function Event Invoke Configs
- List Function Event Invoke Configs
List the asynchronous invocation configurations for a Lambda function
- Get Function Event Invoke Config
Retrieve the asynchronous invocation configuration for a function, version, or alias
- Update Function Event Invoke Config
Update the asynchronous invocation configuration for a function, version, or alias
- Delete Function Event Invoke Config
Delete the asynchronous invocation configuration for a function, version, or alias
Event Source Mappings
- Create Event Source Mapping
Create a mapping between an event source and a Lambda function
- List Event Source Mappings
List the event source mappings for a function or event source
- Get Event Source Mapping
Retrieve details about a single event source mapping
- Update Event Source Mapping
Update the settings of an existing event source mapping
- Delete Event Source Mapping
Delete an event source mapping identified by its UUID
Provisioned Concurrency Configs
- List Provisioned Concurrency Configs
List the provisioned concurrency configurations for a Lambda function
- Get Provisioned Concurrency Config
Retrieve the provisioned concurrency configuration for a function's alias or version
- Delete Provisioned Concurrency Config
Delete the provisioned concurrency configuration for a function
Functions
- Create Function
Create a Lambda function from a deployment package and execution role
- List Functions
List the Lambda functions in the AWS account and region
- Get Function
Retrieve information about a Lambda function or a specific version
- Delete Function
Delete a Lambda function or a specific version
Function Configurations
- Get Function Configuration
Retrieve the version-specific configuration settings of a Lambda function
- Update Function Configuration
Modify the version-specific configuration settings of a Lambda function
Function Concurrencys
- Get Function Concurrency
Retrieve the reserved concurrency configuration for a function
- Delete Function Concurrency
Remove the reserved concurrency limit from a function
Function URL Configs
- Create Function URL Config
Create a Lambda function URL with the specified configuration
- List Function URL Configs
List the Lambda function URLs configured for a function
- Get Function URL Config
Retrieve details about a Lambda function URL
- Update Function URL Config
Update the configuration for a Lambda function URL
- Delete Function URL Config
Delete a Lambda function URL
Layer Versions
- Publish Layer Version
Create a Lambda layer from a ZIP archive
- List Layer Versions
List the versions of a Lambda layer
- Get Layer Version
Retrieve information about a specific version of a Lambda layer
- Delete Layer Version
Delete a version of a Lambda layer
Layer Version Permissions
- Add Layer Version Permission
Grant another account or organization permission to use a Lambda layer version
- Remove Layer Version Permission
Remove a statement from the permission policy of a Lambda layer version
Permissions
- Add Permission
Grant a principal permission to use a Lambda function
- Remove Permission
Revoke function-use permission by removing a policy statement
Other (22)
- Publish Version
Publish an immutable version from the current function code and configuration
- Get Account Settings
Retrieve your Lambda account limits and usage in the AWS Region
- List Aliases
List the aliases for a Lambda function
- List Functions By Code Signing Config
List the functions that use the specified code signing configuration
- Get Runtime Management Config
Retrieve the runtime management configuration for a function's version
- Get Function Recursion Config
Retrieve a function's recursive loop detection configuration
- List Versions By Function
List the published versions of a Lambda function
- List Layers
List the Lambda layers in the AWS account and region
- Get Layer Version By Arn
Retrieve information about a Lambda layer version by its ARN
- Get Layer Version Policy
Retrieve the resource-based permission policy for a Lambda layer version
- Get Policy
Retrieve the resource-based IAM policy for a Lambda function
- List Tags
List the tags on a Lambda function, event source mapping, or code signing configuration
- Update Function Code
Update the code of a Lambda function from a package or container image
- Invoke Function
Invoke a Lambda function synchronously or asynchronously
- Put Function Code Signing Config
Attach a code signing configuration to a function
- Put Function Event Invoke Config
Configure asynchronous invocation for a function, version, or alias (overwrites existing config)
- Put Provisioned Concurrency Config
Add a provisioned concurrency configuration to a function's alias or version
- Put Runtime Management Config
Set the runtime management configuration for a function's version
- Put Function Recursion Config
Set a function's recursive loop detection configuration
- Put Function Concurrency
Set the reserved concurrency limit for a function
- Tag Resource
Add tags to a Lambda function, event source mapping, or code signing configuration
- Untag Resource
Remove tags from a Lambda function, event source mapping, or code signing configuration
Set Up Your AWS Lambda MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to AWS Lambda in under 10 lines of code.
Agent Frameworks
JSON{
"mcpServers": {
"stackone": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.stackone.com/mcp?x-account-id=<account_id>",
"--header",
"Authorization: Basic <YOUR_BASE64_TOKEN>"
]
}
}
}Platform Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
MCP vs A2A: Architecture, Security, and When to Use Each
MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.
12 min
MCP vs API: What 200+ Connector Builds Taught Us
MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.
14 min read
AWS Lambda MCP Server FAQ
Does StackOne have a AWS Lambda MCP server?
Yes. StackOne offers a hosted AWS Lambda MCP server with 66 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
AWS Lambda MCP server vs direct API integration — what's the difference?
A AWS Lambda MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling AWS Lambda. A AWS Lambda MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling AWS Lambda at runtime. StackOne provides both.
How does AWS Lambda authentication work for AI agents?
AWS Lambda authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own AWS Lambda account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are AWS Lambda MCP tools vulnerable to prompt injection?
Yes — AWS Lambda MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a AWS Lambda agent and how do I avoid it?
Context bloat happens when AWS Lambda tool schemas and API responses eat your AWS Lambda agent's memory, preventing it from reasoning effectively. A single AWS Lambda query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my AWS Lambda agent can access?
Yes — you can limit which actions your AWS Lambda agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my AWS Lambda MCP server?
Yes — you can create custom agent actions for your AWS Lambda MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research AWS Lambda's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a AWS Lambda MCP server?
Skip a AWS Lambda MCP server if your integration is purely software-to-software — direct AWS Lambda API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call AWS Lambda actions at runtime.
What AI frameworks and AI clients does the StackOne AWS Lambda MCP server support?
The StackOne AWS Lambda MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.