Light: Download + OCR vs Mobile MCP

A side-by-side look at the Light: Download + OCR and Mobile MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Light: Download + OCR logoLight: Download + OCRSearch & Data Extraction · Remote HTTP/SSELight: Download + OCR, official-source lookup. Platform-hosted, pay per query with prepaid credit.55GoodAuth: not declaredMobile MCP logoMobile MCPSearch & Data Extraction · Local subprocess (stdio)MCP Server for Android/iOS application and device automation, development and app scraping. Simulator/Emulator/Physical devices like iPhone, Google Pixel, Samsung supported.69GreatAuth: no auth required

Verdict: choose Light: Download + OCR for search & data extraction work over a hosted endpoint; choose Mobile MCP for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Light: Download + OCR logoChoose Light: Download + OCR when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like contas_light_download_ocr_consultar, show_version, report_bug.
Explore Light: Download + OCR

Mobile MCP logoChoose Mobile MCP when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like mobile_list_available_devices, mobile_login_to_cloud_provider, mobile_list_remote_devices.
Explore Mobile MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLight: Download + OCR logoLight: Download + OCRMobile MCP logoMobile MCP
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal55/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars09,936
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools733

Tools & capabilities

Light: Download + OCR tools 7

  • contas_light_download_ocr_consultarLight: Download + OCR, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).
  • show_versionShow the current MCP platform and adapter versions.
  • report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
  • connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
  • toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
  • marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
  • authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Mobile MCP tools 33

  • mobile_list_available_devicesList all available devices. This includes both physical mobile devices and mobile simulators and emulators. It returns both Android and iOS devices. These are local devices already connected to this machine, ready to use immediately at no cost - for devices from the shared remote cloud fleet, use mobile_list_remote_devices instead.
  • mobile_login_to_cloud_providerStart authenticating this machine with the remote device cloud provider. This is required once before mobile_list_remote_devices or mobile_allocate_remote_device will work; if either of those fails with an authentication error, call this tool and then retry. This starts a browser-based device-code login and returns quickly with a URL and a one-time code - it does NOT wait for the login to complete. Show the URL and code to the user verbatim and ask them to open the URL and enter the code in their own browser. The login keeps running in the background after this tool returns; once the user confirms they've completed it, retry the remote devices tool that originally failed. Only call this after the user has explicitly asked to connect to, log into, or use remote/cloud devices - never call it speculatively, since it interrupts the user to act in their browser.
  • mobile_list_remote_devicesList the catalog of device models (make, platform, OS version) available to reserve from the remote cloud device fleet. This is different from mobile_list_available_devices, which lists real devices and simulators/emulators already connected to this local machine and ready to use immediately at no cost. Remote devices live in a shared cloud fleet: they are not usable until reserved with mobile_allocate_remote_device, and reserving one may be a limited/billed resource. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry.
  • mobile_allocate_remote_deviceReserve a physical device from the remote cloud fleet for exclusive use, returning a device identifier usable with the other mobile_* tools. Unlike local devices, a remote device is a shared and billed resource borrowed for the session - only call this after the user has explicitly asked to use a remote/cloud device, never speculatively or as a fallback when a local device isn't found. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry. Use mobile_list_remote_devices first to see which names and versions actually exist in the fleet before filtering by them. Release the device with mobile_release_remote_device once the whole task is finished - releasing wipes the device's state, so do not release and reallocate between steps of the same task just to be tidy.
  • mobile_release_remote_deviceRelease a device previously reserved with mobile_allocate_remote_device back to the remote cloud fleet so it becomes available to others. Releasing is destructive to the device's state: apps installed, files pushed, and any other changes made during this session are lost, and a later mobile_allocate_remote_device call may take time and could return a different physical unit. Only release once the whole task is finished - if there is more work to do on the same device shortly, keep holding it rather than releasing and reallocating.
  • mobile_list_appsList all the installed apps on the device
  • mobile_get_foreground_appGet the app currently in the foreground on the device. Use this to verify which app or screen you are on before interacting with it.
  • mobile_launch_appLaunch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device.
  • mobile_terminate_appStop and terminate an app on mobile device
  • mobile_install_appInstall an app on mobile device
  • mobile_uninstall_appUninstall an app from mobile device
  • mobile_get_screen_sizeGet the screen size of the mobile device in pixels
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Light: Download + OCR

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "light-download-ocr": {
      "url": "https://api.mcp.ai/p_contas_light_download_ocr"
    }
  }
}

Mobile MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobile-next-mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Light: Download + OCR is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Mobile MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Light: Download + OCR for search & data extraction work and Mobile MCP for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Light: Download + OCR has no declared pricing — check the project's own site. Mobile MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add light-download-ocr and mobile-next-mobile-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Light: Download + OCR has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Mobile MCP has 69/100 (Great) with 8 views, 0 installs and 9,936 GitHub stars.