use_aws_mcp + OpenCode: Complete MCP Integration

use_aws_mcp is a MCP server that amazon-q-cli's use_aws tool extracted into independent mcp, for general aws api usage..

When integrated with OpenCode, you can:

• Access use_aws_mcp functionality through OpenCode

This guide provides step-by-step instructions to set up use_aws_mcp in OpenCode, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• use_aws_mcp will be fully integrated and operational
• You can use use_aws_mcp tools directly in OpenCode
• All use_aws_mcp capabilities will be available for your workflows

Prerequisites

Before starting, ensure you have:

• OpenCode installed and configured
• Compatible operating system (macOS, Linux, Windows)

Installation

Step 1: Install use_aws_mcp

Configuration

Step 2: Configure OpenCode

1. Locate your configuration file:

2. Add server configuration:

Configure MCP servers in your `opencode.json` or `opencode.jsonc`:

```json
{
  "mcp": {
    "my-mcp": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-everything"],
      "environment": {
        "API_KEY": "$API_KEY"
      },
      "timeout": 5000
    },
    "remote-server": {
      "type": "remote",
      "url": "https://mcp.example.com/sse",
      "headers": {
        "Authorization": "Bearer $API_TOKEN"
      }
    }
  }
}

Disable a server temporarily:

{
  "mcp": {
    "my-mcp": {
      "type": "local",
      "command": ["npx", "-y", "mcp-server"],
      "enabled": false
    }
  }
}

3. **Restart OpenCode**

Completely quit and restart OpenCode to load the new configuration.



## Examples

Once configured, you can use use_aws_mcp in OpenCode:



## Testing Your Setup

1. Run opencode in terminal
2. Add "use the mcp_name tool" to your prompts
3. Verify tool execution and response



## Troubleshooting

### Common Issues

#### MCP Server Not Loading

**Symptoms:** Server not appearing in tools, Timeout errors, Command not found

**Cause:** Invalid configuration, missing dependencies, or timeout too short

**Solution:**
- Verify command array is correct in opencode.json
- Check environment variables are set properly
- Increase timeout value if server takes longer to start
- Test MCP server command independently in terminal

#### Context Limit Exceeded

**Symptoms:** Context too large errors, Slow responses, Truncated output

**Cause:** Too many MCP servers adding to context

**Solution:**
- Disable unused MCP servers with enabled: false
- Use per-agent tool configuration to limit active MCPs
- Avoid MCP servers that add many tokens (e.g., GitHub MCP)

#### Remote Server Connection Failed

**Symptoms:** Cannot connect to remote MCP, Authentication errors

**Cause:** Invalid URL, missing headers, or network issues

**Solution:**
- Verify remote server URL is correct
- Check authorization headers are properly configured
- Ensure environment variables for tokens are set

#### use_aws_mcp not appearing in OpenCode

**Symptoms:** Server not listed, Tools not available

**Cause:** Configuration or installation issue

**Solution:**
- Verify configuration syntax
- Check use_aws_mcp installation
- Restart OpenCode
- Check logs for error messages



## Next Steps

Now that use_aws_mcp is integrated with OpenCode:

- Explore all use_aws_mcp capabilities through OpenCode
- Check out other MCP servers that work with OpenCode
- Join the MCP community for tips and support
- Consider contributing to use_aws_mcp development

## Need Help?

- Search for [use_aws_mcp documentation](https://www.mcpstack.org)
- Check the [OpenCode MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions