Connect third-party apps and AI agents to your Fing account

A third-party app is an application you allow to read your Fing account through a secure sign-in, without ever giving it your password. Two kinds exist today: the IFTTT automation service, open to every Fing account, and AI agents that connect through the Fing MCP server, a beta for Fing Professional accounts. Every app you connect appears under Third-party apps in your account, where you can see what it may do, reduce its access or revoke it.

Where to find your connected apps

Sign in at app.fing.com, open Access from the account navigation and select the Third-party apps tab. The Connected applications list shows every app you authorised:

• Application: the name and icon the app registered with Fing. 'Unknown application' means the app can no longer be read; you can still revoke it.
• Scopes: what the app may do. ifttt is the IFTTT automation scope; mcp_read, mcp_write and mcp_provisioning belong to AI agents.
• Granted: when you approved the app.
• Last used: the last time the app renewed its access. 'Never' means it has not come back since you approved it.

Nothing on this page adds an app. Connections always start in the app itself, which sends you to Fing to sign in and approve. The sections below show where that starts for each kind of app.

Connect IFTTT

IFTTT applets react to what Fing sees on your network. The Fing service on IFTTT works with every Fing plan, including the free one.

Fing on IFTTT offers triggers such as 'Internet Outage event happened', 'Someone arrived', 'Everyone left', 'New device found', 'Internet Speed dropped', 'Device is ON' and 'Device is OFF', and actions to pause or restore internet access for a device and to play an LED effect on a Fingbox.

1. Open ifttt.com/fing and sign in to IFTTT, or create a free IFTTT account.
2. Click Connect. IFTTT opens the Fing sign-in page.
3. Sign in with your Fing account and approve the access. Fing sends you back to IFTTT.
4. Create an applet that uses a Fing trigger or action. IFTTT now appears under Connected applications with the ifttt scope.

The Internet Outage trigger only needs a Fing account; presence and device triggers need an agent or a Fingbox monitoring your network. IFTTT checks polling triggers every hour on its free plan and every five minutes on IFTTT Pro, and its history queries need IFTTT Pro+.

Connect an AI agent through the Fing MCP server (beta)

The Model Context Protocol (MCP) is the open standard AI assistants use to call external tools. Fing runs an MCP server at https://app.fing.com/mcp. Once connected, your assistant can list your workspaces and networks, read the detail of a network, page through its devices and contacts, read its event log and fetch the latest speed test and router vulnerability results. Every tool is read-only in this beta: an agent cannot change your networks, block devices or run scans.

There is no Fing entry in any assistant's connector directory yet, so you add the server by its address. Each assistant does it slightly differently, but the shape is the same:

1. Add https://app.fing.com/mcp as a remote MCP server in the assistant.
2. Start the sign-in. The assistant opens the Fing sign-in page in your browser.
3. Sign in and approve the scopes the agent asks for: mcp_read, mcp_write and mcp_provisioning. The assistant appears under Connected applications as soon as you approve.

The assistant registers itself with Fing and keeps its own sign-in. You do not create a client or paste any key.

claude mcp add --transport http fing https://app.fing.com/mcp

codex mcp add fing --url https://app.fing.com/mcp
codex mcp login fing

[mcp_servers.fing]
url = "https://app.fing.com/mcp"

agy mcp add --type http fing https://app.fing.com/mcp

{
  "mcpServers": {
    "fing": {
      "url": "https://app.fing.com/mcp"
    }
  }
}

How long access lasts

An approval lasts until you revoke it, or until the app's own plan requirement no longer applies to your account. The app renews its access in the background and the Last used column shows the last renewal; an AI agent that keeps working refreshes its access at most every 30 days. You do not need to approve an app again unless you revoke it, or unless it asks for a scope you removed.

Reduce what an app can do

You can take scopes away from an app without disconnecting it.

1. Under Connected applications, click the pencil button in the app's row.
2. In Reduce access, untick the scopes the app should no longer have. At least one scope must stay ticked.
3. Click Save. The change applies to the next access the app requests; what it already fetched is unaffected.

Only the scopes the app already holds are listed. To give a scope back, connect the app again from the app itself so it asks for your approval; the dialog cannot grant more than you removed. To remove every scope, revoke the app instead.

Revoke an app

1. Under Connected applications, click the revoke button, the broken-link icon, in the app's row.
2. Read the confirmation and click Revoke access.

The app loses access immediately and every token Fing issued to it stops working. It disappears from the list and has to ask for your approval again to reconnect. Revoking an AI agent does not remove the server from the agent's configuration, so remove it there as well, or the agent keeps asking you to sign in. For Claude Code that is claude mcp remove fing, for Antigravity agy mcp remove fing, and for the Claude app the Remove button under Connectors.

Troubleshooting

Need help?

Click the Submit a request button at the top right of the page and mention the app you are connecting.