Androidapi Mcp

io.github.TecniForgeMaryamPublished by GitHub account TecniForgeMaryamv1.0.1Updated Oct 24, 2026

Send SMS & WhatsApp, verify OTPs, manage contacts, and control Android devices via AndroidAPI.net.

VerifiedSTDIODesktop onlyProductivity & Workflow Communication & Collaboration

Server details

Identifier: io.github.TecniForgeMaryam/androidapi-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account TecniForgeMaryam for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.TecniForgeMaryam%2Fandroidapi-mcp.svg)](https://sourceweft.com/mcp/io.github.TecniForgeMaryam%2Fandroidapi-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant send SMS and WhatsApp messages, verify OTPs, manage contacts and control Android devices through AndroidAPI.net.

What you can do: Send SMS and WhatsApp messages through AndroidAPI.net, per the registry description, which does not list individual tools or their parameters. Verify one-time passcodes. Manage contacts. Control Android devices. The manifest lists no tools, so exact operations and inputs are not documented here.
When to use it: Useful when an assistant needs to reach people by SMS or WhatsApp, check OTP codes, keep a contact list, or operate Android devices through the AndroidAPI.net service rather than a local phone.
Requirements: Runs as a local stdio process, installed from the npm package androidapi-mcp, so Node.js is needed. Requires an AndroidAPI.net account and an API key supplied in the ANDROIDAPI_SECRET environment variable. Network access to AndroidAPI.net is required. Desktop only.

Before you install

The server needs an AndroidAPI.net API key in ANDROIDAPI_SECRET, which grants access to the account and may incur usage costs. It can send messages and control devices, so actions may reach real recipients or change device state. Message content, contacts and device data are sent to AndroidAPI.net as a third party. No tools are documented, so review what it can do before granting access.

Installation

In SourceWeft

Open Androidapi Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.