You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MCP server: get_attributes tool always fails for named attributes - TypeError: get_attribute() got an unexpected keyword argument 'timeout' #4542
The get_attributes MCP tool always fails when a named attribute is requested — even when the MCP client omits timeout, because the server passes its own default (timeout=5) through to CDPMethods.get_attribute(), which does not accept a timeout parameter.
Repro
Via the MCP server (get_attributes with selector + attribute, e.g. attribute="href" on a link):
Error in get_attributes: TypeError - CDPMethods.get_attribute() got an unexpected keyword argument 'timeout'
Thanks for reporting this. Will be fixed in the next release.
Note that your reproduction steps are incorrect. The MCP server uses Pure CDP Mode (sb_cdp).
The proper code to reproduce the issue directly should look like this:
Thanks @mdmintz for the quick response and the correction — you're right that sb_cdp.Chrome() is the canonical Pure CDP Mode entry point. I confirmed your form reproduces it exactly:
(The signature mismatch is in CDPMethods.get_attribute() itself, so it reproduces from either entry point, but yours is the proper direct repro.) Looking forward to the next release — I'll validate the fix against it and report back.
Activity
mdmintz commentedon Nov 1, 2026
Thanks for reporting this. Will be fixed in the next release.
Note that your reproduction steps are incorrect. The MCP server uses Pure CDP Mode (
sb_cdp).The proper code to reproduce the issue directly should look like this:
SynthLuvr commentedon Nov 1, 2026
Thanks @mdmintz for the quick response and the correction — you're right that
sb_cdp.Chrome()is the canonical Pure CDP Mode entry point. I confirmed your form reproduces it exactly:(The signature mismatch is in
CDPMethods.get_attribute()itself, so it reproduces from either entry point, but yours is the proper direct repro.) Looking forward to the next release — I'll validate the fix against it and report back.mdmintz commentedon Nov 3, 2026
This was resolved in
4.57.0- https://github.com/seleniumbase/SeleniumBase/releases/tag/v4.57.0