Add opt-in per-integration MCP search tools - #1741
Merged
Merged
Conversation
Contributor
Cloudflare previewTorn down — the PR is closed. |
RhysSullivan
marked this pull request as ready for review
August 25, 2026 20:51
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | e52600e | Commit Preview URL Branch Preview URL |
Aug 25 2026, 08:51 PM |
This was referenced Aug 25, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a per-connection MCP option, off by default, mirroring the artifacts flag:
?search_tools=true(stdio:executor mcp --search-tools) registers one minimally-describedsearch_<integration>tool per connected integration. The point is to put the integration namespaces into the model's context as tool names; each call routes through the same flow astools.search({ namespace })insideexecute, and the tool list is parsed from the same inventory block theexecutedescription carries, so the two surfaces cannot disagree.?artifacts=end to end (cloud + host-cloudflare DOs incl. session meta for cold restores, local, selfhost in-memory store, CLI stdio bridge).namespace-search-tools(passing on selfhost) proves the comparative surface and that results match code-side search.