Android Preference Editor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| change_preferenceC | Changes the value of an existing preference |
| delete_preferenceC | Delete an existing preference |
| add_preferenceC | Adds a new preference given the name, value and type. |
| devicesB | Lists connected Android devices |
| list_appsC | Lists apps installed on device |
| list_filesC | Lists preference files for an app |
| read_preferencesC | Reads all user preferences in a file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity. Preference management tools (add, change, delete, read) target specific operations, while device/app/file listing tools serve separate discovery functions. The descriptions make it easy to differentiate between actions on preferences versus actions on devices/apps/files.
All tools follow a consistent verb_noun naming pattern throughout. The verbs (add, change, delete, list, read) are consistently applied to their respective nouns (preference, devices, apps, files, preferences). There are no deviations in style or convention across the tool set.
With 7 tools, this server is well-scoped for editing Android preferences. It covers core operations (CRUD for preferences) plus necessary discovery tools (devices, apps, files) without being overly sparse or bloated. Each tool earns its place in the workflow.
The tool surface provides complete coverage for the Android preference editing domain. It offers full CRUD operations for preferences (add, change, delete, read) plus the necessary discovery chain (devices → apps → files → preferences). There are no obvious gaps that would prevent an agent from performing the intended workflows.