Integrations

Coding tools

Editors, terminals and coding agents that can call our MCP server. Add it once, then ask for a screenshot in plain words.

Every setup below sends the same two things: the address of our server, and your key in the Authorization header.

Where the tool can read an environment variable, the setup reads your key from LOCALSCREENSHOT_API_KEY, so the key is not written into a file you might share. Set it first:

export LOCALSCREENSHOT_API_KEY="your key"

Where the tool cannot, write your key in place of $LOCALSCREENSHOT_API_KEY, and keep that file out of git. The dashboard shows the same setups with your own key already in place, ready to copy.

Under each tool, one line says how far we checked it: Tested means we took a screenshot through that tool, Connected means the tool added our server and listed its tools, and the rest come from the tool's own documentation.

Claude Code

One command in your terminal.

claude mcp add --transport http localscreenshot https://api.localscreenshot.com/mcp \
  --header "Authorization: Bearer $LOCALSCREENSHOT_API_KEY"

Tested: we took a screenshot through it. Source: code.claude.com.

Cursor

Paste into .cursor/mcp.json. Cursor reads the key from your environment.

{
  "mcpServers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer ${env:LOCALSCREENSHOT_API_KEY}" }
    }
  }
}

A .cursor/mcp.json inside a project can end up in git. Prefer ~/.cursor/mcp.json for a file that holds your key.

From its documentation, not tried by us yet. Source: cursor.com.

Codex

One command in your terminal. Codex reads the key from your environment.

# Codex sends it as "Authorization: Bearer $LOCALSCREENSHOT_API_KEY"
codex mcp add localscreenshot --url https://api.localscreenshot.com/mcp \
  --bearer-token-env-var LOCALSCREENSHOT_API_KEY

Tested: we took a screenshot through it. Source: learn.chatgpt.com.

Gemini CLI

One command in your terminal.

gemini mcp add --scope user --transport http \
  --header "Authorization: Bearer $LOCALSCREENSHOT_API_KEY" \
  localscreenshot https://api.localscreenshot.com/mcp

Connected: we added our server to it and it listed our tools. Source: geminicli.com.

VS Code

Paste into .vscode/mcp.json. VS Code asks for your key once and keeps it. Works for GitHub Copilot in VS Code.

{
  "inputs": [
    { "type": "promptString", "id": "localscreenshot-key", "description": "localscreenshot API key", "password": true }
  ],
  "servers": {
    "localscreenshot": {
      "type": "http",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer ${input:localscreenshot-key}" }
    }
  }
}

This file holds your key. Do not commit it: prefer the user configuration, or the variant with a prompt shown on our site.

From its documentation, not tried by us yet. Source: code.visualstudio.com.

Windsurf

Paste into ~/.config/devin/mcp_config.json (Windsurf is now Devin Desktop). It reads the key from your environment.

{
  "mcpServers": {
    "localscreenshot": {
      "serverUrl": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer ${env:LOCALSCREENSHOT_API_KEY}" }
    }
  }
}

From its documentation, not tried by us yet. Source: docs.devin.ai.

Cline

Paste into cline_mcp_settings.json, with your key in place of the variable. This tool does not read environment variables in its settings.

{
  "mcpServers": {
    "localscreenshot": {
      "type": "streamableHttp",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
    }
  }
}

From its documentation, not tried by us yet. Source: docs.cline.bot.

Zed

Paste into your Zed settings, with your key in place of the variable. This tool does not read environment variables in its settings.

{
  "context_servers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
    }
  }
}

From its documentation, not tried by us yet. Source: zed.dev.

Copilot CLI

Paste into ~/.copilot/mcp-config.json, with your key in place of the variable. Or run /mcp add. This tool does not read environment variables in its settings.

{
  "mcpServers": {
    "localscreenshot": {
      "type": "http",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" },
      "tools": ["*"]
    }
  }
}

From its documentation, not tried by us yet. Source: docs.github.com.

Hermes Agent

Add this to ~/.hermes/config.yaml, with your key in place of the variable. Then run hermes mcp test localscreenshot. This tool does not read environment variables in its settings.

mcp_servers:
  localscreenshot:
    url: "https://api.localscreenshot.com/mcp"
    headers:
      Authorization: "Bearer $LOCALSCREENSHOT_API_KEY"

This file then holds your key: keep it out of any shared or versioned folder.

Connected: we added our server to it and it listed our tools. Source: hermes-agent.nousresearch.com.

Copilot in JetBrains

In Copilot Chat (Agent mode): tools icon, Add MCP Tools, then paste into mcp.json. Same format in Xcode and Eclipse. This tool does not read environment variables in its settings.

{
  "servers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "requestInit": {
        "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
      }
    }
  }
}

From its documentation, not tried by us yet. Source: docs.github.com.

Copilot coding agent

In your repository: Settings, Copilot, MCP servers. Store your key as the secret COPILOT_MCP_LOCALSCREENSHOT_API_KEY.

{
  "mcpServers": {
    "localscreenshot": {
      "type": "http",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $COPILOT_MCP_LOCALSCREENSHOT_API_KEY" },
      "tools": ["*"]
    }
  }
}

From its documentation, not tried by us yet. Source: docs.github.com.

Junie

Paste into ~/.junie/mcp/mcp.json, with your key in place of the variable. This tool does not read environment variables in its settings.

{
  "mcpServers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
    }
  }
}

A .junie/mcp/mcp.json inside a project can end up in git. Prefer the file in your home folder.

From its documentation, not tried by us yet. Source: junie.jetbrains.com.

Roo Code

In Roo Code: MCP settings, Edit Global MCP, then paste, with your key in place of the variable. This tool does not read environment variables in its settings.

{
  "mcpServers": {
    "localscreenshot": {
      "type": "streamable-http",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
    }
  }
}

From its documentation, not tried by us yet. Source: roocodeinc.github.io.

Kilo Code

Paste into ~/.config/kilo/kilo.jsonc, with your key in place of the variable. This tool does not read environment variables in its settings.

{
  "mcp": {
    "localscreenshot": {
      "type": "remote",
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" },
      "enabled": true
    }
  }
}

From its documentation, not tried by us yet. Source: kilo.ai.

Continue

Save as .continue/mcpServers/localscreenshot.yaml, with your key in place of the variable. This tool does not read environment variables in its settings.

name: localscreenshot
version: 0.0.1
schema: v1
mcpServers:
  - name: localscreenshot
    type: streamable-http
    url: https://api.localscreenshot.com/mcp
    requestOptions:
      headers:
        Authorization: Bearer $LOCALSCREENSHOT_API_KEY

A .continue folder inside a project can end up in git. Keep this file out of your repository.

From its documentation, not tried by us yet. Source: docs.continue.dev.

OpenCode

Paste into opencode.json. OpenCode reads the key from your environment.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "localscreenshot": {
      "type": "remote",
      "url": "https://api.localscreenshot.com/mcp",
      "enabled": true,
      "oauth": false,
      "headers": { "Authorization": "Bearer {env:LOCALSCREENSHOT_API_KEY}" }
    }
  }
}

An opencode.json inside a project can end up in git. Prefer the variant that reads the key from your environment, shown on our site.

Connected: we added our server to it and it listed our tools. Source: opencode.ai.

Amp

Add to ~/.config/amp/settings.json. Amp reads the key from your environment.

{
  "amp.mcpServers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer ${LOCALSCREENSHOT_API_KEY}" }
    }
  }
}

From its documentation, not tried by us yet. Source: ampcode.com.

Warp

In Warp: Settings, Agents, MCP servers, Add, Streamable HTTP or SSE Server (URL). Write your key in place of the variable. This tool does not read environment variables in its settings.

{
  "localscreenshot": {
    "url": "https://api.localscreenshot.com/mcp",
    "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
  }
}

From its documentation, not tried by us yet. Source: docs.warp.dev.

Kiro

Paste into ~/.kiro/settings/mcp.json. Kiro reads the key from your environment.

{
  "mcpServers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer ${LOCALSCREENSHOT_API_KEY}" },
      "disabled": false
    }
  }
}

From its documentation, not tried by us yet. Source: kiro.dev.

Antigravity

In Antigravity: MCP Servers, Manage MCP Servers, View raw config. Write your key in place of the variable. This tool does not read environment variables in its settings.

{
  "mcpServers": {
    "localscreenshot": {
      "serverUrl": "https://api.localscreenshot.com/mcp",
      "headers": { "Authorization": "Bearer $LOCALSCREENSHOT_API_KEY" }
    }
  }
}

From its documentation, not tried by us yet. Source: antigravity.google.

Qwen Code

One command in your terminal.

qwen mcp add --transport http localscreenshot https://api.localscreenshot.com/mcp \
  --header "Authorization: Bearer $LOCALSCREENSHOT_API_KEY"

Connected: we added our server to it and it listed our tools. Source: qwenlm.github.io.

Kimi Code

Paste into ~/.kimi-code/mcp.json. Kimi Code reads the key from your environment.

{
  "mcpServers": {
    "localscreenshot": {
      "url": "https://api.localscreenshot.com/mcp",
      "bearerTokenEnvVar": "LOCALSCREENSHOT_API_KEY"
    }
  }
}

From its documentation, not tried by us yet. Source: www.kimi.com.

Amazon Q Developer

In the Q Developer chat panel: tools icon, then the plus sign. Write your key in place of $LOCALSCREENSHOT_API_KEY.

1. In the Q Developer Chat panel, choose the tools icon, then the plus (+) symbol
2. Scope: global
3. Name: localscreenshot
4. Transport: http
5. URL: https://api.localscreenshot.com/mcp
6. Headers: Authorization = Bearer $LOCALSCREENSHOT_API_KEY
7. Save

From its documentation, not tried by us yet. Source: docs.aws.amazon.com.

Replit

In Replit: Integrations, add a custom MCP server. Write your key in place of $LOCALSCREENSHOT_API_KEY.

1. In Replit, open Integrations and add a custom MCP server
2. Display name: localscreenshot
3. Server URL: https://api.localscreenshot.com/mcp
4. Custom header
   Authorization: Bearer $LOCALSCREENSHOT_API_KEY

From its documentation, not tried by us yet. Source: docs.replit.com.

Lovable

In Lovable: Connectors, the plus button, MCP server. Write your key in place of $LOCALSCREENSHOT_API_KEY.

1. Open Connectors, select the + button in the top right of the catalog, and choose MCP server
2. Server name: localscreenshot
3. Server URL: https://api.localscreenshot.com/mcp
4. Authentication: Bearer token or API key
   $LOCALSCREENSHOT_API_KEY

From its documentation, not tried by us yet. Source: docs.lovable.dev.

Not ready yet

We show a setup only once we have read it in the tool's own documentation. Not yet for: goose, OpenClaw, v0, JetBrains AI Assistant.

Then ask

Take a screenshot of wikipedia.org on an iPhone.

What your tool can ask for, and what comes back, is on Ask your AI (MCP).

Without MCP

A coding agent that can run a shell command does not need MCP: it can call the command line client. Set LOCALSCREENSHOT_API_KEY, and the agent runs npx localscreenshot https://example.com -o shot.png. The options are on Command line (CLI).

NextAssistants