AWS API (local)
BetaAWS Labs' server runs AWS CLI commands for the agent with the AWS profile on the developer's Mac. Unless it runs in read-only mode, it can change anything that profile can.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- uvx
- Platform
- macOS
- Publisher
- Amazon Web Services
How it works
Every agent request passes through Ferentin policy before it reaches AWS API (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with uvx awslabs.aws-api-mcp-server.
Ferentin's endpoint agent finds AWS API (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- AWS API (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About AWS API (local)
AWS Labs' server runs AWS CLI commands for the agent with the AWS profile on the developer's Mac. Unless it runs in read-only mode, it can change anything that profile can.
Frequently asked about AWS API (local)
- How do I connect AWS API (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add AWS API (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the AWS API (local) integration generally available?
- The AWS API (local) integration is currently beta on Ferentin.
Related integrations
3AWS Documentation (local)
AWS Labs' server for searching the public AWS documentation. It needs no AWS credentials.
Azure (local)
Microsoft's Azure MCP server queries and operates Azure resources with the identity the developer's Azure CLI session already holds.
Azure DevOps (local)
Microsoft's Azure DevOps server works with work items, repositories, pull requests, pipelines, wikis and test plans using the developer's own sign-in.