Documentation

Claude Code

Add Milkey to Claude Code through the built-in `claude mcp add` workflow.

Claude Code is a strong fit for Milkey when you want an MCP-enabled CLI workflow and a quick path from API key to available tools.

The recommended setup is to register Milkey through `claude mcp add` so Claude Code manages the server entry for you.

Configure Claude Code

The client-specific work here is mostly about where the config lives and which field names the client expects.

Run the setup command from any terminal where `claude` is available.
Use `--scope user` for a personal install. Choose a project scope if you want the config tied to a single workspace.

Terminal

1claude mcp add --scope user \2  --transport http \3  --header "Authorization: Bearer mk_sk_your_api_key_id_your_secret" \4  milkey https://mcp.vexelityai.com/mcp

Authorization

Claude Code stores the Milkey Bearer header as part of the MCP server definition. Use a unique key per machine or per team-owned automation environment.

Shared auth model

Every MCP client page uses the same Milkey auth contract: Authorization: Bearer <api_key>. Keep the setup snippet on this page for copy-paste speed, then use the dedicated Authorization and API Keys pages for storage, rotation, and error handling rules.

Verify the connection

Run `claude mcp list` and confirm the `milkey` server shows as connected.
If the server does not appear immediately, restart the terminal session or rerun the setup command with the correct header.
Test with a concrete prompt that should require live skill resolution.

Test prompt

1Use Milkey to resolve the best database optimization skill for this repository and tell me which implementation steps matter first.

Operational tips

Claude Code is often used heavily in terminal workflows, so a dedicated key makes revocation cleaner if a workstation is replaced.
If you update the key, rerun the `claude mcp add` command so the stored header is refreshed.