-
Notifications
You must be signed in to change notification settings - Fork 181
Issues
is:issue state:open
is:issue state:open
Issue creation is restricted in this repository
Search results
- Status: Open.#1042 In apify/apify-mcp-server;
feat: Code Mode — experimental run-code + get-code-docs tools
t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#1017 In apify/apify-mcp-server;fix: Normalize required-array in published tool inputSchema across all tools
t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#1016 In apify/apify-mcp-server;[Feature]: Support MCP Enterprise-Managed Authorization (EMA) extension
enhancementNew feature or request.New feature or request.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#1015 In apify/apify-mcp-server;Cap the size of each individual tool response in MCP server
high priorityDo this ASAP! This is for mission-critical work or work that blocks other teams in their work.Do this ASAP! This is for mission-critical work or work that blocks other teams in their work.t-aiIssues owned by the AI team.Issues owned by the AI team.t-discoveryIssues owned by the discovery team.Issues owned by the discovery team.Status: Open.#1005 In apify/apify-mcp-server;Signed key-value-store record links in resources/read never expire
security relatedThe issue concerns security but does not expose a direct attack vector.The issue concerns security but does not expose a direct attack vector.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#1004 In apify/apify-mcp-server;[Feature]: Expose datasets and key-value stores as MCP resources
enhancementNew feature or request.New feature or request.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#998 In apify/apify-mcp-server;[Feature]: Enable search across private Actors via MCP
enhancementNew feature or request.New feature or request.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#997 In apify/apify-mcp-server;DCR auto-detection fails on RFC-compliant MCP servers (Royal MCP / WordPress)
bugSomething isn't working.Something isn't working.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#994 In apify/apify-mcp-server;[Feature]: Add (empty) output schema to
abort-actor-runenhancementNew feature or request.New feature or request.t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#993 In apify/apify-mcp-server;Add user-agent based on a client
t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#982 In apify/apify-mcp-server;refactor: Clean up src/tools structure and naming
t-aiIssues owned by the AI team.Issues owned by the AI team.Status: Open.#979 In apify/apify-mcp-server;