> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Expose CloudThinker's cloud-ops tools and data to external MCP-compatible AI clients like Claude Desktop, Cursor, and Windsurf

<Note>
  **Preview** — The CloudThinker MCP server is in early access. The tool surface and transport options may change before general availability. [Contact us](https://cloudthinker.io/contact) to join the preview.
</Note>

CloudThinker can act as a [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server, letting any MCP-compatible AI client call CloudThinker tools and read CloudThinker data using your workspace's authenticated context.

This is the inverse of the existing [MCP connection](/guide/connections/mcp), which lets CloudThinker agents call *your* external MCP servers.

***

## What it enables

| Capability            | Description                                                                                         |
| --------------------- | --------------------------------------------------------------------------------------------------- |
| Cloud Ops in Your IDE | Query AWS, GCP, Azure inventory and costs from Cursor, Claude Desktop, or any MCP client            |
| Use Your Connections  | Reach databases, Kubernetes clusters, and observability tools you already connected to CloudThinker |
| Run Skills Remotely   | Invoke your workspace [skills](/guide/skills/overview) from any MCP-compatible host                 |
| Shared Context        | Read recommendations, dashboards, and incident memory the same way the web console does             |

***

## Exposed tools

The MCP server surfaces a curated subset of agent capabilities:

| Tool family         | What it does                                                                         |
| ------------------- | ------------------------------------------------------------------------------------ |
| `resources.*`       | Query the unified [resource inventory](/guide/infrastructure/resources) and topology |
| `recommendations.*` | List, accept, dismiss, or comment on optimization recommendations                    |
| `costs.*`           | Run cost queries and forecasts across cloud accounts                                 |
| `incidents.*`       | Create incidents, attach signals, and read RCA results                               |
| `dashboards.*`      | Read built-in and custom dashboards                                                  |
| `skills.*`          | Execute workspace skills with parameters                                             |

The exact tool list is exposed through MCP discovery — clients see whatever the workspace API key is permitted to use.

***

## Transports

| Transport      | Best For                                                                                  |
| -------------- | ----------------------------------------------------------------------------------------- |
| **HTTP + SSE** | Cloud-hosted clients, remote agents, and team-shared setups                               |
| **stdio**      | Local IDEs and desktop apps (Claude Desktop, Cursor, Windsurf) launched via a local proxy |

***

## Authentication

The MCP server authenticates with the same workspace [API keys](/guide/api/overview) used by the REST API. The key is scoped to a single workspace and inherits the role of the issuing member.

***

## Related

<CardGroup cols={2}>
  <Card title="MCP Connection" icon="link" href="/guide/connections/mcp">
    Connect external MCP servers as CloudThinker tools
  </Card>

  <Card title="API" icon="code" href="/guide/api/overview">
    Same operations over a REST surface
  </Card>

  <Card title="Skills" icon="wand-magic-sparkles" href="/guide/skills/overview">
    Package domain knowledge into reusable workflows
  </Card>

  <Card title="CLI" icon="terminal" href="/guide/cli/overview">
    Terminal access to the same capabilities
  </Card>
</CardGroup>