# Unmutely Account Health MCP

If asked to connect this user to Unmutely, identify the client and follow its section. Apply configuration only when your tools allow it; otherwise give the user the steps. Let the client start OAuth and have the user sign in and approve access. Verify with this read-only request: "List my connected accounts in Unmutely."

Server: https://api.unmutely.io/mcp
Authorization: OAuth 2.1 with PKCE. The user completes sign-in.

## Permissions
### Read account health — unmutely:read
always on
- See your connected accounts, available health tools and credit prices.

### Choose the default account — unmutely:settings
always on for new connections
- Select the connected account to use by default. This permission only changes account selection.

### Read account-health data — unmutely:data
optional, on by default
- Read health reports, following and follower lists, and source-data coverage for your connected accounts.
- See who unfollowed you, new followers and accounts you do not follow back on X.

### Imports and paid checks — unmutely:import
optional, needs unmutely:data
- Update the source data used by account-health checks.
- Run shadowban checks, Profile Audits, recovery scans, Following checks, follower updates and follower audits.
- Your AI shows the quote and asks before a paid run. Read results without running another check.
- MCP following markers record your choice; actual unfollow actions are in the Unmutely app.

Paid checks use their preflight quote and confirmation token. Show the cost and wait for the user's yes before starting the run. Poll the returned run ID and report its result. Only run the health check the user requests.

## Setup
## Claude
Anthropic
### Claude (web)

- anchor: `https://unmutely.io/products/mcp#claude-web`
- vendor: Anthropic
- surface: Web
- setup: follow the client’s setup steps

Add Unmutely as a custom connector in your Claude account.

1. Open Customize → Connectors.
2. Click "+", then "Add custom connector".
3. Paste https://api.unmutely.io/mcp as the remote MCP server URL.
4. The OAuth client is detected as "Register automatically". Leave OAuth Client ID and Secret blank.
5. Click "Add", then sign in to Unmutely and approve access.
6. In a chat, open "+" → "Connectors" and enable Unmutely.

Notes:
- Available on Free, Pro, Max, Team and Enterprise. Free accounts can add one custom connector.
- On Team and Enterprise, an owner must first add Unmutely under Organization settings → Connectors → Add → Custom → Web. Members then select Connect in Customize → Connectors.

Source: [Claude Help Center — Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

### Claude Desktop

- anchor: `https://unmutely.io/products/mcp#claude-desktop`
- vendor: Anthropic
- surface: Desktop app
- setup: follow the client’s setup steps

Uses the same connectors as claude.ai. If Unmutely is already connected there, enable it in your conversation.

1. Open Customize → Connectors in the desktop app.
2. Click "+" → "Add custom connector".
3. Paste https://api.unmutely.io/mcp as the remote MCP server URL.
4. The OAuth client is detected as "Register automatically". Leave OAuth Client ID and Secret blank, then click "Add".
5. Approve the scopes on the Unmutely consent screen that opens in your browser.
6. Enable Unmutely per conversation from the "+" button → "Connectors".

Notes:
- On Team and Enterprise, an owner must add Unmutely to the organization before members can connect. Free accounts can add one custom connector.

Source: [Claude Help Center — Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

### Claude Code

- anchor: `https://unmutely.io/products/mcp#claude-code`
- vendor: Anthropic
- surface: CLI
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely from the terminal, then sign in through your browser.

1. Run the add command below. `--scope user` makes Unmutely available in every project; drop it to keep the server in this project only.
2. Run `/mcp` inside Claude Code and choose Authenticate — or run `claude mcp login unmutely` — and approve the consent screen that opens in your browser.
3. Back in `/mcp`, Unmutely should read ✔ Connected.

Terminal commands:

```bash
claude mcp add --transport http --scope user unmutely https://api.unmutely.io/mcp
claude mcp login unmutely
```

Or commit it to the project — .mcp.json:

```json
{
  "mcpServers": {
    "unmutely": {
      "type": "http",
      "url": "https://api.unmutely.io/mcp"
    }
  }
}
```

Notes:
- If you use the project `.mcp.json` option, approve the server when Claude Code first asks to trust it.

Source: [Claude Code docs — Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp)

## ChatGPT & Codex
OpenAI
### ChatGPT (web)

- anchor: `https://unmutely.io/products/mcp#chatgpt-web`
- vendor: OpenAI
- surface: Web
- setup: follow the client’s setup steps

Enable developer mode to add Unmutely as a custom app.

1. Open Settings → Security and login and turn on Developer mode.
2. Open Plugins, select the plus button and create a developer-mode app.
3. Name it Unmutely, enter https://api.unmutely.io/mcp and choose OAuth. If asked for a registration method, choose Dynamic Client Registration (DCR).
4. Sign in to Unmutely and approve access.
5. In a chat, open the Plus menu → Developer mode and select Unmutely.

Notes:
- Available on the web with Plus, Pro, Business, Enterprise and Education accounts.
- Workspace administrators may need to enable developer mode and permission to create custom MCP connectors.

Source: [OpenAI — ChatGPT Developer mode](https://developers.openai.com/api/docs/guides/developer-mode)

### ChatGPT desktop app

- anchor: `https://unmutely.io/products/mcp#chatgpt-desktop`
- vendor: OpenAI
- surface: Desktop app
- setup: follow the client’s setup steps

Add Unmutely in Settings. This configuration is also used by Codex CLI and the IDE extension.

1. Open Settings and select MCP servers.
2. Select Add server.
3. Enter a name, choose "Streamable HTTP" and paste https://api.unmutely.io/mcp as the URL.
4. Save the server, then select Restart.
5. In the server list, select "Authenticate" next to Unmutely and approve the scopes.
6. Type /mcp in the composer to reach the connected servers.

Source: [ChatGPT Learn — Model Context Protocol (desktop)](https://learn.chatgpt.com/docs/extend/mcp?surface=desktop)

### Codex CLI

- anchor: `https://unmutely.io/products/mcp#codex-cli`
- vendor: OpenAI
- surface: CLI
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely by URL, then sign in through your browser.

1. Run the add command below.
2. Run `codex mcp login unmutely` and approve the consent screen in your browser.
3. Start Codex; the Unmutely tools show up in its tool list.

Terminal commands:

```bash
codex mcp add unmutely --url https://api.unmutely.io/mcp
codex mcp login unmutely
```

Or edit ~/.codex/config.toml:

```toml
[mcp_servers.unmutely]
url = "https://api.unmutely.io/mcp"
```

Notes:
- Codex CLI, the ChatGPT desktop app and the Codex IDE extension share this configuration.

Source: [ChatGPT Learn — Model Context Protocol (CLI)](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)

## Gemini
Google
### Gemini (web app)

- anchor: `https://unmutely.io/products/mcp#gemini-web`
- vendor: Google
- surface: Web
- setup: follow the client’s setup steps

Connect Unmutely as a custom app for Gemini Spark.

1. On a computer, open gemini.google.com → Settings & help → Connected Apps. If needed, open Personal Intelligence first.
2. Under "Custom apps for Spark", select the field to add a custom app link.
3. Enter https://api.unmutely.io/mcp, select "Next" and follow the prompts. Leave Advanced features unchanged.
4. Sign in to Unmutely and approve access.
5. In a Gemini Spark prompt, type @ and select Unmutely.

Notes:
- Requires Gemini Spark access, a personal Google Account, Keep Activity on, age 18+ and a location in the US. Available in English only.
- Connect on the web first; then use the app in Gemini Spark on web or mobile.

Source: [Gemini Apps Help — Connect & manage custom apps for Gemini Spark](https://support.google.com/gemini/answer/17209137)

### Gemini CLI

- anchor: `https://unmutely.io/products/mcp#gemini-cli`
- vendor: Google
- surface: CLI
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely from the terminal, then authorize it inside Gemini CLI.

1. Run the add command below.
2. Run `/mcp auth unmutely` inside Gemini CLI and approve the consent screen.
3. Run `/mcp` to confirm the Unmutely tools are listed.

Terminal commands:

```bash
gemini mcp add --transport http --scope user unmutely https://api.unmutely.io/mcp
# then, inside Gemini CLI:  /mcp auth unmutely
```

Or edit ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "unmutely": {
      "httpUrl": "https://api.unmutely.io/mcp"
    }
  }
}
```

Notes:
- The command saves Unmutely for every project. Use `--scope project` to save it for the current project only.

Source: [Gemini CLI docs — MCP servers with Gemini CLI](https://geminicli.com/docs/tools/mcp-server/)

## Grok
xAI
### Grok

- anchor: `https://unmutely.io/products/mcp#grok`
- vendor: xAI
- surface: Web
- setup: follow the client’s setup steps

Add Unmutely as a custom connector on grok.com.

1. Go to grok.com/connectors.
2. Click "New Connector", then select "Custom".
3. Enter https://api.unmutely.io/mcp as the MCP server URL and complete the authentication.
4. Approve the scopes on the Unmutely consent screen; Grok then discovers the tools and offers them in conversations alongside its built-in connectors.

Notes:
- On Grok Business and Enterprise, a team admin must first add Unmutely in console.x.ai → Grok Business → Connectors.
- These steps apply to grok.com. Setup in the mobile apps or inside X is unconfirmed.

Sources: [xAI docs — Grok Connectors](https://docs.x.ai/grok/connectors) · [xAI docs — Connector Management (Business and Enterprise)](https://docs.x.ai/grok/connector-management)

### Grok Bot

- anchor: `https://unmutely.io/products/mcp#grok-bot`
- vendor: xAI
- surface: Cloud agent
- setup: no verified connection route

Unmutely setup is unconfirmed. Grok Bot documents catalog plugins, but no custom MCP URL setup.


Notes:
- Use Grok on grok.com or Grok Build with the setup guides on this page.

Sources: [xAI docs — Grok Bot](https://docs.x.ai/grok-bot/overview) · [Cursor help — Connect plugins in Grok Bot](https://cursor.com/help/grok-bot/connect-plugins)

### Grok Build

- anchor: `https://unmutely.io/products/mcp#grok-build`
- vendor: xAI
- surface: CLI
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely from the terminal, then sign in through your browser.

1. Run the command below. Add `--scope project` to save it in the current repository.
2. Start `grok`, open `/mcps`, select unmutely and press `i` to sign in. Approve access in Unmutely.
3. Run `grok mcp doctor unmutely` to check the connection.

Terminal commands:

```bash
grok mcp add --transport http unmutely https://api.unmutely.io/mcp
```

Or edit ~/.grok/config.toml:

```toml
[mcp_servers.unmutely]
url = "https://api.unmutely.io/mcp"
```

Notes:
- Grok Build can also load Claude Code and Cursor MCP configurations. Run `grok inspect` to check whether Unmutely is already configured.
- The launch announcement lists early beta access for SuperGrok and X Premium+ subscribers.

Sources: [xAI docs — Grok Build MCP servers](https://docs.x.ai/build/features/mcp-servers) · [xAI — Introducing Grok Build](https://x.ai/news/grok-build-cli)

## Automation platforms
Make, Zapier and n8n
### Make

- anchor: `https://unmutely.io/products/mcp#make`
- vendor: Make
- surface: Automation
- setup: follow the client’s setup steps

Call Unmutely tools from a Make scenario with Make’s MCP Client app.

1. Sign in to unmutely.io in this browser first. If you sign in with X inside Make’s connection popup, the popup loses its link back to Make and the connection never finishes.
2. In your scenario, add the MCP Client module Call a tool and click Create a connection.
3. In the MCP Server field, click + New MCP Server, paste the URL below and leave API Key / Access token empty.
4. Click Save, then approve the permissions on Unmutely’s consent screen in the popup.
5. Pick a tool in Tool Name and map its arguments. Use one Call a tool module per tool; if you switch Tool Name in a module, press Refresh next to it so the old tool’s fields are cleared.

Server URL:

```bash
https://api.unmutely.io/mcp
```

Notes:
- Make’s MCP Client app is in open beta; Make says its features and pricing may change.
- Leave optional fields empty: Unmutely treats an empty field as not set.

Source: [Make Apps docs — MCP Client](https://apps.make.com/c5ZhYquO55e90hoCJ0rzt)

### Zapier MCP Client

- anchor: `https://unmutely.io/products/mcp#zapier`
- vendor: Zapier
- surface: Automation
- setup: follow the client’s setup steps

Call Unmutely tools from a Zap with Zapier’s MCP Client integration.

1. Connect X or Bluesky to Unmutely first, then sign in to unmutely.io in this browser.
2. In Zapier Apps, choose + Add connection, search for MCP Client, and click Add connection.
3. Paste the Unmutely server URL below. Choose Streamable HTTP for Transport and Yes for OAuth; leave Bearer Token empty.
4. Continue, then sign in to Unmutely and approve the permissions in the browser window.
5. In a Zap, select the MCP Client connection and choose Run Read-Only Tool for health reports or Run Tool for a health check. Pick the Unmutely tool and map its arguments.

Server URL:

```bash
https://api.unmutely.io/mcp
```

Notes:
- Zapier MCP Client is in beta. Verify the connection and the health tool you select in your own workflow before depending on it.
- Start with a read-only health tool. A paid health check must show its price and obtain your approval before it runs.

Source: [Zapier Help — Connect remote MCP servers using MCP Client](https://help.zapier.com/hc/en-us/articles/38777069364109-Connect-remote-MCP-servers-to-Zapier-using-MCP-Client)

### n8n MCP Client

- anchor: `https://unmutely.io/products/mcp#n8n`
- vendor: n8n
- surface: Automation
- setup: follow the client’s setup steps

Use Unmutely tools as steps in an n8n workflow with the MCP Client node.

1. Connect X or Bluesky to Unmutely first.
2. Add an MCP Client node to an n8n workflow and set Server Transport to Streamable HTTP.
3. Paste the Unmutely server URL below into MCP Endpoint URL and choose OAuth2 authentication.
4. Create the credential, sign in to Unmutely in the OAuth window, and approve the permissions.
5. Select an Unmutely tool. Enter simple arguments manually or choose JSON input mode for nested arguments, then run the node.

Server URL:

```bash
https://api.unmutely.io/mcp
```

Notes:
- Use the MCP Client node for regular workflow steps. n8n’s separate MCP Client Tool node exposes tools to an AI Agent.
- For a local n8n instance, open its editor with the same hostname configured for its OAuth callback (for example, localhost rather than 127.0.0.1).

Source: [n8n Docs — MCP Client node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcpClient/)

## Editors & other agents
Cursor, GitHub Copilot, Windsurf and OpenClaw
### Cursor

- anchor: `https://unmutely.io/products/mcp#cursor`
- vendor: Anysphere
- surface: Editor
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely to your MCP configuration and enable it in Customize.

1. Merge the entry below into `~/.cursor/mcp.json` for all projects, or `.cursor/mcp.json` for this project.
2. Open Customize in the sidebar and enable Unmutely.
3. Complete the Unmutely sign-in when Cursor prompts you and approve access.

~/.cursor/mcp.json:

```json
{
  "mcpServers": {
    "unmutely": {
      "url": "https://api.unmutely.io/mcp"
    }
  }
}
```

Source: [Cursor docs — Model Context Protocol](https://cursor.com/docs/mcp)

### VS Code (GitHub Copilot)

- anchor: `https://unmutely.io/products/mcp#vscode-copilot`
- vendor: Microsoft
- surface: Editor
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely to VS Code and use it in agent chat.

1. Merge the entry below into `.vscode/mcp.json`. For all workspaces, use MCP: Open User Configuration from the Command Palette instead.
2. Run MCP: List Servers, select Unmutely and start the server. Approve the trust and sign-in prompts.
3. Open agent chat and enable Unmutely in the tool picker.

.vscode/mcp.json:

```json
{
  "servers": {
    "unmutely": {
      "type": "http",
      "url": "https://api.unmutely.io/mcp"
    }
  }
}
```

Source: [VS Code docs — Use MCP servers in VS Code](https://code.visualstudio.com/docs/agent-customization/mcp-servers)

### Windsurf / Devin Desktop

- anchor: `https://unmutely.io/products/mcp#windsurf`
- vendor: Cognition
- surface: Editor
- setup: an agent with configuration access can help; the user completes sign-in

Use the Devin CLI setup for the default Devin agent, or the separate config below for legacy Cascade.

1. For the default Devin agent, run the two commands below and approve access in your browser.
2. For legacy Cascade, merge the JSON below into `~/.codeium/windsurf/mcp_config.json`.
3. In Cascade, open Settings → Cascade → MCP Servers, refresh the list and complete the Unmutely sign-in when prompted.

Default (Devin) agent — terminal commands:

```bash
devin mcp add -s user unmutely https://api.unmutely.io/mcp
devin mcp login unmutely
```

Legacy Cascade agent — ~/.codeium/windsurf/mcp_config.json:

```json
{
  "mcpServers": {
    "unmutely": {
      "serverUrl": "https://api.unmutely.io/mcp"
    }
  }
}
```

Notes:
- The Devin command saves Unmutely for all projects. Cascade uses a separate configuration and sign-in.
- Team settings may restrict MCP servers; Enterprise users must enable MCP in settings.

Sources: [Devin docs — CLI MCP configuration (default agent)](https://docs.devin.ai/cli/extensibility/mcp/configuration) · [Devin docs — Cascade MCP (legacy agent, formerly docs.windsurf.com)](https://docs.devin.ai/desktop/cascade/mcp)

### OpenClaw

- anchor: `https://unmutely.io/products/mcp#openclaw`
- vendor: OpenClaw
- surface: Self-hosted agent
- setup: an agent with configuration access can help; the user completes sign-in

Add Unmutely with OAuth enabled, then sign in through your browser.

1. Run the two commands below.
2. Open the authorization URL and approve access in Unmutely.
3. Run `openclaw mcp doctor unmutely --probe` to verify the connection.

Terminal commands:

```bash
openclaw mcp add unmutely --url https://api.unmutely.io/mcp --transport streamable-http --auth oauth
openclaw mcp login unmutely
```

Or edit ~/.openclaw/openclaw.json:

```json5
{
  mcp: {
    servers: {
      unmutely: {
        url: "https://api.unmutely.io/mcp",
        transport: "streamable-http",
        auth: "oauth",
        enabled: true,
      },
    },
  },
}
```

Notes:
- If the browser cannot reach the callback, finish with the --code command printed by OpenClaw.
- An existing Gateway or agent may need its configuration reloaded before Unmutely tools appear.

Sources: [OpenClaw docs — Connect MCP servers](https://docs.openclaw.ai/tools/mcp) · [OpenClaw docs — MCP commands and OAuth](https://docs.openclaw.ai/cli/mcp/registry)

## Any other MCP client

- anchor: `https://unmutely.io/products/mcp#any-other-client`
- vendor: —
- surface: Anything else
- setup: an agent with configuration access can help; the user completes sign-in

Use a client that supports remote Streamable HTTP and MCP OAuth with dynamic client registration.

1. Add Unmutely as a remote (streamable HTTP) MCP server with the URL below.
2. Let the client run the OAuth flow. Unmutely registers clients dynamically, so there is no client ID or secret to create first, and no API key.
3. Approve the permissions on the consent screen. Reading account health and choosing the default account are required. Reading health data and paid checks are optional; paid checks require data access.

Server URL:

```bash
https://api.unmutely.io/mcp
```

Notes:
- A localhost URL works only for a client on that machine. For a hosted client, use https://api.unmutely.io/mcp to connect to production.
- A stdio-only client needs a bridge that also supports Unmutely’s OAuth sign-in.

Source: [Model Context Protocol — Connect to remote MCP servers](https://modelcontextprotocol.io/docs/develop/connect-remote-servers)


Manage access: https://unmutely.io/ai-apps