# FutureInfra MCP server

> Create and manage cloud servers, Docker apps, domains and DNS on FutureInfra from your AI assistant.

- Listing: https://mcp.tc/i/futureinfra
- Connect: use the server's own URL `https://futureinfra.ai/v1/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: FutureInfra
- Homepage: <https://futureinfra.ai/>

## About

FutureInfra is a Korean cloud provider. Its MCP server lets an assistant create and manage cloud servers, deploy Docker apps with an address and HTTPS, and search, register and configure domains and DNS. The same account also covers LLM routing and other AI services.

It runs as a hosted Streamable HTTP endpoint at https://futureinfra.ai/v1/mcp. Users sign in through a browser OAuth flow, or use a pk\_live\_ API key from the console passed as a Bearer header. Destructive operations need browser approval. Usage is billed per minute.

## What it can do

- Create and manage cloud servers
- Deploy Docker apps with an address and HTTPS
- Search and connect domains and DNS
- Check usage and balance
- Access LLM models through one key
- Scoped permissions with browser approval for destructive actions

## Example prompts

- "Deploy this project to FutureInfra and connect myshop.com"
- "Create a small cloud server with my SSH key"
- "Check whether example.io is available to register"
- "Launch n8n and give me the address"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http futureinfra https://futureinfra.ai/v1/mcp
```

2. Start Claude Code, type `/mcp`, pick **futureinfra** and choose **Authenticate**. A browser window opens for the FutureInfra sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **FutureInfra** and paste this URL:

```url
https://futureinfra.ai/v1/mcp
```

3. Click **Add**, then **Connect**, and sign in when FutureInfra asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=FutureInfra&connectorUrl=https%3A%2F%2Ffutureinfra.ai%2Fv1%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://futureinfra.ai/v1/mcp` and click **Add**.

3. Click **Connect** and sign in when FutureInfra asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://futureinfra.ai/v1/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to FutureInfra to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=futureinfra&config=eyJ1cmwiOiJodHRwczovL2Z1dHVyZWluZnJhLmFpL3YxL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "futureinfra": {
      "url": "https://futureinfra.ai/v1/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=futureinfra&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ffutureinfra.ai%2Fv1%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"futureinfra","type":"http","url":"https://futureinfra.ai/v1/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "futureinfra": {
      "type": "http",
      "url": "https://futureinfra.ai/v1/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "futureinfra": {
      "serverUrl": "https://futureinfra.ai/v1/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add futureinfra --url https://futureinfra.ai/v1/mcp
codex mcp login futureinfra
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.futureinfra]
url = "https://futureinfra.ai/v1/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http futureinfra https://futureinfra.ai/v1/mcp
```

Then, inside Gemini CLI, run `/mcp auth futureinfra` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "futureinfra": {
      "type": "http",
      "url": "https://futureinfra.ai/v1/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://futureinfra.ai/v1/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/futureinfra (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
