Provider hosted
No sign in
Tools: 161

Oil Command

Oil Command

Oilfield service software built for the field. Offline field tickets, real-time dispatch, inventory management, QuickBooks sync. 25+ modules, 50+ successful projects. Built by operators, for operators.

https://oilcommand.com/

Use in your AI tool

Use the tools from this page

Opens ChatGPT on the web or desktop and asks it to use the WebMCP tools available here.

Connect the MCP server

Connect straight to this server’s public endpoint.

Remote MCP URL
https://api.oilcommand.com/mcp

Use on MCPBundles

We add this server to your workspace, then open Studio — saved access, one connection to many servers, with a history of what ran.

Last probed Sep 14, 2026 · api.oilcommand.com

161tools discovered

Tools discovered (161)

Showing 25 of 161 from the live probe.

  • Cloudwatch Logs By Transaction

    Query CloudWatch Logs Insights for a backend transaction id in the current APP_ENV log group. `username` is kept for MCP call symmetry and audit context; AWS access uses the MCP server's internal admin identity, not tenant impersonation. `transaction_time` accepts ISO datetime or unix epoch and anchors the search window. If omitted, the window is anchored on now. The query range is capped at 120 minutes and results are capped at 500 rows. Common fields are timestamp, level, logger, message, tr

  • Cloudwatch Log Query

    Run a bounded CloudWatch Logs Insights query against the current APP_ENV Oil Command log group. `username` is kept for MCP call symmetry and audit context; AWS access uses the MCP server's internal admin identity, not tenant impersonation. `start_time` and `end_time` accept ISO datetime or unix epoch. The query range is capped at 120 minutes and results are capped at 500 rows. Use fields such as @timestamp, level, name, logger, message, @message, `meta.transaction.id`, `meta.request_id`, `meta

  • Company Integration List

    List all integrations and whether the tenant company has configured each. `typed=true` marks integrations with a structured config schema (call `company_integration_config_schema` for those, e.g. TWG Business Central and NetSuite). Others store a free-form `data` value. QuickBooks (`quickbooks`) is included too; its config lives on QbSetting rather than in the Integration catalog.

  • Company Integration Get

    Get the tenant company's configuration for one integration, by its code. Returns the parsed `data` (or the raw string when it is not JSON), whether it is configured, and the typed config schema when one exists. `quickbooks` configs also can be fetched here.

  • Company Integration Config Schema

    Describe the config fields for a typed integration. For TWG Business Central (`twg_business_central`) and NetSuite (`netsuite`) this returns each field's name, type, default, whether it is required, and its kind: `config` (behavior/secrets) or `mapping` (a JMESPath expression resolved against the OC ticket). Untyped integrations report `typed=false`.

  • Company Settings Get

    Read Company Settings for the tenant service account. Returns company profile fields, current timezone, logo file fields, locales YAML, field aliases, and advanced settings (`data_json`). Args: username: Tenant service account being managed.

  • Company Settings Update

    Update Company Settings through the existing company API/service path. Read `resource://company_settings_instructions` before calling this tool. The required `changes` object must contain at least one effective change. `advanced_settings` is deeply merged into the company's `data_json` object without removing omitted keys. Use `remove_advanced_setting_keys` to delete only explicitly named top-level keys. Call `company_settings_get` first and remove only keys confirmed by the human user. `defaul

  • Customer Accounting Name List

    List QuickBooks customer-name reconciliation mappings. Each mapping stores the tenant company, the customer office, and the accounting name that should be sent to QuickBooks. Args: username: Tenant service account being managed. search: Optional accounting-name search. fields: Optional API field projection. page: Page number. limit: Page size.

  • Customer Accounting Name Upsert

    Create or update a QuickBooks customer-name reconciliation mapping. Read `resource://company_settings_instructions` before calling this tool. Supply exactly one typed selector. Prefer an office id returned by a read. Args: username: Tenant service account being managed. accounting_name: QuickBooks customer name to use, for example `Walsh E.`. selector: Either an `office_id` selector or a `customer_name` selector.

  • Account Role List

    List account roles and their current permission data. Args: username: Tenant service account being managed. search: Optional role-name search. fields: Optional API field projection. page: Page number. limit: Page size.

  • Account Role Permission List

    List permission codenames that can be assigned to account roles. Args: username: Tenant service account being managed. search: Optional codename/name search. limit: Maximum permissions to return.

  • Account Role Create

    Create an account role with a permission set. Read `resource://company_settings_instructions` first. If permissions are requested, call `account_role_permission_list` in the current task and copy exact codenames from its result. Role data is passed to the existing `AccountRole` model/API, so group creation, audit columns, and role application stay on the canonical path. Args: username: Tenant service account being managed. name: Role name. permission_codenames: Auth permission cod

  • Custom Form Access Grant

    Grant company access through `/v2/custom_forms/{id}/access/`.

  • Custom Form Access Update

    Update company access through `/v2/custom_forms/{id}/access/{rule_id}/`.

  • Custom Form Access Revoke

    Revoke company access through `/v2/custom_forms/{id}/access/{rule_id}/`.

  • Custom Form Activity List

    Return a normalized Custom Form activity timeline across the form, its property groups, its properties, and optionally a ticket.

  • Custom Form List

    List Custom Forms using the v2 endpoint.

  • Custom Form Get

    Get a Custom Form with the v2 builder detail shape. Dropdown option lists can be huge. Request `property_groups__properties__values` in `fields` when those values are needed.

  • Custom Form Create

    Create a Custom Form through `/v2/custom_forms/`.

  • Custom Form Update

    Patch a Custom Form through `/v2/custom_forms/{id}/`.

  • Custom Form Clone

    Clone a Custom Form through `/v2/custom_forms/{id}/clone/`.

  • Custom Form List Types

    List Custom Form type codes.

  • Custom Form List Property Types

    List property types and their high-level MCP configuration contract.

  • Custom Form Get Property Type Config

    Return the expected configuration for a chosen property type.

  • Custom Form Property Create

    Create a typed Custom Form property through `/v2/properties/`.

Get your MCP into directories

A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.

Directory coverage for brands

Frequently Asked Questions

What is the Oil Command MCP server?

Oilfield service software built for the field. Offline field tickets, real-time dispatch, inventory management, QuickBooks sync. 25+ modules, 50+ successful projects. Built by operators, for operators.

How do I connect Oil Command to my AI agent?

Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.

How many tools does Oil Command provide?

MCPBundles probed 161 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.

What authentication does Oil Command require?

No provider sign-in was required during MCPBundles' probe. Your client may still need MCPBundles credentials depending on how you connect.

Maintain this listing

Operate Oil Command? Verify ownership to take over this directory entry.

Operate Oil Command?

This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Claim this listing