# Install and diagnose Aune in every agent client

Canonical human page: https://aune-homepage-chat.vercel.app/docs/clients
Canonical machine page: https://aune-homepage-chat.vercel.app/ai/client-install.md

Every client connects to the same Streamable HTTP endpoint and OAuth 2.1 contract. These diagnostics identify the exact client configuration, prove tool discovery and the sandbox booking lifecycle, and remove cached or revoked state without asking users to paste bearer tokens.

## Facts

- **Diagnostics contract:** aune_client_diagnostics_v1
- **Verified:** 2026-07-11
- **Endpoint:** https://aune-homepage-chat.vercel.app/mcp
- **Transport:** MCP Streamable HTTP
- **Authentication:** OAuth 2.1 Authorization Code + PKCE
- **Clients:** ChatGPT, Claude Code, Codex, Cursor, Visual Studio Code, Generic MCP client

## ChatGPT

Write-capable custom MCP use depends on the client's current workspace plan, admin policy, and beta availability. Verify entitlement before connector review.

Official client reference: https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-connectors-in-chatgpt-beta

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Verify: After any tool-schema change, recreate or republish the development app when ChatGPT still shows its previously approved frozen tool snapshot.
- Troubleshoot: Confirm the workspace plan and admin policy currently allow custom apps and write-capable MCP tools.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### ChatGPT installation

```text
Enable Developer mode, create a custom app in Workspace settings > Apps, and set the remote MCP server URL to https://aune-homepage-chat.vercel.app/mcp. Review and publish the app only after the sandbox write checks pass.
```

## Claude Code

Use the client-native remote HTTP configuration and let the client complete Aune OAuth in the browser on the first protected operation.

Official client reference: https://docs.anthropic.com/en/docs/claude-code/mcp

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Verify: Run claude mcp get aune, then use /mcp to authenticate or clear authentication.
- Troubleshoot: Run claude mcp get aune and claude mcp list before changing configuration.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### Claude Code installation

```bash
claude mcp add --transport http aune https://aune-homepage-chat.vercel.app/mcp
```

## Codex

Use the client-native remote HTTP configuration and let the client complete Aune OAuth in the browser on the first protected operation.

Official client reference: https://developers.openai.com/codex/mcp/

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Verify: Run codex mcp get aune and confirm the URL, enabled state, and OAuth resource.
- Troubleshoot: Run codex mcp get aune; use codex mcp logout aune followed by codex mcp login aune to renew authorization.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### Codex installation

```bash
codex mcp add aune --url https://aune-homepage-chat.vercel.app/mcp
codex mcp login aune
```

## Cursor

Use the client-native remote HTTP configuration and let the client complete Aune OAuth in the browser on the first protected operation.

Official client reference: https://docs.cursor.com/context/model-context-protocol

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Verify: Confirm Aune appears under Available Tools and complete Cursor's OAuth prompt on first protected use.
- Troubleshoot: Inspect .cursor/mcp.json or the global ~/.cursor/mcp.json and restart the Aune server from Cursor settings.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### Cursor installation

```json
{
  "mcpServers": {
    "aune": {
      "url": "https://aune-homepage-chat.vercel.app/mcp"
    }
  }
}
```

## Visual Studio Code

Use the client-native remote HTTP configuration and let the client complete Aune OAuth in the browser on the first protected operation.

Official client reference: https://code.visualstudio.com/docs/agent-customization/mcp-servers

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Verify: Use MCP: List Servers to inspect Aune, then Configure Tools in chat to verify the current tool set.
- Troubleshoot: Use MCP: Show Output and MCP: Reset Cached Tools before changing the server definition.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### Visual Studio Code installation

```json
{
  "servers": {
    "aune": {
      "type": "http",
      "url": "https://aune-homepage-chat.vercel.app/mcp"
    }
  }
}
```

## Generic MCP client

Use the client-native remote HTTP configuration and let the client complete Aune OAuth in the browser on the first protected operation.

Official client reference: https://modelcontextprotocol.io/specification/2025-06-18/basic/transports

- Verify: Connect to the exact HTTPS endpoint and complete browser OAuth when challenged.
- Verify: Verify initialize negotiates MCP protocol 2025-06-18 and tools/list includes search_home_service_booking_options.
- Verify: Run an anonymous sandbox option search without customer contact data or a street address.
- Verify: Before a write, verify the client shows the exact tool and arguments for user approval.
- Verify: Confirm only in sandbox, then verify booking_created, availability_checked, provider_selected, and booking.status=confirmed.
- Verify: Revoke the grant at /connected-apps and verify the next protected call fails.
- Troubleshoot: Preserve the MCP-Protocol-Version and Accept headers after initialize, and accept either JSON or SSE responses.
- Troubleshoot: Fetch /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server from the canonical origin.
- Troubleshoot: Remove cached tools after a contract update, reconnect, and compare tools/list with /docs/mcp.
- Troubleshoot: Do not paste an access token into chat or source control; restart the OAuth connection instead.
- Troubleshoot: Use the trace ID and stable problem code from a failed call; never copy customer PII into diagnostics.

### Generic MCP client installation

```bash
curl -X POST "https://aune-homepage-chat.vercel.app/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  --data '{"jsonrpc":"2.0","id":"init-1","method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"aune-diagnostic","version":"1.0.0"}}}'
```