Home / MCP registry index / co.civai.nova/mcp-apple_developer

Apple Developer MCP by Nova (CIVAI)

co.civai.nova/mcp-apple_developer in the official MCP registry. Endpoint https://nova.civai.co/mcp/agents/mcp-apple_developer.

The registry describes it as: Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http mcp-apple-developer https://nova.civai.co/mcp/agents/mcp-apple_developer

{
  "mcpServers": {
    "mcp-apple-developer": {
      "url": "https://nova.civai.co/mcp/agents/mcp-apple_developer"
    }
  }
}

code --add-mcp '{"name":"mcp-apple-developer","type":"http","url":"https://nova.civai.co/mcp/agents/mcp-apple_developer"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

login session_status list_bundle_ids create_bundle_id delete_bundle_id list_asc_api_keys create_asc_api_key download_asc_api_key revoke_asc_api_key get_bundle_id list_apps list_app_bundles create_app_bundle create_app get_app update_app probe_update_version_localization update_version_localization get_testflight_public_link submit_testflight_beta_review list_builds submit_build_for_review upload_build set_version_build get_review_submission create_review_submission attach_review_item submit_build_and_press_submit press_submit_for_review submit_for_review list_review_messages distribute_build_to_testflight invite_testflight_testers list_asc_team_members invite_asc_team_member list_app_media_sets get_build get_review_path get_app_store_version update_app_info_localization upload_screenshot wait_build_processed set_export_compliance attach_build_and_compliance update_app_review_information set_age_rating set_app_store_metadata set_app_privacy delete_orphan_review_submissions get_pre_submit_status set_pricing_and_availability delete_screenshots upload_screenshots get_account_compliance_status start_browser_auth

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): 2ed5529ebb538d39. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/co-civai-nova-mcp-apple-developer/badge.svg)](https://lazaretto.dev/mcp-registry/co-civai-nova-mcp-apple-developer)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.