audit_play_app_owner — ShipASO MCP Tool
audit_play_app_owner
(audit play app owner) is one of 12 tools on the
ShipASO
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call audit_play_app_owner from your client
- Claude Code ShipASO audit_play_app_owner run in your project directory
- Claude Desktop ShipASO audit_play_app_owner ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ShipASO audit_play_app_owner ~/.cursor/mcp.json
- VS Code ShipASO audit_play_app_owner .vscode/mcp.json
- Zed ShipASO audit_play_app_owner ~/.config/zed/settings.json
- Windsurf ShipASO audit_play_app_owner ~/.codeium/windsurf/mcp_config.json
- Cline ShipASO audit_play_app_owner ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ShipASO audit_play_app_owner ~/.gemini/settings.json
- Grok ShipASO audit_play_app_owner .mcp.json (in your project root)
- ChatGPT ShipASO audit_play_app_owner Settings → Connectors → Advanced → Developer mode
- Claude.ai ShipASO audit_play_app_owner Settings → Connectors → Add custom connector
- LangChain ShipASO audit_play_app_owner pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http shipaso https://api.shipaso.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.