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

# MCP server and text export

> Connect a coding agent to canonical documentation and retrieve pages as Markdown.

## Overview

The **ai-coustics documentation** is available through a Model Context Protocol (MCP) server. Connect an MCP-compatible tool to search the published site and retrieve pages while building your integration.

## Server URL

```text theme={null}
https://docs.ai-coustics.com/mcp
```

## What it exposes

The hosted server supports documentation search, page retrieval and documentation feedback. Search returns matching pages; retrieval reads page content; feedback reports a documentation issue. These tools do not process audio or manage your SDK account. See [Mintlify's search MCP documentation](https://www.mintlify.com/docs/ai/model-context-protocol) for the tool contract.

Do not include SDK keys, access tokens or private audio in searches or feedback. Use your client's approval controls before sending feedback.

## Read plain text

Use the [documentation index](https://docs.ai-coustics.com/llms.txt) to discover canonical pages. It lists Markdown URLs, such as the [SDK quickstart as Markdown](https://docs.ai-coustics.com/models/get-started/sdk-quickstart.md). You can also use the page's copy menu. Mintlify generates these exports from the published documentation; a local edit does not update the hosted index.

## Find the canonical answer

| Question | Source of truth |
| - | - |
| Which model fits my task? | [Model reference](/reference/sdk/models) and its model-specific guides |
| How do I configure an SDK key? | [Authentication](/models/get-started/authenticate-apps) and the selected binding's quickstart |
| What sample rate and frame size should I send? | [Audio format](/reference/concepts/audio-format) and the selected model's metadata |
| What data leaves the process? | [SDK telemetry](/reference/concepts/sdk-telemetry) and [OpenTelemetry](/models/get-started/opentelemetry) |
| How do I upgrade? | [Compatibility matrix](/reference/sdk/compatibility-matrix), [changelog](/changelog) and the migration guide for the installed version |
| Can I process local files? | [SDK examples](/reference/sdk/examples) and [Tyto batch analysis](/models/audio-insight/batch-call-analysis) |

Ask your tool to cite the page and state the package/model version it used. Historical migration examples apply to the versions in their titles. If search returns stale guidance, read the canonical page directly and check the changelog before changing code.

## Connect your tool

<Tabs>
  <Tab title="Claude">
    1. Go to [Settings → Connectors](https://claude.ai/settings/connectors)
    2. Click **Add custom connector**
    3. Name: `ai-coustics docs`, URL: `https://docs.ai-coustics.com/mcp`
    4. Click **Add**
    5. In a chat, click the attachments (+) button and select the connector
  </Tab>

  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http ai-coustics-docs https://docs.ai-coustics.com/mcp
    ```
  </Tab>

  <Tab title="Codex">
    Add the server to `~/.codex/config.toml`:

    ```toml theme={null}
    [mcp_servers.ai-coustics-docs]
    url = "https://docs.ai-coustics.com/mcp"
    ```
  </Tab>

  <Tab title="Cursor">
    Open the command palette → **Open MCP settings** → **Add custom MCP**, then add to `mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "ai-coustics-docs": {
          "url": "https://docs.ai-coustics.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Create `.vscode/mcp.json` and add:

    ```json theme={null}
    {
      "servers": {
        "ai-coustics-docs": {
          "type": "http",
          "url": "https://docs.ai-coustics.com/mcp"
        }
      }
    }
    ```
  </Tab>
</Tabs>

## Check the connection

Ask your tool to find the SDK quickstart and return its source URL, then compare the answer with that page. The MCP connection provides documentation access; SDK activation is separate.

If the tool cannot connect, confirm the exact HTTPS endpoint above and that your client supports remote HTTP MCP servers. If retrieval is unavailable, use the Markdown index and page exports. If an answer cites an old version, state your installed version and request the corresponding migration guidance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.