I thought I should mention our API wrapper intended for use with Cucumber test scenarios.

A description is here: https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Shared_features#Create_page_at_run_time_via_API

The way this works is that we have a "page object" in the mediawiki-selenium gem (https://github.com/wikimedia/mediawiki-selenium/blob/master/lib/mediawiki_selenium/support/pages/api_page.rb) that knows how to call our API wrapper in the ruby-api gem: https://github.com/wikimedia/mediawiki-ruby-api

This is very much a special-purpose API client and not intended to be comprehensive. It only exists to support testing features directly on a mediawiki instance within a special framework.

@Fhocutt: As you are set as assignee of this task, do you still plan to work on this or should this be placed up for grabs?
Could you elaborate what this task is about and what the supposed outcome will be? Should that TODO list include numeous existing client libraries to further investigate?

This task was part of my 2014 OPW internship work: https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries

https://www.mediawiki.org/wiki/API:Client_code/Evaluations satisfies this task.