{
  "server": {
    "name": "Every Help Docs",
    "version": "1.0.0",
    "transport": "http"
  },
  "instructions": "This Model Context Protocol server provides search and retrieval tools for the Every Help Docs site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect, outdated, confusing, or incomplete — use the submit_feedback tool to report it to the docs team. Apart from the submit_feedback tool, the server is read-only and scoped to Every Help Docs; it does not otherwise perform actions, mutate state, or access anything beyond the published site content and these resources.",
  "capabilities": {
    "tools": {
      "listChanged": false
    },
    "resources": {
      "listChanged": false
    }
  },
  "tools": [
    {
      "name": "search_every_help_docs",
      "description": "Search across the Every Help Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Every Help Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "A query to search the content with."
          }
        },
        "required": [
          "query"
        ]
      },
      "operationId": "mintlify_default_search"
    },
    {
      "name": "query_docs_filesystem_every_help_docs",
      "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Every Help Docs documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il \"keyword\" /` to find where it is covered.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples (replace the placeholder paths with real ones from `tree` or search):\n- `tree / -L 2` — see the top-level directory layout\n- `rg -il \"rate limit\" /` — find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /some-directory/` — show matches with 3 lines of context around each hit\n- `head -80 /some/page.mdx` — read the top 80 lines of a specific page\n- `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call\n- `cat /some/page.mdx` — read a full page when you need everything\n- `head -100 /openapi/api-reference/openapi.yaml` — read the start of an OpenAPI spec\n\nOpenAPI specs for this site are mounted at: `/openapi/api-reference/openapi.yaml`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "command": {
            "type": "string",
            "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`)."
          }
        },
        "required": [
          "command"
        ]
      },
      "operationId": "mintlify_default_query_docs_filesystem"
    },
    {
      "name": "submit_feedback",
      "title": "Submit documentation feedback",
      "description": "Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "path": {
            "type": "string",
            "minLength": 1,
            "description": "The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension)."
          },
          "feedback": {
            "type": "string",
            "minLength": 1,
            "description": "A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing."
          }
        },
        "required": [
          "path",
          "feedback"
        ]
      },
      "operationId": "submit_feedback"
    }
  ],
  "resources": [
    {
      "uri": "mintlify://skills/every-accounting",
      "name": "every-accounting",
      "description": "Explains Every's Accounting menu (Expenses and QuickBooks sync, Accounting insights and financial statements, spending budgets), the Taxes guide (vendor 1099s, payroll tax settings and where to ask about corporate taxes and filings) and Settings → Accounting (QuickBooks connection, mappings, bookkeeping automations and receipt and reimbursement policies). Use when someone asks how to do something in Every's Accounting menu or Accounting settings, where to take a tax question, who can do it or why they can't.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-ai",
      "name": "every-ai",
      "description": "Explains AI chat in Every: opening conversations, asking about company data or your own records, reviewing proposed changes and returning to past conversations. Use for AI chat access, roles, approvals and employee questions.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-banking",
      "name": "every-banking",
      "description": "Explains Every's business banking: the checking account, moving money, transactions and receipts, company cards, the credit card and Treasury. Use when someone asks how to do something in Every's Banking menu, on My cards or on My transactions, who can do it, or why they can't.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-benefits",
      "name": "every-benefits",
      "description": "Explains Every's company benefits for Company Admins and HR Admins, and employees' own benefits. Covers health and financial enrollment, waivers, life-event changes, benefit cards, retirement review and company benefit setup. Use for benefit choices, changes and statuses.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-compliance",
      "name": "every-compliance",
      "description": "Explains the rules the law sets that Every's Compliance guides cover, for managers and for employees: yearly tax deadlines, Delaware's franchise tax, corporate income tax and Form 7004, exempt status, minimum wage and overtime, state paid leave, disability insurance and the FMLA, who gives a W-9 and who gets a 1099-NEC, commuter benefit requirements and final paycheck deadlines, and where each rule touches Every. Use when someone asks what the law requires, of whom, by when or where, or where Every records it. General rules only, not legal or tax advice.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-mcp",
      "name": "every-mcp",
      "description": "Explains Every MCP connections: personal tokens, client setup, read-only tools, role limits and revocation. Use for connecting Claude Code, Claude Desktop, Cursor, Windsurf or Codex and for employee MCP questions.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every-payments",
      "name": "every-payments",
      "description": "Explains Every's Payments: the All payments page, uploading bills to the Inbox, approvals, Send money, paying a vendor abroad, reimbursements, vendors, collecting vendor details and 1099s. Use when someone asks how to do something in Every's Payments menu, such as pay a vendor, approve a bill or request a 1099, who can do it, or why they can't.",
      "mimeType": "text/markdown"
    },
    {
      "uri": "mintlify://skills/every",
      "name": "every",
      "description": "Index to Every's help docs, which cover getting started, banking, payments, accounting, people, payroll, time, benefits, reports, documents, compliance, AI chat, MCP, settings and pages for employees. Use first when someone asks how to do something in Every: it points to the right area and says how to read these docs.",
      "mimeType": "text/markdown"
    }
  ]
}