> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ascendgtm.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Amazon Q

> Use V5 Gateway tools in Amazon Q Developer and Q Business

## Prerequisites

* Amazon Q Developer (via AWS Console, IDE plugin, or CLI) or Q Business
* A V5 bearer token — get one from `POST /admin/tokens/issue`
* An IAM-compatible environment for Q Developer (AWS CLI configured)

## Amazon Q Developer (IDE plugin)

Amazon Q Developer supports MCP servers in its agentic mode (available in VS Code and JetBrains plugins).

<Steps>
  <Step title="Open Q Developer settings">
    In VS Code: **Command Palette** → **Amazon Q: Open Settings** → **MCP Servers**.
    In JetBrains: **Settings** → **Tools** → **Amazon Q** → **MCP Servers**.
  </Step>

  <Step title="Add V5 as MCP server">
    ```json theme={null}
    {
      "mcpServers": {
        "ascend": {
          "type": "http",
          "url": "https://ascend-gateway-v5.ascendgtm.workers.dev/mcp",
          "headers": {
            "Authorization": "Bearer <your-token>"
          }
        }
      }
    }
    ```
  </Step>

  <Step title="Verify">
    Ask Q Developer in the chat panel: *"Pull my HubSpot pipeline and give me the top 5 deals by amount."*

    Q should call `hubspot_crm` and return structured results.
  </Step>
</Steps>

## Amazon Q Business (enterprise)

Amazon Q Business uses "plugins" for external tool integrations. To connect V5:

1. Go to AWS Console → Amazon Q Business → your application → **Plugins**
2. Choose **Custom plugin** → **HTTP API**
3. Set the endpoint to `https://ascend-gateway-v5.ascendgtm.workers.dev/api/v1/{tenant}/{domain}`
4. Add an **Auth header** with your bearer token
5. Upload the OpenAPI schema from `GET /admin/openapi` on the gateway

The OpenAPI schema documents all available REST endpoints and input schemas.

## Notes

* Q Developer's agentic mode (inline suggestions + chat) both support MCP tools
* Q Business plugins use the REST API, not MCP — same tools, different protocol
* For AWS-native workflows, use the `aws_bedrock_invoke` or `aws_bedrock_converse` tools in V5 to call Bedrock models from within Q sessions