Skip to main content
Get started
MCP serverConnect Claude Desktop
MCP server

Connect Claude Desktop

Let Claude help run your Aly workspace from the desktop app once you give it the right scoped key.

Add the Aly MCP server to claude_desktop_config.json so Claude can operate your workspace directly.

Claude Desktop reads MCP servers from a JSON config file. Add Aly there and Claude can operate your workspace directly — list sites, mutate products, fulfill orders, read analytics.

Prerequisites

  • Claude Desktop installed.
  • An Aly API key with the scopes you want Claude to use. Authentication covers the scope catalog.

1. Find your config file

OSPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

Create the file if it doesn't exist.

2. Add Aly to mcpServers

claude_desktop_config.jsonjson
{  "mcpServers": {    "aly": {      "type": "http",      "url": "https://aly.store/api/mcp",      "headers": {        "Authorization": "Bearer aly_..."      }    }  }}

Replace aly_... with the key from Settings → API keys. If you already have other MCP servers in the file, merge the aly entry into your existing mcpServers object.

3. Restart Claude Desktop

Quit and reopen Claude. The connection status is visible from the integration menu in the composer.

4. Verify

Ask Claude:

“List my Aly sites and tell me which one has the most products.”

Claude should call sites.list, then iterate through products.list per site, and answer with a summary. If you get a permissions error, check that your API key carries read:sites and read:content.

Treat the config like a secret
Your API key sits in plaintext in the config file. Don't commit it to a public repo, and don't paste the file contents anywhere. Revoke a leaked key immediately from Settings → API keys.

OAuth instead of an API key

If you're distributing an integration where each user installs it themselves, ship an OAuth client and have Claude Desktop use the OAuth token (also aly_oauth_*) in the same Authorization header. The server treats both kinds identically; only the issuance path differs. See Authentication.

Troubleshooting

  • Server doesn't appear in Claude's integration menu — JSON syntax error. Validate the file and restart.
  • 401 Unauthorized — Key revoked, expired, or wrong scopes. Mint a new one.
  • 403 Forbidden on a specific tool — The tool requires a scope your key lacks. Mint a new key with the needed scope or use the scope guide.
  • 429 Too Many Requests — You've hit the per-principal limit. Back off, then retry.
Updated

Was this page helpful?