Apify MCP server shows connected but no tools available to the agent

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Apify MCP server shows as connected in Settings → Tools & MCP (green status) but the AI agent in chat cannot use any Apify tools. When the agent tries to call Apify tools (e.g. fetch-actor-details for harvestapi/linkedin-profile-posts), the call fails with “Tool user-apify-fetch-actor-details was not found.” The agent also cannot search Apify documentation via MCP. The UI shows “1 prompt enabled” for Apify; we expect all configured tools and actors to be available to the agent. In the project MCP cache (mcps/user-apify/) there are no tool descriptor files for Apify—only SERVER_METADATA.json and INSTRUCTIONS.md—while other MCP servers (e.g. Supabase) have a full tools/*.json set and work.

Steps to Reproduce

  1. Add Apify MCP server in ~/.cursor/mcp.json with url Apify MCP Server (and optionally more actors), and headers: { “Authorization”: “Bearer YOUR_APIFY_TOKEN” }.
  2. Restart Cursor fully.
  3. Open any chat and ask the agent to use Apify (e.g. “Search Apify for the actor harvestapi/linkedin-profile-posts and show me its input schema” or “Call fetch-actor-details for harvestapi/linkedin-profile-posts”).
  4. Observe: agent reports tool not found (e.g. Tool user-apify-fetch-actor-details was not found) and cannot search Apify docs or call any Apify tools.
  5. Check mcps/user-apify/ in the project: no tools/*.json files are present for Apify, unlike other MCP servers.

Expected Behavior

The agent should be able to call Apify MCP tools (e.g. search-actors, fetch-actor-details, call-actor, doc search) and run the Actors listed in the MCP server URL. The Apify server should expose its tool list to the agent so that tool names like fetch-actor-details are available and succeed when invoked.

Screenshots / Screen Recordings

Screenshot at Feb 20 00-47-55.png
Screenshot at Feb 20 00-47-55.png872×504 41.7 KB

Operating System

MacOS

Version Information

Connection: Remote (Streamable HTTP). Base URL: https://mcp.apify.com with ?tools=… query. Authentication: Bearer token in headers.Authorization.
Environment: macOS (darwin 24.6.0), Cursor IDE.
Version: 2.5.17
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

MCP not working - picture says it all
3

Hey, thanks for the report. This is a known issue with MCP tool discovery. The agent can’t see the tools even though the server is connected and shows green in the UI. In the mcps/user-apify/ directory, the tool descriptor files are missing.

Related thread with the same issue: MCP tool schemas not populated to file system

A couple of workarounds you can try:

  1. Start a new chat and, in your very first message, explicitly mention the server by name, for example: “Using the Apify MCP, fetch actor details for harvestapi/linkedin-profile-posts”. This can help the agent “discover” the server for the current session.

  2. In a new chat, try asking: “List all MCP tools you have access to”. It doesn’t always work, but sometimes it helps.

The team is aware of this issue. Please send the Request ID from the chat where the tools aren’t being discovered (three dots in the top right > Copy Request ID). That’ll help with prioritization.

1 Like
4

OK got ya. THanks!

I tried and it did not work.

I dont understand the “Please send the Request ID from the chat” Who should I send it to?

5

I am running into the same thing - two MCPs installed, connected and green. No tools are discovered. It has worked in the past, and I’ve tried removing them/re-adding, toggling on and off and nothing will get the tools to be discoverable even in a chat.

This means I can’t use MCPs in Cursor at all, which is a huge failure.