toolspoke
Start free

Sandboxed CLI

Infrastructure

Connect Claude to AWS

Inspect AWS identity, storage, compute, logs, and cost data using scoped IAM credentials. Toolspoke puts 11 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

ConnectView pricing
Connection
Sandboxed CLI
Authentication
Access keys
Actions exposed
11
Cost per call (typical)
5 credits
Adapter
Maintained by Toolspoke

Connected in three steps

  1. 1

    Install AWS

    Open the marketplace in your workspace, add AWS to the project your agents work in, and it appears on the gateway immediately.

  2. 2

    Connect the credential

    Authenticate with access keys. Where to get one, and what it has to be able to reach, is the next section.

  3. 3

    Point your agent at the gateway

    Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json
{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. AWS shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code

Run it in your project, then /mcp to sign in

claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop

Settings, then Connectors, then Add custom connector

https://toolspoke.com/mcp
Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project

{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex

~/.codex/config.toml

[mcp_servers.toolspoke]
url = "https://toolspoke.com/mcp"
VS Code

.vscode/mcp.json, or the MCP: Add Server command

{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What AWS asks for

Access keys. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Access key IDRequired
AKIA…
Secret access keyRequired
Secret access key
Session tokenOptional
Default regionOptional

What Claude can do in AWS

11 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads
10Reads
Writes
1Writes
Destructive
0Destructive

Reads

10

Fetches data and changes nothing.

  • whoami

    Return the account and IAM principal represented by these credentials.

  • list_buckets

    List S3 buckets owned by the account.

  • list_objects

    List objects in an S3 bucket, optionally under a prefix.

  • get_object

    Download an S3 object as text.

  • list_functions

    List Lambda functions in the configured region.

  • get_function

    Fetch one Lambda function's configuration.

  • list_log_groups

    List CloudWatch log groups.

  • filter_log_events

    Filter recent events in a CloudWatch log group.

  • describe_instances

    List EC2 instances and their current state.

  • get_cost_summary

    Return AWS Cost Explorer usage totals for a date range.

Writes

1

Creates or updates something on the other side.

  • invoke

    Invoke a Lambda function with a JSON event.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else
The 11 actions above are the whole of it. A call to any other name is refused before it reaches AWS rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes
This connector writes to AWS, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential
Toolspoke holds no access to AWS of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from AWS
Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in AWS. An agent has to ask.
It does not smooth over provider limits
Toolspoke does not retry, queue or back off around AWS's own rate limits. A call that AWS refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in AWS?

11 named actions: 10 that only read and 1 that write. They include whoami, list_buckets and list_objects. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the AWS connector need?

Access keys. The connector asks for access key id and secret access key, and optionally session token and default region. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the AWS connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 11 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the AWS connector not do?

The 11 actions above are the whole of it. A call to any other name is refused before it reaches AWS rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to AWS, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to AWS of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in AWS. An agent has to ask. Toolspoke does not retry, queue or back off around AWS's own rate limits. A call that AWS refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches AWS's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls AWS?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More infrastructure connectors

Browse all of them