Home / Token cost / Scrcpy

The Scrcpy MCP server costs 3,805 tokens before the first call.

Connect Scrcpy and its 38 tool definitions are loaded into the model's context on every request — 1.9% of a 200k window spent before your agent does anything.

QUICK ANSWER The Scrcpy MCP server's tool definitions consume 3,805 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 38 tools · 3,805 tokens · 1.9% of 200k · 0.4% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 1.9%
1M WINDOW 0.4%

Corpus context: Scrcpy ranks #1179 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 3,805 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 100 tokens per tool.

ToolCategoryTokens% of server
drag_drop Write 236 6.2%
swipe Write 209 5.5%
scroll Write 180 4.7%
ui_find_element Read 179 4.7%
start_session Execute 164 4.3%
long_press Write 142 3.7%
app_start Execute 136 3.6%
clipboard_set Write 123 3.2%
screen_record_start Execute 117 3.1%
start_video_stream Execute 116 3.0%
app_list Read 113 3.0%
file_pull Write 112 2.9%
file_push Write 112 2.9%
key_event Write 111 2.9%
connect_wifi Write 110 2.9%
tap Write 108 2.8%
screen_record_stop Execute 106 2.8%
shell_exec Execute 94 2.5%
app_uninstall Destructive 84 2.2%
app_stop Execute 84 2.2%
app_install Write 84 2.2%
file_list Read 83 2.2%
clipboard_get Read 82 2.2%
device_info Read 76 2.0%
disconnect_wifi Write 73 1.9%
input_text Write 72 1.9%
ui_dump Write 68 1.8%
collapse_panels Write 63 1.7%
stop_video_stream Execute 62 1.6%
stop_session Execute 61 1.6%
screenshot Read 61 1.6%
expand_settings Write 58 1.5%
expand_notifications Write 57 1.5%
rotate_device Write 57 1.5%
app_current Read 56 1.5%
screen_on Write 55 1.4%
screen_off Write 51 1.3%
device_list Read 50 1.3%

Most agents use a handful of these tools. They pay for all 38.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (100 tokens each).

Grant scopeDefinition costReduction
All 38 tools (no gateway) 3,805 tokens
3 granted tools ~300 tokens −92%
5 granted tools ~501 tokens −87%
10 granted tools ~1,001 tokens −74%

Scrcpy token-cost questions.

How many tokens does the Scrcpy MCP server use?+

Its 38 tool definitions total 3,805 tokens — 1.9% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Scrcpy consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Scrcpy's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Scrcpy to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 300 tokens, a 92% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 38 catalogued Scrcpy tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Scrcpy to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.