DEV Community

Cover image for How to Connect Remote MCP Tools to Claude Code
Germey
Germey

Posted on • Originally published at platform.acedata.cloud

How to Connect Remote MCP Tools to Claude Code

#ai #programming #devtools #tutorial

You are already using Claude Code in the terminal, but the moment you need a search result, an image, a short link, or a media asset, you leave the coding flow and start juggling browser tabs. MCP gives Claude Code a way to call external tools from the same terminal session.

This guide walks through a practical setup: connecting Ace Data Cloud's managed remote MCP servers to Claude Code with HTTP transport and an Authorization header, then using them as part of normal development work.

What you can do

Claude Code is already useful for coding, debugging, and refactoring. After adding MCP servers, it can also call specialized tools while you stay in the terminal. The documented Ace Data Cloud MCP set includes servers for:

  • music generation with Suno
  • image generation or editing with Midjourney, Flux, Seedream, and NanoBanana
  • video generation with Luma, Veo, and Seedance
  • web search with Serp
  • URL shortening with ShortURL

The important part is not that you add every tool. It is that the same pattern works for whichever servers match your workflow: an MCP server name, an HTTP URL, and an authorization header.

How it works

Each server is exposed as a remote MCP endpoint. Claude Code connects to it over HTTP using the claude mcp add command.

The basic shape is:

claude mcp add <name> --transport http <remote-mcp-url> \
  -H "Authorization: Bearer <TOKEN>"
Enter fullscreen mode Exit fullscreen mode

A concrete example for search:

claude mcp add serp --transport http https://serp.mcp.acedata.cloud/mcp \
  -H "Authorization: Bearer <TOKEN>"
Enter fullscreen mode Exit fullscreen mode

And another for short links:

claude mcp add shorturl --transport http https://shorturl.mcp.acedata.cloud/mcp \
  -H "Authorization: Bearer <TOKEN>"
Enter fullscreen mode Exit fullscreen mode

Two small details are easy to miss:

  1. --transport http tells Claude Code this is a remote HTTP MCP server.
  2. -H must be uppercase, because lowercase -h is commonly treated as help.

After adding servers, verify the setup:

claude mcp list
Enter fullscreen mode Exit fullscreen mode

You should see the servers you added listed as HTTP MCP servers.

Start with a small subset

It is tempting to connect everything at once, but I prefer starting with one or two tools that remove real friction.

For a technical writing workflow, I would begin with:

claude mcp add serp --transport http https://serp.mcp.acedata.cloud/mcp \
  -H "Authorization: Bearer <TOKEN>"

claude mcp add shorturl --transport http https://shorturl.mcp.acedata.cloud/mcp \
  -H "Authorization: Bearer <TOKEN>"
Enter fullscreen mode Exit fullscreen mode

Then, inside Claude Code, you can ask it to research current references, outline a post, and shorten the final links without leaving your terminal. That keeps the workflow narrow and debuggable: if something fails, you know which server to inspect.

For a visual workflow, add one image server instead:

claude mcp add flux --transport http https://flux.mcp.acedata.cloud/mcp \
  -H "Authorization: Bearer <TOKEN>"
Enter fullscreen mode Exit fullscreen mode

The documented image options include Midjourney, Flux, Seedream, and NanoBanana, so choose based on the kind of output you need rather than installing every option by default.

Use project config when the workflow belongs to the repo

For a team project, you can put MCP configuration in a .mcp.json file in the project root. The documented structure uses an mcpServers object, with each server containing type, url, and headers.

Here is a minimal version with search and short links:

{
  "mcpServers": {
    "serp": {
      "type": "http",
      "url": "https://serp.mcp.acedata.cloud/mcp",
      "headers": { "Authorization": "Bearer <TOKEN>" }
    },
    "shorturl": {
      "type": "http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": { "Authorization": "Bearer <TOKEN>" }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Do not commit a real token to a public repository. Either keep .mcp.json out of Git, let each teammate fill in their own token, or use an environment-variable based workflow in your local setup.

A real terminal workflow

Once configured, the most useful prompts are not vague ones like "use tools." They are small workflows with clear handoffs.

For example:

Search for recent AI video generation trends, summarize the useful engineering points, draft a technical blog outline, then shorten the final reference links.

That maps cleanly to the documented pattern: Serp handles search, Claude Code does the reasoning and writing, and ShortURL handles link cleanup.

For a media-heavy project, you could instead ask Claude Code to generate background music with Suno, create product showcase images with Midjourney, and then combine images into a video with Luma. The point is to make the tool chain explicit, so each step produces an artifact Claude Code can pass to the next step.

Troubleshooting checklist

If a server does not respond the way you expect, start with the boring checks:

claude mcp list
Enter fullscreen mode Exit fullscreen mode

Confirm the server is present and using HTTP transport. If needed, remove and re-add it with the same claude mcp add shape. Also check that the authorization header is exactly in this form:

Authorization: Bearer <TOKEN>
Enter fullscreen mode Exit fullscreen mode

If you use both a global Claude Code config and a project .mcp.json, remember that project-level configuration is intended for repo-specific workflows and can override personal defaults.

Closing thoughts

The best MCP setup is not the largest one. It is the one that removes a repeated context switch from your build loop. Start with one remote server, verify it with claude mcp list, and only add more when the workflow is stable.

The full Ace Data Cloud Claude Code MCP reference is here: https://platform.acedata.cloud/documents/claude-code-mcp-all

Top comments (0)