---
title: MCP Server | Lightcone
description: Model Context Protocol server exposing Lightcone browser actions as tools for any MCP-compatible client.
---

The Lightcone Model Context Protocol (MCP) server exposes browser automation actions as [MCP](https://modelcontextprotocol.io) tools. Any MCP-compatible client (Claude Desktop, Cursor, Windsurf, and more) can use Lightcone to browse the web.

## Available tools

The MCP server exposes these tools:

| Tool                | Description                         |
| ------------------- | ----------------------------------- |
| `create_session`    | Create a browser or desktop session |
| `navigate`          | Navigate to a URL                   |
| `click`             | Click at coordinates                |
| `type`              | Type text                           |
| `screenshot`        | Capture the current viewport        |
| `scroll`            | Scroll the page                     |
| `execute_action`    | Execute any Lightcone action        |
| `get_html`          | Get the page HTML                   |
| `terminate_session` | End the session                     |

## Setup with Claude Desktop

Add to your Claude Desktop configuration (`claude_desktop_config.json`):

```
{
  "mcpServers": {
    "lightcone": {
      "command": "npx",
      "args": ["@tzafon/mcp-server"],
      "env": {
        "TZAFON_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}
```

Then ask Claude: *“Open a browser and go to example.com”* — Claude will use the Lightcone MCP tools to create a session, navigate, and return results.

## Setup with stdio transport

For programmatic use:

Terminal window

```
TZAFON_API_KEY=sk_your_key npx @tzafon/mcp-server
```

## Setup with HTTP transport

For remote server deployments:

Terminal window

```
TZAFON_API_KEY=sk_your_key npx @tzafon/mcp-server --transport http --port 3001
```

## How it works

The MCP server wraps Lightcone’s API into the MCP tool specification. When an MCP client (like Claude) decides it needs to interact with a web page, it:

1. Calls `create_session` to spin up a Lightcone browser
2. Uses `navigate`, `click`, `type`, `screenshot` tools to interact
3. Calls `terminate_session` when done

The server manages session lifecycle and translates MCP tool calls into Lightcone API requests.

## Resources

- [Model Context Protocol specification](https://modelcontextprotocol.io/docs/sdk)
- [MCP server repository](https://github.com/tzafon)

## See also

- [**Anthropic Claude**](/integrations/anthropic-claude/index.md) — Claude computer-use with Lightcone
- [**Computers**](/guides/computers/index.md) — direct API access to browser sessions
- [**How Lightcone works**](/guides/how-lightcone-works/index.md) — understand the session architecture