Connect Your MCP Client with an API Key

The 101domain MCP Server supports token-based authentication using HTTP, allowing any MCP-compatible AI client to connect using an API key issued from your 101domain account.

This guide covers how to configure your client using mcp-remote (v0.1.38, the current stable release as of April 2026) — the standard bridge for connecting stdio-based AI clients to remote MCP servers over HTTP. Security best practices for credential management are covered throughout.

Prerequisites

Before you begin, ensure you have:

A 101domain account with API access enabled
Your 101domain API key (available from your account dashboard under API Settings)
Node.js 18 or higher (node -v to check) — required by mcp-remote
npx available (bundled with Node.js)
Reviewed Essential Security Practices for MCP Clients before proceeding

What is mcp-remote?

mcp-remote is an open-source bridge that translates between a local AI client's stdio transport and a remote MCP server running over HTTP. Most AI desktop apps and IDEs communicate with MCP servers via local subprocess (stdio), but the 101domain MCP Server is a hosted remote endpoint. mcp-remote sits between them: your AI client launches it as a local subprocess, and it handles the authenticated HTTP connection to the 101domain server on your behalf.

AI Client (Claude Desktop, Cursor, etc.)
        │  stdio (local subprocess)
        ▼
   mcp-remote@0.1.38
        │  HTTPS + Bearer Token
        ▼
  https://mcp.101domain.com

Important: Although mcp-remote is described by its authors as a "working proof-of-concept" it is widely distributed and the default open-source tool for the purpose it serves.

It exists as a bridge until MCP clients natively support authorized remote servers. Once your client adds native remote MCP support, you can remove it.

Need information on configuration with AI Clients? We’ve created some quick start guides for a range of what AI Clients. Get started at Configuration by AI Client.