Skip to content

[FEATURE]: Allow to enable MCP on a per-agent basis #5373

Description

@lcswillems

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I'm using Playwright MCP server. I'd like this MCP server to only appear in the context of my scrap agent (and only be usable by my scrap agent too).

I can enable / disable a MCP server globally but I can't enable / disable a MCP server on a per-agent basis.

By default, I'd like the playwright MCP server to be disabled for all my agents (i.e. the MCP server is not in the context at all), and then for my agent scrap, I'd like to enable the playwright MCP server.

I know that there is a "tools" setting globally and per-agent, but this won't disable the MCP server meaning that even though the agent can't use it, it still appears in the context.

Activity

added
discussionUsed for feature requests, proposals, ideas, etc. Open discussion
on Dec 11, 2025

github-actions commented on Dec 11, 2025

@github-actions
Contributor

This issue might be a duplicate of existing issues. Please check:

Feel free to ignore if none of these address your specific case.

SamirSaidani commented on Dec 11, 2025

@SamirSaidani

rekram1-node commented on Dec 12, 2025

@rekram1-node
Collaborator

I know that there is a "tools" setting globally and per-agent, but this won't disable the MCP server meaning that even though the agent can't use it, it still appears in the context.

Uh that's not true

If the tool is disabled it will NOT appear in context

self-assigned this
on Dec 12, 2025

paralin commented on Dec 12, 2025

@paralin
Contributor

lcswillems commented on Dec 12, 2025

@lcswillems
Author

@paralin How is your PR addressing the issue? It seems the flag is just equivalent to setting the tools in the config, no? Doesn't seem to address the concern with the config. And personally, I would prefer config over flags.

lcswillems commented on Dec 12, 2025

@lcswillems
Author

@rekram1-node I missed your message. When I turn the playwright tools off, the context size reported by OpenCode doesn't decrease. It is only when I disable the MCP that it decreases.

lcswillems commented on Dec 12, 2025

@lcswillems
Author

@rekram1-node I've just tried again:

If I add the playwright MCP in the global config with "enabled": false, then I can't enable the Playwright tools in my local project. So only way is to enable the playwright MCP in my global config, but now if I disable the tools, the MCP server still gets loaded in the context...

Or maybe I'm misunderstanding something.

lcswillems commented on Dec 12, 2025

@lcswillems
Author

@rekram1-node Another option would be:

Allow me to set the Playwright MCP server in the global config with enabled: false. And then in my local configs, allow me to set it to enabled: true. (without having to set the other fields type and command)

rekram1-node commented on Dec 13, 2025

@rekram1-node
Collaborator

Allow me to set the Playwright MCP server in the global config with enabled: false. And then in my local configs, allow me to set it to enabled: true. (without having to set the other fields type and command)

If this is all you are asking for we have a separate issue tracking this and itll be added soon

lcswillems commented on Dec 13, 2025

@lcswillems
Author

@rekram1-node Do you have the link of this other issue? So I could confirm whether it is the same? 🙏

rekram1-node commented on Dec 17, 2025

@rekram1-node
Collaborator

Issue:
#4525

there is an Open PR for it that should be merged soon

eXamadeus commented on Dec 31, 2025

@eXamadeus
Contributor

Check out #6306. This is a configuration issue. It works, you just need wildcards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussion

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions