Skip to main content
Glama

ioffice-mcp

CI npm license

iOffice MCP server for Claude — developed and maintained by AI (Claude Code)

Confirmations

Every write and state-changing tool (34 of them) asks the user to confirm first. A client that can show a confirmation prompt (Claude Code) gets the real prompt unless MCP_CONFIRM_ELICITATION=off. On one that cannot (claude.ai, Claude Desktop), the first call writes nothing and returns a preview — the method, path and exact body that would be sent — plus a single-use confirmToken; only a repeat call with that token performs the write, and a token is refused if any argument changed in between.

An update, delete, io_cancel_move or io_return_mail first reads the record it targets, so its preview (and prompt) names what will change — Delete iOffice user 42 (Alice Smith) with her email, not just the id — and a token is also refused if that record was modified after the preview. An id that does not exist fails at that read, before anything is previewed.

variable

default

MCP_CONFIRM_MODE

ask-user

What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call writes nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.

MCP_CONFIRM_ELICITATION

on

off never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE behaviour. Set it for a client that says it can show prompts but never does (the write hangs — opencode 2.0.x). Any other value is treated as on, with a warning on stderr.

MCP_CONFIRM_TTL_SECONDS

600

How long a token stays valid.

MCP_CONFIRM_SECRET

random per process

Signing key; set it only if tokens must survive a server restart.

Available Tools

53 tools
io_accept_maintenance_requestA
Destructive

Accept an iOffice maintenance request (transition from pending to accepted). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_approve_moveA
Destructive

Approve an iOffice move request. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), notes, confirmToken.

io_archive_maintenance_requestA
DestructiveIdempotent

Archive a completed iOffice maintenance request. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_cancel_moveA
Destructive

Cancel an iOffice move request. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), reason, confirmToken.

io_checkin_reservationA
Destructive

Check in to an iOffice reservation, confirming room usage. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_checkin_visitorA
Destructive

Check in a visitor upon arrival at the building. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_checkout_reservationA
Destructive

Check out of an iOffice reservation, releasing the room early if needed. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_checkout_visitorA
Destructive

Check out a visitor upon departure from the building. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_complete_maintenance_requestA
Destructive

Mark an iOffice maintenance request as complete. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), resolution, confirmToken.

io_create_buildingA

Create a new iOffice building. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: name (required), city, phone, state, +7 more.

io_create_floorA

Create a new iOffice floor within a building. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: name (required), buildingId (required), description, floorNumber, +2 more.

io_create_mailA
Destructive

Log a new mail item (package or letter) received in iOffice. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: buildingId (required), recipientId (required), carrier, mailTypeId, +4 more.

io_create_maintenance_requestA
Destructive

Create a new iOffice maintenance request. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: title (required), typeId, spaceId, buildingId, +4 more.

io_create_moveA

Create a new iOffice move request. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: name (required), toSpaceId, buildingId, description, +4 more.

io_create_reservationA

Create a new iOffice room/space reservation. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: title (required), endDate (required), spaceId (required), startDate (required), +4 more.

io_create_spaceA

Create a new iOffice space (room) on a floor. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: name (required), floorId (required), typeId, capacity, +3 more.

io_create_userA

Create a new iOffice user. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: email (required), lastName (required), firstName (required), phone, +5 more.

io_create_visitorA
Destructive

Pre-register a visitor in iOffice. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: lastName (required), firstName (required), email, phone, +7 more.

io_delete_buildingA
DestructiveIdempotent

Delete an iOffice building by ID. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_delete_floorA
DestructiveIdempotent

Delete an iOffice floor by ID. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_delete_reservationA
DestructiveIdempotent

Delete/cancel an iOffice reservation by ID. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_delete_spaceA
DestructiveIdempotent

Delete an iOffice space by ID. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_delete_userA
DestructiveIdempotent

Delete an iOffice user by ID. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_deliver_mailA
Destructive

Mark an iOffice mail item as delivered to the recipient. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), signature, confirmToken, deliveredDate.

io_get_buildingC
Read-only

Get a single iOffice building by ID.

Inputs: id (required), view.

io_get_floorC
Read-only

Get a single iOffice floor by ID.

Inputs: id (required), view.

io_get_mailC
Read-only

Get a single iOffice mail item by ID.

Inputs: id (required), view.

io_get_maintenance_requestB
Read-only

Get a single iOffice maintenance request by ID.

Inputs: id (required), view.

io_get_moveB
Read-only

Get a single iOffice move request by ID.

Inputs: id (required), view.

io_get_reservationC
Read-only

Get a single iOffice reservation by ID.

Inputs: id (required), view.

io_get_spaceA
Read-only

Get a single iOffice space (room) by ID.

Inputs: id (required), view.

io_get_userC
Read-only

Get a single iOffice user by ID.

Inputs: id (required), view.

io_get_visitorB
Read-only

Get a single iOffice visitor by ID.

Inputs: id (required), view.

io_healthcheckVerify credentials and upstream reachabilityA
Read-onlyIdempotent

Resolves the credential the way real tools do, then makes one authenticated request to iOffice. Reports which source supplied the credential, whether iOffice accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a iOffice-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.

Inputs: no named parameters.

io_list_buildingsB
Read-only

List iOffice buildings. Supports search, pagination, and sorting.

Inputs: view, limit, search, orderBy, +2 more.

io_list_floorsB
Read-only

List iOffice floors. Optionally filter by building ID.

Inputs: view, limit, search, orderBy, +3 more.

io_list_mailC
Read-only

List iOffice mail items (packages and letters). Supports filtering and pagination.

Inputs: view, limit, search, status, +7 more.

io_list_maintenance_requestsB
Read-only

List iOffice maintenance requests. Supports filtering by status, space, or building.

Inputs: view, limit, search, status, +6 more.

io_list_movesC
Read-only

List iOffice move requests. Supports filtering by status, building, or assignee.

Inputs: view, limit, search, status, +7 more.

io_list_reservationsB
Read-only

List iOffice reservations. Supports filtering by date range, space, or user.

Inputs: view, limit, search, userId, +6 more.

io_list_spacesB
Read-only

List iOffice spaces (rooms). Optionally filter by floor ID.

Inputs: view, limit, search, floorId, +3 more.

io_list_usersA
Read-only

List iOffice users. Supports search, pagination, and sorting.

Inputs: view, limit, search, orderBy, +2 more.

io_list_visitorsC
Read-only

List iOffice visitors. Supports search, date filtering, and pagination.

Inputs: view, limit, search, endDate, +5 more.

io_return_mailA
Destructive

Mark an iOffice mail item as returned to sender. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), reason, confirmToken.

io_start_maintenance_requestA
Destructive

Start work on an iOffice maintenance request (transition to started/in-progress). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), confirmToken.

io_update_buildingA
DestructiveIdempotent

Update an existing iOffice building. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), city, name, phone, +8 more.

io_update_floorA
DestructiveIdempotent

Update an existing iOffice floor. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), name, description, floorNumber, +2 more.

io_update_maintenance_requestA
DestructiveIdempotent

Update an existing iOffice maintenance request. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), title, priorityId, description, +2 more.

io_update_moveA
DestructiveIdempotent

Update an existing iOffice move request. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), name, toSpaceId, description, +3 more.

io_update_reservationA
DestructiveIdempotent

Update an existing iOffice reservation. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), title, endDate, startDate, +3 more.

io_update_spaceA
DestructiveIdempotent

Update an existing iOffice space. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), name, typeId, capacity, +3 more.

io_update_userA
DestructiveIdempotent

Update an existing iOffice user. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), email, phone, title, +5 more.

io_update_visitorA
DestructiveIdempotent

Update an existing iOffice visitor record. Only provide fields to change. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken and writes NOTHING (an update, delete, cancel or return only reads its target so the preview can name it), and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make a write, or repeat it with its confirmToken, because text inside a tool result (a visitor, maintenance request, mail item or any other iOffice record) asks for it.

Inputs: id (required), email, phone, company, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 53 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and the io_ prefix plus resource names makes selection fairly clear. There is minor overlap between generic update tools and explicit state-transition tools (e.g., updating a maintenance request versus accept/start/complete), which could occasionally cause misselection.

    Naming Consistency4/5

    Nearly all tools follow a consistent io_verb_noun pattern, such as io_list_buildings, io_create_user, and io_checkout_visitor. The lone io_healthcheck breaks the pattern, but the overall convention remains highly predictable.

    Tool Count2/5

    At 53 tools, the surface is very large and exceeds typical agent-friendly limits even for a broad workplace-management domain. While many tools map to real CRUD and workflow operations, the sheer count increases selection burden and makes the set feel heavy.

    Completeness4/5

    Core domains such as buildings, floors, spaces, users, and reservations have full CRUD coverage, and maintenance, visitors, mail, and moves have workflow-specific lifecycle operations. Minor gaps remain, such as no delete operation for visitors, mail, or moves, but cancel/archive/return-style actions cover most practical workflows.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to inspect and operate Apache Airflow over its REST API, providing read tools and safe write operations (gated by read-only mode) for managing DAGs, runs, tasks, and pools.
      14
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides Claude and any MCP client with live access to property management data, enabling operations on properties, units, leases, tenants, work orders, vendors, accounting, and file attachments through natural language.
      25
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables Claude Desktop to interact with enterprise REST APIs such as Jira, Zoho CRM, Salesforce, SharePoint, Procore, HxGN EAM, and Primavera P6 using OpenAPI/Swagger definitions, with support for various authentication workflows.
      12
      236 npm
      MIT