Skip to main content

TinyShield MCP Server for AI Agents

TinyShield's MCP server lets AI agents such as Claude Code, Codex, and Cursor work with TinyShield. An agent can see which apps connect where, answer connection approval requests, and manage your Block List, Allow List, and connection mode, all in plain language.

MCP and the command line are TinyShield PRO features.

Claude Code asks TinyShield what a weather app connects to, then blocks its two trackers.

1. Benefits​

  • ✅ Ask what an app, domain, or IP address connected to, and how much data it used.
  • ✅ Unblock unattended work: in Require Approval mode, an agent sees which tools are waiting and allows the ones you asked it to run. It doesn't fail on a connection timeout.
  • ✅ Manage the Block List, Allow List, decisions, and connection mode from a prompt.
  • ✅ Keep track of changes: every decision an agent makes is labeled with the agent's name in TinyShield's Decisions list.
  • ✅ Local only: the server listens on this Mac, needs an access token, and is off until you turn it on.

2. Turn on the MCP server​

  1. Open TinyShield › Settings › MCP.
  2. Check Enable MCP & Command Line. The status shows Running on 127.0.0.1.

Settings › MCP also shows the setup command for your agent, the command line alias, a Recent Activity list of every call agents and scripts made, and Regenerate Access Token.

3. Add TinyShield to your agent​

Use the path of the TinyShield app you run. For the Setapp edition, replace /Applications/Tiny Shield.app with /Applications/Setapp/Tiny Shield.app.

Claude Code​

claude mcp add --scope user tinyshield -- "/Applications/Tiny Shield.app/Contents/MacOS/tinyshield-mcp"

Codex​

codex mcp add tinyshield -- "/Applications/Tiny Shield.app/Contents/MacOS/tinyshield-mcp"

Cursor and other MCP clients​

{
"mcpServers": {
"tinyshield": {
"command": "/Applications/Tiny Shield.app/Contents/MacOS/tinyshield-mcp"
}
}
}

Starting an agent doesn't open TinyShield. The first time the agent uses a TinyShield tool, TinyShield opens in the background, without windows.

4. Example prompts​

  • What is forecast connecting to? Block the trackers.
  • My build can't download packages. Is TinyShield holding it?
  • Allow the tools waiting for approval from this build.
  • Which apps connected to new countries today?
  • Show me everything Chrome connected to in the last hour.
  • How much data did Safari use this week?
  • Switch to Require Approval and turn off the DNS exception.

5. Available tools​

AreaTools
Status and settingsget_status, set_connection_mode, get_settings, update_settings
Require Approvallist_pending_connections, allow_pending_connections, block_pending_connections, wait_for_pending_connections
Decisionslist_decisions, update_decisions, remove_decisions
Block List and Allow Listlist_block_rules, add_block_rules, remove_block_rules, list_allow_rules, add_allow_rules, remove_allow_rules
Network activitylist_apps, get_app_details, get_app_connections, get_domain_details, get_ip_details, get_activity_tree, list_countries, list_recently_blocked, clear_recently_blocked, clear_network_activity
Bandwidthget_bandwidth_usage, get_live_traffic
Configuration and windowsexport_configuration, import_configuration, open_window

Your MCP client shows each tool's description and arguments. Read-only tools are marked as such, so a client can run them without asking. Tools that remove data or weaken protection are marked destructive.

get_app_details and get_app_connections accept an app name, bundle ID, path, or the pid of a running process. get_status also works without PRO, so an agent can tell you why the other tools aren't available.

6. How it works​

  • TinyShield runs a small server on 127.0.0.1. The tinyshield-mcp tool that your agent starts forwards each tool call to it.
  • Every call needs an access token. TinyShield writes the token to ~/Library/Application Support/com.proxyman.ProxymanGuard/automation-server.json, which only your user account can read, and replaces it each time the server starts. The tools send the token only to the TinyShield process that wrote the file.
  • Requests from web pages are refused.
  • Turning the server off in Settings stops it. Agents then report that it's off instead of opening TinyShield.

7. Troubleshooting​

MessageWhat to do
Tiny Shield's MCP & Command Line server is offTurn it on in Settings › MCP.
…tools are part of Tiny Shield PROActivate your license in TinyShield › License.
Network activity isn't available yetInstall and allow the Network Extension.
No app is waiting for approvalRequests only wait in Require Approval mode.
The agent doesn't list TinyShield's toolsCheck the path in the setup command, then restart the agent, for example with /mcp in Claude Code.