MetriFi MCP — "I can't make edits anymore" Troubleshooting

When the MetriFi tools stop responding or you get "tool not found" / "not authorized" errors, work through these in order. The first two solve the large majority of cases.

1. Confirm who you are (the whoami check)

Ask your assistant:

"Run metrifi whoami"

This calls the MetriFi identity tool and tells you three things at once:

  • You're still connected & authorized → it returns your name, your teams, and your role. If you can see the correct team listed, the connection is healthy and the problem is elsewhere (skip to Section 4).
  • You need to re-authorize → it errors, returns nothing, or says you're unauthenticated/expired. Go to Section 3.
  • You're connected but on the wrong team / missing a role → it succeeds but the team you're trying to edit isn't listed, or your role is view-only. You may just need to be re-invited or have your role upgraded (see Section 5).

Tip: MCP tokens expire periodically for security. If whoami reports an authentication error, re-authorizing is usually the fastest next step.

2. Restart the app first (the 10-second fix)

MCP connections can drop quietly during a long session or after a computer sleeps. Before anything technical:

  1. Fully quit and reopen Claude Code / Codex.
  2. Run whoami again.

A surprising number of "it broke" cases are just a stale session that a restart clears.

3. Re-authorize the MetriFi connection

If whoami says you're not connected/authorized:

In Claude Code:

  • Run the /mcp command. This opens the MCP panel showing each server and its status.
  • Find metrifi in the list. If it shows needs authentication / disconnected, select it and choose Authenticate (or Reconnect).
  • A browser window opens — log in with your MetriFi account and approve access.
  • Return to Claude Code and run whoami to confirm.

In Codex:

  • Open the MCP/connectors settings (or your ~/.codex/config.toml where MCP servers are listed).
  • Locate the metrifi server entry and trigger its sign-in/authorize flow, then approve in the browser.
  • Restart Codex and run whoami to confirm.

If no browser window appears, check that a pop-up blocker didn't swallow it, and that you're signed into the correct MetriFi account in your default browser.

4. Verify the connection is actually active (finding where the connector lives)

The MCP connector can be a little tricky to locate and does disconnect from time to time. Here's where to look:

Claude Code:

  • /mcp — the quickest way to see live status of every connected server. A healthy MetriFi shows as connected; a broken one shows failed / disconnected / needs auth.
  • From a terminal: claude mcp list lists configured servers, and claude mcp get metrifi shows that server's details.

Codex:

  • codex mcp list (terminal) shows configured MCP servers and their state.
  • The connector definition lives in your Codex config file (typically ~/.codex/config.toml, under the MCP servers section). If metrifi isn't listed there at all, the connector was never added or got removed — it needs to be re-added, not just re-authorized.

What "active" looks like: the server is present in the list and status is connected/authenticated and whoami returns your identity. All three need to be true.

5. Other things to check

  • Right team selected. Edits are scoped to a specific team/site. If whoami shows you're connected but on a different team, ask the assistant to switch to the correct team before editing. If the team you need isn't listed at all, you likely need a fresh invite.
  • Role / permissions. Making page edits requires more than view access. If tools like publishing or writing files are refused but read tools work, your role may have changed — contact your MetriFi admin to restore edit rights.
  • One session at a time. If you use MetriFi for multiple MCP clients and one stops authenticating, re-authorize the affected client. 
  • Network / VPN. A corporate VPN, firewall, or proxy can block the MCP connection or the OAuth pop-up. Try toggling the VPN off for the sign-in step.
  • Check for outages. If whoami works but every edit tool times out, it may be a temporary MetriFi service issue rather than your setup — wait a few minutes and retry before deeper troubleshooting.
  • Still stuck? Capture the exact error text (and whether whoami succeeded) and send it to your MetriFi contact — that one detail tells us immediately whether it's auth, permissions, or a service issue.

Quick reference — the 30-second version:

  1. Run whoami
  2. If it fails → restart the app, run it again
  3. Still failing → /mcp (Claude Code) or connector settings (Codex) → re-authorize in the browser
  4. Works but can't edit → wrong team or role → contact your admin
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.