MCP server · v1
The ashiba.ai MCP server.
Point Claude — or any Model Context Protocol client — at your live job data. The same role-scoped key, the same cost rule, exposed as tools an agent can read and drive.
Calling from your own code instead of an agent? Every tool here has a matching HTTP endpoint — see the
REST API reference →Transport
JSON-RPC 2.0 over Streamable HTTP at https://www.ashiba.ai/api/mcp. It implements initialize, tools/list, and tools/call — no SDK required on either side.
Connect a client
Create a key in
Settings → API keys (company owners), then add the server to your MCP client with the key as a bearer token. It carries exactly your access, and is
read-only by default — a read+write key is an explicit opt-in that unlocks the write tools below.
{
"mcpServers": {
"ashiba": {
"url": "https://www.ashiba.ai/api/mcp",
"headers": { "Authorization": "Bearer ak_3f9c…" }
}
}
}
The cost rule
A sub- or client-scoped key never carries a cost or margin figure. The cost tools return an error for such a key, never a number — the same invariant the app and REST API enforce, held at the tool boundary.
Tools
58 tools. read works with any key; write needs a read+write key.
Projects
list_projectsget_projectcreate_projectupdate_project
Estimating & money
list_cost_itemslist_bidslist_paymentslist_change_orderslist_drawsadd_cost_itemupdate_cost_itemdelete_cost_itemadd_bidaward_biddelete_bidadd_paymentadvance_paymentdelete_paymentadd_change_orderadvance_change_orderadd_drawadvance_drawdelete_draw
Field
list_checklistlist_schedulelist_logslist_documentslist_permitslist_punchlist_inspectionstoggle_checklist_itemadd_checklist_itemupdate_checklist_itemdelete_checklist_itemadd_logdelete_logadd_documentupdate_documentdelete_documentadd_schedule_taskupdate_schedule_taskdelete_schedule_taskadd_permitadvance_permitadd_punch_itemtoggle_punch_itemdelete_punch_itemadd_inspectionset_inspection_status
Company
list_leadslist_vendorsadd_leadadvance_leadconvert_leaddelete_leadadd_vendorupdate_vendordelete_vendor
Call a tool
List the tools, then call one — the arguments mirror the REST bodies (e.g. a project id, a checklist title):
curl https://www.ashiba.ai/api/mcp \
-H "Authorization: Bearer ak_3f9c…" -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"list_projects","arguments":{}}}'