PatchOps

Available tools

76 tools

Tool	Description
`get_me`	Get some account information of the authenticated user.
`get_users`	List all company users.
`post_users`	Create a new user.
`get_users_user_id`	Get single user.
`patch_users_user_id`	Update user.
`get_users_user_id_wells`	Retrieve list of wells that can be accessed by the user.
`get_users_user_id_wells_well_id`	Verify if the well can be accessed by the user.
`post_users_user_id_wells_well_id`	Grant well access to the user.
`get_users_user_id_well_groups`	Retrieve list of well groups that can be accessed by the user.
`get_users_user_id_well_groups_group_id`	Verify if the well group can be accessed by the user.
`post_users_user_id_well_groups_group_id`	Grant well group access to the user.
`get_wells`	Get the list of wells in the company.
`post_wells`	Create a new well.
`get_wells_well_id`	Get information of a single well.
`patch_wells_well_id`	Update an existing well.
`get_wells_well_id_users`	Retrieve list of users with access to this well.
`get_wells_well_id_users_user_id`	Verify if the user have access to the well.
`post_wells_well_id_users_user_id`	Grant well access to the user.
`get_wells_well_id_tanks`	Retrieve list of the tanks allocated to this well.
`get_wells_well_id_tanks_tank_id`	Verify if the tank is allocated to the well.
`post_wells_well_id_tanks_tank_id`	Allocate the tank to the well.
`get_tanks`	Get all tanks.
`post_tanks`	Create new tank
`get_tanks_tank_id`	Get a single tank
`patch_tanks_tank_id`	Update tank
`get_tanks_tank_id_readings`	Retrieve a list of tank readings.
`post_tanks_tank_id_readings`	Create tank reading. The previous portion of the reading is optional.
`get_tanks_tank_id_readings_reading_id`	Get single tank reading.
`patch_tanks_tank_id_readings_reading_id`	Update tank reading. The previous portion of the reading is optional.
`get_tanks_tank_id_readings_reading_id_run_tickets`	Get run tickets recorded on a tank reading
`post_tanks_tank_id_readings_reading_id_run_tickets`	Create run ticket.
`get_tanks_tank_id_readings_reading_id_run_tickets_run_ticket_id`	Get single run ticket.
`patch_tanks_tank_id_readings_reading_id_run_tickets_run_ticket_id`	Update run ticket.
`get_wells_well_id_meters`	Get the meters for the well.
`post_wells_well_id_meters`	Create new meter.
`get_wells_well_id_meters_meter_id`	Get single meter.
`patch_wells_well_id_meters_meter_id`	Update meter.
`get_wells_well_id_meters_meter_id_readings`	Get the readings of the meter.
`post_wells_well_id_meters_meter_id_readings`	Create meter reading.
`get_wells_well_id_meters_meter_id_readings_reading_id`	Get single meter reading.
`patch_wells_well_id_meters_meter_id_readings_reading_id`	Update reading.
`get_wells_well_id_production`	Get production data of specific well.
`post_wells_well_id_production`	Create new production data
`get_wells_well_id_production_production_id`	Get a single production.
`patch_wells_well_id_production_production_id`	Update production.
`get_well_groups`	List all company well groups.
`post_well_groups`	Create a new group.
`get_well_groups_group_id`	Get single group.
`patch_well_groups_group_id`	Update well group.
`get_well_groups_group_id_wells`	Retrieve list of wells in well group.
`get_well_groups_group_id_wells_well_id`	Verify if the well is part of the well group.
`post_well_groups_group_id_wells_well_id`	Add well to well group.
`get_well_groups_group_id_users`	Retrieve list of users with access to the well group.
`get_well_groups_group_id_users_user_id`	Verify if the user have access to the well group.
`post_well_groups_group_id_users_user_id`	Grant well group access to the user.
`get_fields`	Get all custom fields.
`post_fields`	Create field.
`get_fields_field_id`	Get single field.
`patch_fields_field_id`	Update field.
`get_wells_well_id_fields`	Get all fields assigned for this well.
`get_wells_well_id_fields_field_id_values`	Get field values of specific well.
`post_wells_well_id_fields_field_id_values`	Create a field value for a specific well.
`get_wells_well_id_fields_field_id_values_value_id`	Get field value for a specific well.
`patch_wells_well_id_fields_field_id_values_value_id`	Update field value for a specific well.
`get_wells_well_id_validation_rules`	Get validation rules for well.
`post_wells_well_id_validation_rules`	Create a new validation rule for well.
`get_wells_well_id_validation_rules_rule_id`	Get single validation rule.
`patch_wells_well_id_validation_rules_rule_id`	Update validation rule.
`get_wells_well_id_notes`	Get notes made on the well.
`post_wells_well_id_notes`	Create a new note.
`get_wells_well_id_notes_note_id`	Get single note.
`patch_wells_well_id_notes_note_id`	Update note.
`get_wells_well_id_well_tests`	Get a list of well tests of a specific well.
`get_wells_well_id_well_tests_well_test_id`	Get a single well test.
`find_wells_by_name`	Filter wells by a name/alias substring (case-insensitive). One underlying get_wells call, prefer over get_wells for pad or operator subsets.
`list_users_map`	Return a compact {id: name} dict of company users. Use to humanize numeric updated_by fields on production, readings, notes, and run tickets.

About

iWell is a field-data platform for oil and gas operators. Pumpers and lease operators capture daily tank gauges, run tickets, meter readings, production, and well tests from mobile or web, and managers get centralized dashboards and reporting. The API exposes the full data model so you can read and write wells, tanks, tank readings (daily and hourly), run tickets, meters, meter readings, daily production, custom fields, validation rules, notes, well tests, users, and well groups. Rate limit: 24 requests/minute per account. The date-range query params come in two forms that are NOT interchangeable. `since` is a UNIX epoch integer (30-day lookback max), while `start`/`end` are YYYY-MM-DD strings (inclusive, 30-day window max; the published docs say 31 but the server enforces 30). When `hourly=true` on tank readings, start must equal end (same-day window). 74 read and write methods (DELETE operations intentionally omitted for safety).

Requirements

iWell admin account
An iWell user account with administrator privileges is required to use the API.
Access Key and Access Key Secret
Issued from the iWell developer portal, these are the OAuth 2.0 client credentials used by the token endpoint.
Admin email and password
The email/password used to sign into iWell (password-grant OAuth2).

Setup

A few steps to connect your AI agents to iWell.

Get started

1
Sign into iWell as an admin
Log into https://revolution.iwell.info/ using an account that has administrator privileges.
2
Get credentials
Open the iWell developer portal at https://revolution.iwell.info/developer and copy your Access Key and Access Key Secret.
3
Add credentials in PatchOps
In PatchOps, open the iWell connector and enter your Access Key, Access Key Secret, admin email (username), and password. PatchOps exchanges these for a 7-day bearer token and refreshes automatically.
4
Mind the rate limits and date formats
The iWell API allows 24 requests/minute per account. Date-range queries are capped at 30 days (the public docs say 31 but the server enforces 30). `since` takes a UNIX epoch integer and also caps at a 30-day lookback; `start` and `end` take YYYY-MM-DD strings, do not pass UNIX timestamps to start/end or iWell will 500. For hourly tank readings, start and end must be the same day.

Connect to your AI assistant

Pick the tool your team uses for the exact setup steps.

1
Open Claude settings
Launch Claude, click the profile button (bottom left), and go to Settings.
2
Access connectors
Open the Connectors tab, scroll to the bottom, and click “Add custom connector”.
3
Name your connector
Enter any name you’d like for this connector.
4
Get the connector URL
Log in to PatchOps, open the /mcp page, and copy the connector URL you want to use.
5
Add the connector
Paste the URL into the “Remote MCP server URL” box and click Add.
6
Start using
Your iWell connector is ready to use in Claude.