Oyster MCP by usefulapi

Read team, time off, expenses and invoices; approve or decline time off and expenses in Oyster.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
99%
Integridad del esquema
93%
Calidad de los nombres
79%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (1)

  • LOWTool 'oyster_approve_time_off_request' name length outside 3-30 rangeen oyster_approve_time_off_request

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~3,676Tokens (definiciones de herramientas)
~1.2 KBTamaño de respuesta típico
Impacto significativo en la atención (2.87% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "oyster": {
      "url": "https://oyster.usefulapi.io/mcp"
    }
  }
}

Puntos de conexión remotos

https://oyster.usefulapi.io/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (20)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢oyster_get_company

The connected Oyster company: id, name, registration number and corporate/billing addresses. GET /v1/company.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_team_members(page, per_page)

List the company's team members (Oyster engagements: EOR employees, contractors, payroll team members) with name, role, type, state, country, start date, department and work email. Private details (date of birth, addresses, phones, salary, tax id) are left out; use oyster_get_team_member for one person. GET /v1/engagements.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_team_member(engagement_id, include_compensation, include_personal_details)

One team member (engagement) with employment or contract details, department, benefits and terminations. Salary only with include_compensation; date of birth, addresses, phone numbers and citizenships only with include_personal_details. A contractor's tax id is never returned. GET /v1/engagements/{id}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "engagement_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Engagement ID (from the matching list tool)."
    },
    "include_compensation": {
      "description": "Also return the salary (employees). Default false.",
      "type": "boolean"
    },
    "include_personal_details": {
      "description": "Also return date of birth, addresses, phone numbers and citizenships. Default false.",
      "type": "boolean"
    }
  },
  "required": [
    "engagement_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_departments(page, per_page)

List the company's departments with their description and number of team members. GET /v1/departments.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_time_off_requests(engagement_ids, page, per_page)

List time off requests with person, dates, type, state, reason and comments, optionally for some team members only. GET /v1/time_off/requests.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "engagement_ids": {
      "description": "Only these engagement IDs.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 200
      }
    },
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_time_off_request(time_off_request_id)

One time off request with dates, day durations, hours, state, type, reason, comments and attachment. GET /v1/time_off/requests/{id}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "time_off_request_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Time off request ID (from the matching list tool)."
    }
  },
  "required": [
    "time_off_request_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_time_off_balances(page, per_page)

Time off entitlements per team member, in days: annual entitlement, accrued, carried over, adjusted, taken, available, upcoming and projected balance. GET /v1/time_off/entitlements.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_public_holidays(start_date, end_date, country_code, subdivision_code, engagement_id, ...)

Public holidays between two dates (up to two years ahead) for a country (ISO code, optional subdivision) or for a team member's location. GET /v1/public_holidays.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day, YYYY-MM-DD."
    },
    "end_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Last day, YYYY-MM-DD."
    },
    "country_code": {
      "description": "ISO 3166-1 alpha-2 country code, e.g. DE.",
      "type": "string",
      "pattern": "^[A-Za-z]{2}$"
    },
    "subdivision_code": {
      "description": "Subdivision (state/region) code, with country_code.",
      "type": "string",
      "minLength": 1,
      "maxLength": 20
    },
    "engagement_id": {
      "description": "A team member's engagement ID: their location's holidays.",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "required": [
    "start_date",
    "end_date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_expenses(query, review_states, page, per_page)

List team members' expenses with amount, category, dates, review state (UNREVIEWED, APPROVED, DECLINED) and receipt link. Search by name and filter by review state. GET /v1/expenses.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Search expenses by name.",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "review_states": {
      "description": "Only these review states.",
      "maxItems": 3,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "APPROVED",
          "DECLINED",
          "UNREVIEWED"
        ]
      }
    },
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_expense(expense_id)

One expense with amount, receipt amount, category, dates, review state, receipt link and team member. GET /v1/expenses/{id}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "expense_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Expense ID (from the matching list tool)."
    }
  },
  "required": [
    "expense_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_contract_changes(page, per_page)

List contract change requests for all team members (position, compensation, bonus, allowance changes) with state, effective date, requester and the changes. GET /v1/contract_changes.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_contract_change(contract_change_id)

One contract change with the requested changes, state, dates, team member and amendment documents. GET /v1/contract_changes/{id}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "contract_change_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Contract change ID (from the matching list tool)."
    }
  },
  "required": [
    "contract_change_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_invoices(payroll_period_from, payroll_period_to, issue_date_from, issue_date_to, statuses, ...)

List the company's Oyster invoices with type, status, payroll month, issue and due dates, amount, charge (payment) status and payout status. Filter by payroll period, issue date, type, status, charge status or team member. GET /v1/invoices.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "payroll_period_from": {
      "description": "Payroll period from, YYYY-MM.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}$"
    },
    "payroll_period_to": {
      "description": "Payroll period to, YYYY-MM.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}$"
    },
    "issue_date_from": {
      "description": "Issued on or after, YYYY-MM-DD.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "issue_date_to": {
      "description": "Issued on or before, YYYY-MM-DD.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "statuses": {
      "description": "Only these invoice statuses.",
      "maxItems": 6,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "DISPUTED",
          "VOIDED",
          "WAITING_APPROVAL",
          "READY_FOR_REVIEW",
          "APPROVED",
          "AUTO_APPROVED"
        ]
      }
    },
    "charge_statuses": {
      "description": "Only these charge (payment) statuses, e.g. OVERDUE.",
      "maxItems": 10,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "PENDING",
          "DIRECT_DEBIT_IN_PROGRESS",
          "DIRECT_DEBIT_FAILED",
          "CHARGED_BACK",
          "PAID",
          "WAITING_FOR_WIRE_TRANSFER",
          "NO_PAYMENT",
          "OVERDUE",
          "PARTIALLY_PAID",
          "VOIDED"
        ]
      }
    },
    "types": {
      "description": "Only these invoice types, e.g. PREFUNDING, SETTLEMENT, OYSTER_FEES, EXPENSES.",
      "maxItems": 25,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[A-Z_]{2,40}$"
      }
    },
    "reference_codes": {
      "description": "Only these invoice reference codes.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      }
    },
    "engagement_ids": {
      "description": "Only these engagement IDs.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 200
      }
    },
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_invoice(invoice)

One invoice by ID or reference code, with line items, tax, applied credit, charge, payout and document links. GET /v1/invoices/{identifier}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "invoice": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Invoice ID or reference code."
    }
  },
  "required": [
    "invoice"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_list_time_sheets(page, per_page)

List time sheets with team member, period, cadence, status (PENDING_SUBMISSION, SUBMITTED, PENDING_APPROVAL, APPROVED) and worked/time-off totals. GET /v1/time_tracking/time_sheets.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "description": "Page number, from 1 (meta.pages is the page count).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10000
    },
    "per_page": {
      "description": "Results per page (1-100).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢oyster_get_time_sheet(time_sheet_id)

One time sheet with totals, work summary, time off days and the daily entries. GET /v1/time_tracking/time_sheets/{id}.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "time_sheet_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Time sheet ID (from the matching list tool)."
    }
  },
  "required": [
    "time_sheet_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡oyster_approve_time_off_request(time_off_request_id)

WRITE: approve a pending time off request. Only on the user's explicit request; check the request with oyster_get_time_off_request first. Needs the manage scope. POST /v1/time_off/requests/{id}/approve.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "time_off_request_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Time off request ID (from the matching list tool)."
    }
  },
  "required": [
    "time_off_request_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴oyster_reject_time_off_request(time_off_request_id, reason)

WRITE: reject a pending time off request with a reason the team member sees. Only on the user's explicit request. Needs the manage scope. POST /v1/time_off/requests/{id}/reject.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "time_off_request_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Time off request ID (from the matching list tool)."
    },
    "reason": {
      "type": "string",
      "minLength": 1,
      "maxLength": 1000,
      "description": "Why the request is rejected (shown to the team member)."
    }
  },
  "required": [
    "time_off_request_id",
    "reason"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡oyster_approve_expense(expense_id)

WRITE: approve an unreviewed expense for reimbursement. Only on the user's explicit request; check it with oyster_get_expense first. Needs the manage scope. POST /v1/expenses/{id}/approve.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "expense_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Expense ID (from the matching list tool)."
    }
  },
  "required": [
    "expense_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴oyster_decline_expense(expense_id, reason)

WRITE: decline an unreviewed expense, optionally with a reason the team member sees. Only on the user's explicit request. Needs the manage scope. POST /v1/expenses/{id}/decline.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "expense_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Expense ID (from the matching list tool)."
    },
    "reason": {
      "description": "Why the expense is declined (shown to the team member).",
      "type": "string",
      "minLength": 1,
      "maxLength": 1000
    }
  },
  "required": [
    "expense_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada20 herramientas