AWS MCP servers: documentation, costs and safe infrastructure questions

An AWS MCP server gives an MCP-capable assistant access to AWS documentation or selected AWS APIs, depending on the server you connect. The official awslabs/mcp repository contains specialized servers; the AWS Documentation MCP Server is the starting point for documentation questions. For account questions, use a dedicated read-only IAM role and restrict the available tools so an agent run cannot change production resources.

Guidance as of 30 Oct 2026. Browse related MCP servers for apps or start with what MCP means.

What it can do

Find documentation for a concrete engineering decision

The documentation server searches and reads AWS documentation. Ask it to find the documentation relevant to a proposed event-processing design, return the source links, and separate documented behavior from assumptions. This retrieves reference context; it does not inspect your deployed account. Its documented capabilities are listed in the official server guide.

A useful request includes the service, deployment region and the decision you need to make. Request the relevant passage and its URL before asking for a recommendation. You should be able to open the page and verify the reasoning yourself.

Separate a price estimate from your bill

The AWS Pricing MCP Server retrieves generally available pricing rather than account-specific spending. It also supports cost reports and analysis of infrastructure projects. For a proposed architecture, ask for itemized assumptions about usage, region and billing units. Treat the result as a scenario to review.

The AWS Billing and Cost Management MCP Server can analyze account cost and usage through the caller's credentials. A suitable question is to compare spending by service across equivalent reporting periods, with the filters shown. Neither an unexplained total nor a suggested optimization is authorization to alter infrastructure or purchase a commitment.

Which servers are read-only?

Assess the configured server and its tools, rather than assuming every entry in awslabs/mcp has the same permissions. As of 30 Oct 2026:

The Serverless guide includes an example that enables both write and sensitive-data access. Review its arguments before reusing it. The repository also points new production projects toward Agent Toolkit for AWS; check that current guidance before choosing a deployment path. Repository guidance.

How to connect it safely

1. Define the permitted result. Begin with a documentation summary or a cost comparison. Record the account, region, reporting period and permitted data. Make the output a report for human review. Exclude deployment, deletion, access-policy changes and purchases from this run.

2. Start with documentation context. Follow the official documentation-server README for runtime prerequisites. Its Unix launch recipe is uvx awslabs.aws-documentation-mcp-server@latest; Windows has a separate recipe. Review the package and launch command before starting it. Record the release used if you need to reproduce the setup.

3. Add it to the intended editor client. In an MCP-capable VS Code session, run MCP: Add Server, choose Command (stdio) and enter the publisher's launch command. Select the configuration destination for your client. Review prompts, enable only the intended tools, then inspect a completed documentation call. Follow the VS Code connection instructions; the MCP in VS Code guide provides broader context.

4. Add account access only when needed. Have your AWS administrator prepare a dedicated role with the minimum permissions for the approved queries. AWS recommends temporary credentials and least privilege in its IAM best practices. Use an explicitly selected profile where supported. Keep administrator credentials out of this server process and credentials out of chat or committed configuration.

5. Apply both permission boundaries. Limit IAM permissions and the client's available tools. For Serverless, preserve the read-only default and leave sensitive-data access disabled unless separately authorized. For Billing, select the relevant query permissions instead of copying the full feature list. Have the administrator validate the policy; an instruction in a prompt cannot enforce it. See the MCP security checklist.

6. Verify a bounded request. Ask for a documentation URL first, then an approved account query if required. Check the actual tool output, account scope and filters. Confirm the effective role permissions separately. Keep unrelated shell and deployment tools unavailable during the session, and retain the reviewed configuration with the report.

When this does not work

The answer needs live account evidence. Documentation alone cannot establish which resources you deployed. Ask the assistant to mark missing evidence rather than turning reference material into an inventory claim.

A report lacks its assumptions. A pricing query cannot establish your actual bill. Require usage assumptions for estimates and explicit reporting periods and filters for account comparisons.

Authentication or access fails. Check the selected profile, credential validity and required permissions in the server's current documentation. Do not solve a denied query by granting administrator access.

The server starts but no tool runs. Inspect client tool availability and server output. VS Code's verification procedure requires an actual successful tool call; a plausible answer is insufficient evidence.

Read-only data is still sensitive. Agree which account details may leave the environment before sending results to an assistant. Review the data-flow guidance and the differences between remote and local MCP servers.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension provides an editor entry for Tvijo tasks. Use selected, sanitized documentation and approved query results as context for a bounded explanation. Review the installed build's modes and file or command permissions. See editor installation.

TvijoCode is described as a test build with the extension embedded. Tvijo MCP makes Tvijo callable by a compatible MCP client for consultation; it does not automatically connect the Tvijo editor to AWS tools. The MCP release status distinguishes published consultation from prepared diff review awaiting package publication. Editor MCP integration and safe delegation remain planned work.

Scope an AWS connection separately: documentation context, a dedicated read-only IAM role where account access is necessary, and no production changes from an agent run. The editor and a consultation response do not replace AWS permission controls.

The Tvijo workspace shows the Try plan at $0 as of 30 Oct 2026: up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown as $10 and requests prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated; an order is not a charge. These terms describe Tvijo usage, not AWS account charges.

FAQ

Is awslabs/mcp one universal AWS server?

It is a collection of specialized servers. Choose the component that matches the question and inspect its permissions before connecting it. The repository is the starting index.

Can the AWS documentation server inspect my account?

Its documented tools retrieve documentation, rather than account inventory. Use an appropriately scoped account-connected server when the answer requires live account data. See the documentation tool list.

Does read-only mean the whole workflow is free?

No. AWS Pricing documents its pricing API calls as free of charge, as of 30 Oct 2026. That statement does not price the assistant, hosting or other APIs; check each service's current terms. AWS Pricing server documentation.

AWS is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.