Talk to your drilling business from Claude, ChatGPT, and other AI assistants
Connect DrillerDB to Claude, ChatGPT, or any MCP-compatible AI assistant and skip the clicks. Jobs, schedules, money owed, well logs - your whole shop is one question away. And when the AI wants to send something to a customer, it waits for your approval first.
Works with Claude · ChatGPT · Cursor · Codex
Every example below runs on tools that exist in the connector today - the tool names are listed under each card.
“What's on the schedule tomorrow, and which crew has each job?”
Every booked job with its date and crew, straight from your DrillerDB schedule.
query_schedule, list_crews
“Who owes us more than $5,000 and is past 60 days? Sort by oldest invoice.”
A real accounts-receivable aging report - current, 30, 60, 90+ buckets - in one question.
ar_aging_report, list_invoices, get_invoice_detail
“Pull up everything on Trillion Farms: their projects, what we've billed them, and any open proposals.”
Project history, lifetime billing, and proposal status without clicking through three screens.
list_projects_by_customer, total_billed_by_contact, customer_ltv_report, list_proposals
“What did we hit on the Hansen well? Give me the lithology, casing, and static water level.”
Depth-by-depth geology from your own well logs: formations, casing, and water levels.
query_well_logs, get_project_detail
“What does our revenue pipeline look like? Which proposals are still waiting on customers?”
Open proposals, pending work, and pipeline value summarized from live data.
revenue_pipeline, list_proposals, get_project_financials
“Summarize last week's timecards by project, and list any field reports filed for the Smith job.”
Timecard totals, field reports, work orders, and equipment - the whole field picture.
get_timecard_summary, list_field_reports, list_work_orders, list_equipment
Reading your data is useful. Getting work done is better. The connector ships 8 write tools: quick additive actions like notes, field reports, and route planning run directly, while job status changes, scheduling, dispatch, and anything that touches a customer or your books go through an approval gate.
Approval-gated actions pause mid-conversation. The assistant tells you it's waiting, and you approve or deny the request under AI agent approvals in DrillerDB. Approval alone does not run the action: after you approve, ask the assistant to retry it. A request that is not approved within ten minutes expires, and the assistant can ask for a new one.
Every action - gated or not - lands in the audit log with the assistant's identity attached, so the activity trail always shows what was done by AI and what was done by hand.
Open, closed, on-hold, cancelled, active - stamped on the activity log with the assistant's identity, after you approve.
update_project_status
Attach a note to any project or file a field report from a conversation recap.
attach_note_to_project, submit_field_report
Adds a job to a tech's daily route in DrillerDB's route planner.
plan_crew_route
Books a project to a date and crew. Detects double-booking and refuses to overwrite - and waits for your approval first.
schedule_project
Sends the dispatch email or text to the field tech - the same one the Dispatch Crew button sends - after you approve it.
dispatch_project
Emails the invoice to your customer through DrillerDB's send flow. Nothing leaves the building until you approve it.
send_invoice
Brings a vendor invoice into DrillerDB, after you approve it.
import_vendor_invoice
This is the complete surface your AI assistant gets - exactly what the server exposes, nothing more. Tools marked with * are approval-gated.
list_my_projects, get_project_detail, list_projects_by_customer, get_project_financials, get_job_profitability, list_customers, list_contacts, list_invoices, get_invoice_detail, list_proposals, get_proposal_detail, get_company_proposal_habits, get_quote_detail, get_quote_engagement, list_work_orders, get_work_order_detail, list_crews, query_schedule, list_field_reports, list_project_files, list_communications, get_communication_detail, list_equipment, get_equipment_detail, get_maintenance_due, list_inventory, list_timecards, get_timecard_summary, get_compliance_form, get_project_compliance_status, query_well_logs, get_geology_at_location, customer_ltv_report, total_billed_by_contact, revenue_pipeline, ar_aging_report, run_report
attach_note_to_project, submit_field_report, plan_crew_route, update_project_status*, schedule_project*, dispatch_project*, import_vendor_invoice*, send_invoice*
Technical details - OAuth scopes, troubleshooting, and client setup - live on the connector setup page.
No IT department required. If you can log in to DrillerDB, you can connect your AI assistant in a few minutes.
In your AI client (Claude, ChatGPT, Cursor, Codex), add a custom connector with the server URL "https://mcp.drillerdb.com". Your client discovers the sign-in flow automatically.
A standard OAuth 2.0 sign-in with your existing DrillerDB email and password. No API keys to copy, no tokens to manage. Access is scoped to your company only.
Start with "What's on the schedule tomorrow?" or "Who owes us money past 60 days?" Your assistant pulls live answers from your account.
Your customer list and your receivables are your business. The connector treats them that way.
You authorize the connector with your DrillerDB login through a standard OAuth flow. There is no API key to leak, share, or rotate.
Every request is locked to the company on your sign-in, derived from your token - never from anything the AI types. The connector cannot read another company's data.
Sending an invoice, changing a job's status, scheduling or dispatching a job, importing a vendor bill - these pause and wait for your explicit approval in DrillerDB before they run.
All 45 tools record who called them, what was asked, when, and the outcome. You can always see exactly what the assistant did.
The server enforces per-client rate limits (100 calls/minute, 1,000/hour), so a runaway session can't hammer your account.
Remove the connector in your AI client to stop using it there. Contact support if you also need help revoking its DrillerDB authorization.
Connector data handling is covered in our Privacy Policy.
We'd rather you know the edges up front than find them mid-conversation.
The only customer-facing send is an invoice through DrillerDB's own send flow - and it waits for your approval. There is no general 'send a message' capability.
Writes today are: notes, field reports, crew route planning, job status, scheduling, dispatch, vendor bill import, and invoice send. Line-item editing stays in the app.
There is no delete tool. The closest action is setting a job's status to cancelled - which is visible and reversible in DrillerDB.
It can list the files already attached to a project, but uploads still happen in DrillerDB directly.
The assistant reads your DrillerDB account. If well logs or invoices were never entered, it can't conjure them.
Want a capability prioritized? Email craig@drillerdb.com. We move fast on customer requests.
Already on DrillerDB? Connect your AI assistant in minutes. Not yet? See the whole platform in a 30-minute demo.
