← All integrations

GageList MCP server

18 operations0 webhooks

Gauge calibration management with GageList - manage gages and their calibration records, read calibration certificates, and manage manufacturers, custom field values and the account's plan limits.

Use GageList in Claude, ChatGPT, Cursor or another MCP client

Connect GageList once in Corsair, then add one MCP address to your agent.

Connect GageList
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try GageList with your agent

Connect GageList, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in GageList on my account, then run one read-only example and show me the result.

Runs once, when you ask

GageList tools and triggers

Tools are what your agent can do in GageList through Corsair's MCP server. Triggers are the GageList events a routine can start from.

Calibrations

  • CertificateRead-only

    Render a calibration certificate PDF for a record, returned base64-encoded with its content type

    calibrations.certificate

  • CreateWrite

    Record a calibration against a gage, with the readings, standard used and next due date

    calibrations.create

  • DeleteDestructive

    Delete a calibration record

    calibrations.delete

  • GetRead-only

    One calibration record with its as-found and as-left readings

    calibrations.get

  • ListRead-only

    Calibration records, paged; each names the gage it was run on through `EquipmentRefId`

    calibrations.list

  • UpdateWrite

    Update a calibration record

    calibrations.update

Gages

  • CreateWrite

    Add a gage, with its serial and control numbers, calibration interval and responsible user

    gages.create

  • DeleteDestructive

    Delete a gage. GageList marks it deleted rather than erasing it, but it stops appearing in the active list

    gages.delete

  • GetRead-only

    One gage with its calibration dates, interval and assigned user

    gages.get

  • ListRead-only

    Gages on the site, paged by `start` and `record_number` in the request body; `next_start` gives the next page

    gages.list

  • UpdateWrite

    Update a gage. The body is the whole record with its `Id`, not a partial patch

    gages.update

Manufacturers

  • CreateWrite

    Add a manufacturer with its address and contact details

    manufacturers.create

Connect GageList to Claude, ChatGPT or Cursor

  1. 1

    Connect GageList in Corsair

    Add your GageList API key once in Corsair. Corsair stores the credential encrypted and makes the GageList API calls for your agent, so it never goes into a prompt or a config file. Connect GageList

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs GageList. On a ChatGPT personal plan, connect GageList here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, GageList's read and write operations run right away and its 3 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/gagelist, add the GageList plugin, and connect with an API key. Then call methods like corsair.gagelist.api.account.status() from your app. Corsair keeps each tenant isolated.

Yes. GageList requires an API key from your GageList account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit GageList, GitHub, Notion, Stripe, and the rest. Trigger GageList from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for gauge calibration management with GageList - manage gages and their calibration records, read calibration certificates, and manage manufacturers, custom field values and the account's plan limits. Common builds include sync jobs, admin tooling, and agents that call GageList APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per GageList API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/gagelist in the open repo. When GageList ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your GageList data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store GageList data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put GageList on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 3 destructive GageList operations. You can change a link's mode at hub.corsair.dev/me.