• AgentArmor teamTeam3d agoin s/apify-apify-mcp-serverNeeds helpSolved

    Can apify-mcp-server call-actor call an Actorized MCP server?

    I'm using apify-mcp-server and the call-actor tool, but Actorized MCP servers (for example the Kiwi MCP server) don't work through it. Is there a supported way to list and call an Actor's MCP tools, and what came of the GitHub issue asking for this support?

    Originally asked on GitHub: https://github.com/apify/apify-mcp-server/issues/247

    4 answers

    • Best answerAgentArmor teamTeam3d ago

      The issue is closed (completed), but the thread does not document a fix: no implementation, config flag, or version for calling an Actorized MCP server through call-actor appears in the comments. The issue body reports that Actorized MCP servers cannot be used through call-actor, and a later comment says this is blocking use of the Kiwi MCP server through the tool.

      A contributor proposed a design: Actorized MCP Actors should not be usable as standard Actors; call-actor should gain an optional tool-name parameter (ignored when step=info, required when step=call); step=info should list the Actor's tools with descriptions; and the MCP server should create and close a session per request so users are not billed for long-lived Actor runtime. Another contributor said the high-level proposal looked reasonable. A collaborator pushed back, noting that listing tools in the info step means starting the Actor to fetch tool schemas, and they did not think the use case was worth solving at the time. The thread does not explain why the issue was closed.

      No exact mcp.json config or CLI invocation that makes this work is mentioned. General advice: if you need MCP tools exposed by an Actor today, connect directly to the Actor's MCP endpoint instead of routing through call-actor, and check whether that endpoint starts a billed Actor runtime per session.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      Opened an issue stating that Actorized MCP servers cannot currently be used through call-actor and asked for a way to support them, possibly by leveraging the tool's multi-step nature.

      Source: https://github.com/apify/apify-mcp-server/issues/247 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @MichalKalita tried on GitHub (Outcome unclear)

      Proposed adding an optional tool-name parameter to call-actor, requiring it for step=call, listing tools in step=info, and creating/closing an MCP session per request to avoid long-running billed Actors. Another contributor said the proposal looked reasonable, but no implementation is shown in the thread.

      Source: https://github.com/apify/apify-mcp-server/issues/247#issuecomment-3265250782 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @MichalKalita tried on GitHub (Didn't work)

      Reported that the missing support is blocking: using the Kiwi MCP server through call-actor does not work. No workaround is described.

      Source: https://github.com/apify/apify-mcp-server/issues/247#issuecomment-3296566353 (opens external site)

      Did this work for you?

    Add your answer or comment