Fix & troubleshoot

MCP tools not showing up in Claude or ChatGPT after connecting

In almost every case, this is not a broken connection. It is that the connector is added but not switched on for the specific chat you are in. Modern AI clients treat "connector added to my account" and "connector active in this conversation" as two separate steps. Adding the wptaskify connector once (via your account or connector settings) saves it, but the tools stay dormant until you explicitly enable the connector inside the chat window, and often until you start a fresh chat so the client re-reads its tool list. On ChatGPT there is an extra gate: custom MCP connectors only work when Developer Mode is turned on first. A smaller set of cases are genuinely on the site side: the free wptaskify WordPress plugin was deactivated, or the site URL/authorization was never fully completed, so the server connects but has nothing to expose. The fastest way to tell them apart is the checklist below: enable-and-restart fixes the common case in under a minute; only if that fails do you look at the plugin and connection.</cause> <parameter name="is_platform_limitation">false

The fix

Step by step

Confirm the connector is actually enabled IN this chat, not just addedAdding a connector to your account does not turn it on for a conversation. In Claude (Desktop or web), open a chat and click the '+' button near the message box, choose Connectors, and toggle wptaskify ON for that conversation. In ChatGPT, click the '+' / tools menu in the composer and enable the wptaskify connector for the chat. This single step resolves the large majority of 'connected but no tools' reports.
Start a brand-new chat after enablingMost clients read their available tools once, when a conversation starts. If you enabled the connector inside a chat that was already open, the tools may not appear until you begin a fresh conversation. Open a new chat and try again. In Claude Code (CLI), the tool list is loaded at session start, so fully quit and relaunch the session rather than just starting a new prompt.
ChatGPT only: turn on Developer Mode firstCustom MCP connectors in ChatGPT require Developer Mode to be enabled before the connector's tools become usable in a chat. It lives in ChatGPT Settings under the Connectors / Apps area, behind an Advanced settings option. Turn Developer Mode on, then re-add or re-enable the wptaskify connector, then start a new chat. Without this, ChatGPT can show the connector but expose no usable tools. (Exact menu labels shift between ChatGPT releases and plan types, so look for 'Developer mode' under Connectors/Apps > Advanced rather than a fixed click path.)
Restart the client if it was open when you connectedIf you added the connector while Claude Desktop, Claude Code, or ChatGPT was already running, the app may be holding a stale tool list. Fully quit the application (not just close the window) and reopen it. This forces a fresh tool-discovery pass and clears the most common caching-related version of this problem.
Check that no wptaskify tools are individually BlockedIn Claude, you can block specific tools per connector under Customize > Connectors. If tools were blocked (by you or a workspace admin), they will be missing even though the connector is on. Open the wptaskify connector's settings there and make sure the tools you expect are set to allowed, not Blocked.
Verify the wptaskify WordPress plugin is still activeIf the connector is on and restarted but tools still do not appear or every call fails, check the site side. In your WordPress admin under Plugins, confirm the wptaskify (application password) plugin is Active. If it was deactivated or removed, the MCP server has nothing to operate on. Reactivate it, then in wptaskify confirm the site still shows as connected.
Re-check the server URL and re-authorize if neededA connector can show 'connected' while auth never fully completed. In your Claude/ChatGPT connector settings, confirm the wptaskify MCP server URL is exactly the one from your wptaskify dashboard (no trailing spaces, correct https URL). If in doubt, remove the connector, add it again, and complete the sign-in/authorization step all the way to the success screen before returning to your chat.
Confirm your plan and workspace allow custom connectorsCustom remote MCP connectors are a paid/plan-gated feature on both Claude (Pro/Max/Team/Enterprise tiers) and ChatGPT, and in team or enterprise workspaces an admin can restrict which connectors members may enable. If you see no option to add or toggle the connector at all, verify your plan supports custom connectors and, on a shared workspace, ask your admin to allow it.
Still stuck? If you have enabled the connector in the chat, started a fresh conversation, restarted the app, confirmed the plugin is active, and re-authorized, and tools still do not appear, the issue is usually a temporary client-side tool-discovery glitch rather than your wptaskify setup. Some client versions are known to lazy-load MCP tools or drop them mid-session, which needs a full restart or, occasionally, waiting for a client update. Try a different supported client (for example, if ChatGPT is misbehaving, test the same wptaskify connector in Claude Desktop) to confirm the connection itself is healthy. If tools work in one client but not another, it is a limitation of that client, not wptaskify. If nothing works in any client, reach out to wptaskify support with your site URL and which client and version you are using, and we will check the connection from our side.
FAQ

Related questions

The connector clearly says 'Connected' - why are there still no tools?

'Connected' only means the client reached the wptaskify server and authorized. It does not mean the connector is switched on for your current chat. In Claude, enable it via the '+' > Connectors toggle inside the conversation; in ChatGPT, enable it in the composer's tools menu (with Developer Mode on). Then start a new chat. That gap between 'connected' and 'active in this chat' is the number one cause.

Do I need to re-enable the connector in every new conversation?

Often, yes. Many client versions require you to toggle the connector on per conversation rather than globally. It is a quick one-click step from the '+' or tools menu at the start of a chat. If you use wptaskify daily, just make enabling the connector the first thing you do in a new chat.

I added it on ChatGPT but see nothing. What is different about ChatGPT?

ChatGPT requires Developer Mode to be enabled before custom MCP connectors expose their tools, and it usually needs a fresh chat after you enable it. Turn on Developer Mode (under Connectors/Apps > Advanced settings), then enable the wptaskify connector in the composer, then open a new chat.

Could this be because wptaskify has a lot of tools?

wptaskify exposes a large tool set (360+ tools across WordPress, WooCommerce and Shopify). A big tool list should still load, but if a client seems to hang or truncate, toggling the connector off and on and restarting the app forces a clean re-fetch. Blocking tools you do not need (in Claude's connector settings) can also make the list easier to work with.

Is my site or plugin the problem?

Usually not - the common cause is the per-chat enable/restart step on the client. But if you have done all of that and calls still fail, check that the free wptaskify WordPress plugin is still Active in your WordPress Plugins page and that your site shows connected in the wptaskify dashboard. A deactivated plugin lets the connector 'connect' but leaves it with nothing to run.

Do I have to reconnect my WordPress or Shopify site again?

No. This issue is about the AI client not surfacing the tools, not about your site connection. As long as your site still shows connected in wptaskify and the plugin is active, you only need to fix things on the client side (enable the connector in the chat and restart). Reconnecting the site is only necessary if the plugin was removed or the authorization was reset.

Ready to connect your AI to your site?

Start free How it works