# FutureInfra MCP [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://futureinfra.ai/v1/mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/futureinfra-mcp

## Description
FutureInfra provides a hosted MCP server for Korean cloud infrastructure and AI APIs. Connect supported clients to cloud servers, Docker apps, domains and DNS, and AI APIs using browser OAuth or scoped Bearer authentication. Endpoint: https://futureinfra.ai/v1/mcp. Setup: https://futureinfra.ai/docs/mcp/. Currently in pilot operation; paid billing has not started.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation

## What FutureInfra MCP MCP server does

FutureInfra MCP MCP server provides hosted access to Korean cloud infrastructure and AI APIs through the endpoint `https://futureinfra.ai/v1/mcp`. Its supported service areas include cloud servers, Docker applications, domains, DNS, and AI APIs. The listing describes these as agent-accessible capabilities, but does not provide individual tool names or schemas.

This server fits workflows where an MCP-compatible client needs to connect to FutureInfra-managed infrastructure or API services. It is also relevant when the client should authenticate remotely instead of running an MCP server locally. The available scope depends on the account, authorization method, and services supported by FutureInfra.

## How it works

The server is hosted by FutureInfra, so clients connect to a remote MCP endpoint rather than launching a local process from a repository. The connection target is:

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

Two authentication approaches are documented: browser-based OAuth and scoped Bearer authentication. OAuth lets the client authorize through a browser. Bearer authentication uses a token with limited scope, where the permitted access is determined by the token configuration.

Once a supported client is connected and authorized, the server exposes access to the listed infrastructure and API categories. It should be selected for tasks involving FutureInfra services, not as a general-purpose interface to unrelated cloud providers.

## Setup and configuration

Use the FutureInfra MCP documentation for client-specific setup instructions:

`https://futureinfra.ai/docs/mcp/`

Configure the client with the hosted endpoint and one of the supported authentication methods. Browser OAuth may be appropriate for interactive client setup, while scoped Bearer authentication may suit a controlled token-based deployment.

The endpoint and authentication details are the relevant starting points for configuration.

## Limitations and notes

FutureInfra MCP MCP server is currently described as being in pilot operation. Paid billing has not started, according to the listing. Availability, supported services, authentication behavior, and access limits may therefore change during the pilot.

The listing does not name specific MCP clients, provide a license, enumerate tool definitions, or state detailed permission requirements. Confirm those details in the FutureInfra documentation before deploying an agent against production infrastructure.

_Full upstream README: https://allmcps.com/mcp/futureinfra-mcp/readme_

