Skip to content

yunIO MCP Integration with Amazon Q (Kiro)

This article shows how to integrate yunIO with an Amazon Q. Amazon Q is AWS’s generative AI assistant. It appears in the AWS console, IDEs such as Kiro, and the AWS documentation. Integrate the yunIO MCP server with Amazon Q to access SAP data without direct SAP access or transaction-code knowledge. You do not need SAP GUI experience.

About this Article

The depicted example uses the yunIO MCP server in combination with the Amazon Q CLI and the Kiro CLI as the MCP client. The operating system used to run the Amazon Q CLI and the Kiro CLI is Ubuntu. The commands used in this article can vary depending on your Linux OS.

About the CLIs:

  • Amazon Q on Linux relies on AWS infrastructure and primarily uses the command line (CLI) as part of AWS infrastructure.
  • Kiro is an AI-powered development environment (IDE) created by AWS. Kiro is also an Amazon Q MCP client that is required to register MCP servers locally and connect them to Amazon Q.

Prerequisites

Setup the MCP Client on Linux

To set up the MCP client on Linux:

  1. Install the Amazon Q CLI. For more information, see Amazon Q CLI Documentation: Installation:

    OS: Ubuntu
    curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

  2. Install the Kiro CLI. For more information, see Kiro CLI Documentation: Installation.

    OS: Ubuntu
    wget https://desktop-release.q.us-east-1.amazonaws.com/latest/kiro-cli.deb
sudo dpkg -i kiro-cli.deb
sudo apt-get install -f

  3. Connect your system to your AWS account (Amazon Q Builder ID or IAM Identity Center):

    kiro-cli login

    Note

    When using Ubuntu, make sure xdg-open is installed and working. The CLI uses this to open your browser for the login.

    sudo apt install xdg-utils

  4. If it does not exist, create a directory .kiro/settings in the Linux user's home directory. When using the Amazon Q Developer CLI instead of Kiro to communicate with the MCP server, create a directory .aws/amazonq.

    mkdir -p ~/.kiro/settings

  5. Inside the settings/ folder, create a new file mcp.json:

    touch ~/.kiro/settings/mcp.json

    Note

    To use the Amazon Q Developer CLI instead of Kiro for the communication with the MCP server, create a directory .aws/amazonq in the Linux user's home directory and create the mcp.json file there:

    mkdir -p ~/.aws/amazonq/
touch ~/.aws/amazonq/mcp.json

  6. Add the following content to the mcp.json file. For more information, see Kiro Documentation: MCP Configuration.

    mcp.json
    {
"mcpServers": {
    "yunio-mcp": { 
        "url": "https://yunio.example.com:8177/mcp(1)",
        "headers": {
            "Authorization": "Basic ZXhhbXBsZV9vbmx5OmRvX25vdF91c2U=(2)"
        },
        "disabled": false
    }
}
}
    1. Replace the example URL with the actual URL of your yunIO MCP server.
    2. Replace ZXhhbXBsZV9vbmx5OmRvX25vdF91c2U= with your own base64 encoded yunIO credentials in the format username:password.

    You can use the following terminal commands to write content to the mcp.json file:

    You can use the terminal command cat to write the content to the mcp.json file.

    • Overwrite the file content:

      cat << 'EOF' > ~/.aws/amazonq/mcp.json
<content>
EOF

    • Verify the file content:

      cat ~/.aws/amazonq/mcp.json

    You can use the Nano terminal-based text editor to populate the mcp.json file.

    • Open the file in the nano text editor:

      nano ~/.aws/amazonq/mcp.json

    • Paste the content.

    • Press Ctrl + O, then Enter to save the changes.
    • Press Ctrl + X to exit the editor.

  7. Start using the MCP server in the terminal:

    kiro-cli chat

Kiro now reads the mcp.json and connects to the yunIO MCP server.

Troubleshooting

  • Path errors: Ensure the file is named exactly mcp.json (lowercase) and located in the hidden folder .aws/amazonq/.

  • Connection test: Test the accessibility of the yunIO MCP server with:

    curl -I https://yunio.example.com:8177/mcp

    If the MCP server is not reachable, check if the MCP server is enabled in the Server Settings.

Last update: January 30, 2026
Written by: Christian Tauchmann, Valerie Schipka