---
name: ansight-mcp-setup
description: Use this skill when configuring Ansight Studio as an MCP server for an AI client or developer workstation. Configure the local stdio bridge with ansight-daemon mcp-stdio for Codex, Cursor, Claude Code, or another MCP-capable client, preserve existing MCP configuration, use https://localhost:45125/mcp/ only as a fallback, verify the ansight server can be listed, and do not install an app SDK.
---

# Ansight MCP Setup Skill

Use this skill when a user wants an AI agent to configure workstation access to Ansight Studio through MCP.

Do not use this skill to install an Ansight SDK into an app. Use the platform install skills for app integration.

## Goal

Configure the user's AI client to reach the local Ansight Studio MCP server through the stdio bridge, keep the setup machine-local, verify the client can list the server, and report any manual restart or UI steps that remain.

## Required Constraints

- preserve existing MCP servers and client configuration
- prefer stdio with `ansight-daemon mcp-stdio`
- use the server name `ansight` unless the user explicitly asks for another name
- use user/global client configuration for machine-local helper paths unless the user asks for project-local setup
- do not commit workstation-specific MCP config to a shared repo unless the user explicitly requests it
- do not configure app pairing, app SDK packages, or runtime tool guards from this skill
- do not use direct HTTPS unless stdio is unavailable or unsupported
- for direct HTTPS fallback, use `https://localhost:45125/mcp/`, not `127.0.0.1`
- if TLS fails for direct HTTPS, prefer stdio or instruct the user to trust Ansight Studio's exported local certificate

## Workflow

1. Identify the AI client: Codex, Cursor, Claude Code, or another MCP-capable tool.
2. Confirm Ansight Studio is installed and running on the same desktop machine.
3. Locate the helper executable:
   - macOS: `/Applications/Ansight.app/Contents/Helpers/ansight-daemon`
   - Windows: `%LOCALAPPDATA%\Programs\Ansight\ansight-daemon.exe`
4. Inspect the client's existing MCP configuration or use the client's MCP CLI.
5. Add an `ansight` stdio MCP server that runs the helper with `mcp-stdio`.
6. Verify the server is registered with the client.
7. If the client can list MCP tools, confirm Ansight tools appear or explain that the client must be restarted.
8. Report the config path or CLI command used, verification result, and remaining manual steps.

## Codex

Prefer the CLI because Codex shares MCP configuration between the CLI and IDE extension.

macOS:

```bash
codex mcp add ansight -- /Applications/Ansight.app/Contents/Helpers/ansight-daemon mcp-stdio
codex mcp list
```

Windows:

```powershell
codex mcp add ansight -- "$env:LOCALAPPDATA\Programs\Ansight\ansight-daemon.exe" mcp-stdio
codex mcp list
```

Manual macOS config in `~/.codex/config.toml`:

```toml
[mcp_servers.ansight]
command = "/Applications/Ansight.app/Contents/Helpers/ansight-daemon"
args = ["mcp-stdio"]
```

Direct HTTPS fallback:

```bash
codex mcp add ansight --url https://localhost:45125/mcp/
```

## Cursor

Prefer global config because the Ansight helper path is workstation-specific.

macOS `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "ansight": {
      "command": "/Applications/Ansight.app/Contents/Helpers/ansight-daemon",
      "args": ["mcp-stdio"]
    }
  }
}
```

Windows:

```json
{
  "mcpServers": {
    "ansight": {
      "command": "C:\\Users\\<you>\\AppData\\Local\\Programs\\Ansight\\ansight-daemon.exe",
      "args": ["mcp-stdio"]
    }
  }
}
```

Use `.cursor/mcp.json` only when the user wants project-scoped setup and accepts the machine-specific path.

## Claude Code

macOS:

```bash
claude mcp add --transport stdio --scope user ansight -- \
  /Applications/Ansight.app/Contents/Helpers/ansight-daemon mcp-stdio
claude mcp get ansight
```

Windows:

```powershell
claude mcp add --transport stdio --scope user ansight -- `
  "$env:LOCALAPPDATA\Programs\Ansight\ansight-daemon.exe" mcp-stdio
claude mcp get ansight
```

Direct HTTPS fallback:

```bash
claude mcp add --transport http --scope user ansight https://localhost:45125/mcp/
```

## Generic MCP Clients

Use stdio when the client accepts command-based MCP servers:

```json
{
  "mcpServers": {
    "ansight": {
      "command": "/Applications/Ansight.app/Contents/Helpers/ansight-daemon",
      "args": ["mcp-stdio"]
    }
  }
}
```

If the client only supports HTTP MCP servers, configure:

```text
https://localhost:45125/mcp/
```

The client must run on the same desktop machine as Ansight Studio.

## Verification

Use the client's own list or get command first:

```bash
codex mcp list
claude mcp list
```

When the client can list tools, verify tools with names such as `ansight_query_apps`, `ansight_list_sessions`, or `ansight_list_app_tools` are available.

If tools do not appear:

- launch Ansight Studio and confirm the MCP panel reports the server is running
- restart the AI client after changing config
- check that the helper path exists
- use stdio if direct HTTPS fails with a certificate error
- keep the server name short and explicit, normally `ansight`

## Done Criteria

- the client has an `ansight` MCP server entry
- the entry uses `ansight-daemon mcp-stdio` unless stdio is impossible
- existing MCP configuration is preserved
- no app SDK integration was attempted
- verification command was run or the remaining manual verification step is listed
- final response names the client, config method, server name, and any restart needed