4dayweek-io MCP API

openapi: 3.2.0
info:
  title: 4dayweek Io MCP API
  version: 1.0.0
  contact:
    name: 4dayweek.io
    url: https://4dayweek.io/contact
  license:
    name: Free for public use; link-back requested.
  description: 'Operations tagged mcp across 2 of this provider''s published API definitions: 4dayweek-io-openapi.yaml, 4dayweek-io.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://4dayweek.io
  description: Production
tags:
- name: MCP
  description: Read-only Model Context Protocol endpoint for AI assistants. JSON-RPC over streamable HTTP, so it does not follow REST conventions and is described here only so that a client generated from this spec knows the path exists.
  externalDocs:
    description: MCP server documentation
    url: https://4dayweek.io/mcp
paths:
  /api/mcp:
    post:
      tags:
      - MCP
      summary: Model Context Protocol endpoint (JSON-RPC 2.0)
      description: 'The MCP server''s single endpoint. It speaks JSON-RPC 2.0 over the streamable-HTTP transport, NOT REST: the method, the parameters and the result all live in the JSON body, so the request and response schemas below are deliberately loose. Use an MCP client library rather than a generated REST client.


        Six read-only tools are advertised: `search_jobs`, `get_job`, `search_companies`, `get_company`, `get_market_stats` and `explain_schedule_type`. No authentication. Rate limited separately from the REST endpoints at 300 requests per minute per IP sustained, bursting to 60 (the value `X-RateLimit-Limit` reports).


        Setup instructions for every client: https://4dayweek.io/mcp'
      externalDocs:
        description: MCP specification
        url: https://modelcontextprotocol.io
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              description: A JSON-RPC 2.0 request or notification.
              required:
              - jsonrpc
              - method
              properties:
                jsonrpc:
                  type: string
                  enum:
                  - '2.0'
                id:
                  description: Absent on a notification.
                  oneOf:
                  - type: string
                  - type: integer
                method:
                  type: string
                  example: initialize
                params:
                  type: object
            example:
              jsonrpc: '2.0'
              id: 1
              method: initialize
              params:
                protocolVersion: '2025-06-18'
                capabilities: {}
                clientInfo:
                  name: example-client
                  version: 1.0.0
      responses:
        '200':
          description: 'A JSON-RPC response. The content type depends on what the client sent in `Accept`: `application/json` for a single response, or `text/event-stream` when the reply is streamed. Both must be accepted — an MCP client sends both in `Accept`.'
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                    enum:
                    - '2.0'
                  id:
                    oneOf:
                    - type: string
                    - type: integer
                  result:
                    type: object
                  error:
                    type: object
            text/event-stream:
              schema:
                type: string
        '400':
          description: Malformed JSON-RPC, or a missing/unacceptable Accept header.
        '429':
          $ref: '#/components/responses/RateLimited'
      operationId: postApiMcp
      x-operation-id-source: derived
    get:
      tags:
      - MCP
      summary: Not supported on this deployment
      description: The server runs in stateless mode, so there is no session to attach a standalone server-to-client SSE stream to and nothing to push down one. A GET returns 405. Send requests with POST.
      responses:
        '405':
          description: Method not allowed.
      operationId: getApiMcp
      x-operation-id-source: derived
    servers:
    - url: https://4dayweek.io
      description: Production
components:
  schemas:
    ErrorResponse:
      type: object
      required:
      - error
      properties:
        error:
          type: object
          required:
          - code
          - message
          properties:
            code:
              type: integer
              example: 400
            message:
              type: string
              example: invalid sort
            field:
              type: string
            error_code:
              type: string
              description: Machine-readable code, present for some errors.
              example: NOT_YET_PUBLIC
            data:
              type: object
              description: Extra detail for the code, when there is any.
              example:
                available_at: '2026-10-09T12:00:00Z'
  responses:
    RateLimited:
      description: Rate limit exceeded (60 req/min per IP).
      headers:
        Retry-After:
          schema:
            type: integer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
x-refined-from:
- 4dayweek-io-openapi.yaml
- 4dayweek-io.yaml