Skip to content

Getting Started

Connect Ark MCP to your AI client, then ask it to create or understand media. Your client handles tool calls and starts the local server automatically. You do not need to keep a terminal open.

Start with Set Up Ark MCP. A terminal-capable coding agent can prepare the installation and client configuration with your permission. If your administrator already provides an endpoint, use Connect to a Shared Server and skip local setup.

The ark-mcp-setup skill guides installation and updates in the user’s preferred agent. It detects the current client where possible and asks when ambiguous, distinguishes Claude Code from Desktop and TRAE IDE from Work, and defaults to global/user-level MCP registration. Request project-only setup to change that scope.

The workflow selects the latest published stable GitHub release and stages a locked installation before changing client configuration. If no stable release is published, it asks before using a default-branch commit. Existing credentials, other MCP servers, and development checkouts are preserved.

This is an agent-executed workflow, not an unattended installer. Credential entry and some clients’ configuration UIs need user interaction. Verification checks startup and tool discovery without paid generation; provider key validity and account entitlement are not established by those local checks.

For local setup, enter the provider keys you need in the private file prepared for you. Never paste keys into chat or shared client configuration. Images and video use ModelArk; audio generation and speech-to-text use Seed Speech. You do not need every service.

Enable ark-seed in your client’s MCP settings. The saved configuration tells the client how to start Ark; a manual server-start command is not an additional user step. For a shared server, your administrator handles startup.

Ask your connected client:

Check my Ark connection with ark_list_models and ark_job_capabilities.
List the services and tools available to me. Do not generate, understand,
transcribe, upload, or submit jobs.

Confirm that the tools you need appear in actual results. Discovery makes no provider calls; it does not validate provider keys or account entitlement. See Troubleshooting if the connection or tools are missing.

Choose your client guide, then try Your First Tool Call. Copy an example prompt into your agent and describe the image or video you want. Developers can find exact JSON envelopes in the tool reference.

For clients that support skills, install the optional ark-mcp skill to give your agent workflow instructions. This is separate from connecting the MCP server.

Installing without an agent? Use Manual Installation. Developing or deploying the server? Use Transports, Background Execution, and Configuration. These are not prerequisites for ordinary use.