Skip to content

Conversation

@MQ37
Copy link
Contributor

@MQ37 MQ37 commented Jul 16, 2025

closes #166

Only docs tools category is currently enabled by default (always)

This PR introduces the tools (--tools or ?tools) comma separated list param so users can choose which tools are loaded into their MCP session.

Possible values:

  • docs: Search and fetch Apify documentation tools.
  • runs: Get Actor runs list, run details, and logs from a specific Actor run.
  • storage: Access datasets, key-value stores, and their records.

Example:

--tools docs,runs
?tools=docs,storage

Also vibe refactored the tool loading logic so it's not duplicated in the stdio.ts

@github-actions github-actions bot added t-ai Issues owned by the AI team. tested Temporary label used only programatically for some analytics. labels Jul 16, 2025
@MQ37 MQ37 requested review from MichalKalita and jirispilka July 17, 2025 07:47
@jirispilka jirispilka marked this pull request as ready for review July 17, 2025 08:35
Copy link
Collaborator

@jirispilka jirispilka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The only change I would do is rename things and remove the beta flag. What do you think?

@MQ37
Copy link
Contributor Author

MQ37 commented Jul 17, 2025

Looks good to me. The only change I would do is rename things and remove the beta flag. What do you think?

Agree, renamed and moved the beta tools to preview tools category 👍 Thank you for review

Copy link
Contributor

@MichalKalita MichalKalita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@MQ37 MQ37 merged commit f3b2e4f into master Jul 17, 2025
2 checks passed
@MQ37 MQ37 deleted the feat/tool-selection-param branch July 17, 2025 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-ai Issues owned by the AI team. tested Temporary label used only programatically for some analytics.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

May I know why we decide not to expose the other tools for more granular control of actors?

3 participants