Gagelist for AI agents

GageList is a calibration management platform for tracking gages, calibration records, and manufacturer data for quality teams that must keep measurement equipment in compliance. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Developer toolsOAuth 2.0 client credentialsMCP + RESTgagelist.com
AUDIT LOG · GAGELISTPOLICY: acme-support
09:41:07 · claude · u_8f2read
gagelist.get_attachment
Get Attachment✓ allowed · 212ms
09:41:08 · claude · u_8f2read
gagelist.get_custom_fields
Get Custom Fields✓ allowed · 164ms
09:41:09 · claude · u_8f2write
gagelist.update_manufacturer
Update Manufacturer✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
gagelist.delete_gage_record
Delete Gage Record✕ blocked · policy: deny
EVERY GAGELIST CALL, ON THE RECORD
01 · USE CASES

What agents do in Gagelist.

01

Check a gage's calibration record

Get a gage's calibration history to confirm it is due for its next check.

02

Generate a calibration certificate

Generate a calibration certificate once a gage passes its scheduled inspection.

03

Confirm before deleting a gage record

Require approval before deleting a gage record, since it removes its full calibration history.

02 · ACTIONS

21 Gagelist actions, graded by risk.

Every Gagelist action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

9

Look things up. Allowed by default.

  • gagelist.get_attachment
    Get Attachment
  • gagelist.get_custom_fields
    Get Custom Fields
  • gagelist.get_account_status
    Get account status
  • gagelist.get_account_settings
    Get Account Settings
  • gagelist.get_all_gage_records
    Get All Gage Records
  • gagelist.get_all_manufacturers
    Get All Manufacturers
  • gagelist.get_single_gage_record
    Get Single Gage Record
  • gagelist.get_all_calibration_records
    Get all calibration records
  • gagelist.get_single_calibration_record
    Get Single Calibration Record

write

9

Create and change things. Allow, or ask the user first.

  • gagelist.add_gage_record
    Add Gage Record
  • gagelist.add_manufacturer
    Add Manufacturer
  • gagelist.update_manufacturer
    Update Manufacturer
  • gagelist.add_calibration_record
    Add Calibration Record
  • gagelist.update_account_settings
    Update Account Settings
  • gagelist.update_custom_field_values
    Update Custom Field Values
  • gagelist.authenticate_with_gagelist
    Authenticate with Gagelist
  • gagelist.generate_calibration_certificate
    Generate Calibration Certificate
  • gagelist.upload_attachment_to_gage_record
    Upload Attachment To Gage Record

destructive

3

Delete, cancel or archive. Ask first, or deny outright.

  • gagelist.delete_gage_record
    Delete Gage Record
  • gagelist.delete_manufacturer
    Delete Manufacturer
  • gagelist.delete_calibration_record
    Delete Calibration Record
03 · HOW IT WORKS

Gagelist in three steps.

  1. 01Your users connect GagelistThey add their Gagelist oauth 2.0 client credentials on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “update Manufacturer” can wait for the user, and “delete Gage Record” can be denied outright.
  3. 03Any agent can actYour agent calls Gagelist through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('gagelist', {
  read: 'allow',
  write: 'ask',        // update_manufacturer
  destructive: 'deny',  // delete_gage_record
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Gagelist connects.

Connect Gagelist with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

The same Gagelist connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 client credentials
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Gagelist from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Gagelist and Arc0, answered.

Q01

Can I use Gagelist with Claude, ChatGPT or Cursor?

Yes. Connect Gagelist to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Gagelist actions you allow.

Q02

How do users connect Gagelist?

Connect Gagelist with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

Q03

Which Gagelist actions can my agent take?

21 in total: 9 read, 9 write and 3 destructive, such as “update Manufacturer”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Gagelist?

Yes. Actions like “delete Gage Record” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Gagelist too?

Yes. The same Gagelist connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Gagelist into your agent.

Your users connect Gagelist once, under your brand. Your agent gets 21 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan