Codex can connect to streamable HTTP MCP servers from the CLI and the IDE extension. Adding Requidex MCP gives Codex read-only access to documented Requidex Open API operations and Requidex Intercom help guides while it works on code, analysis, or integration tasks.

Codex reads the server instructions returned by the Requidex MCP server and uses OAuth for user authentication.

​

Add a Requidex MCP server entry to ~/.codex/config.toml. In a trusted project, you can use .codex/config.toml instead if the configuration should be scoped to that project.

Use this TOML configuration: `[mcp_servers.requidex]`, `url = "https://api.requidex.com/mcp"`, `enabled = true`, and `default_tools_approval_mode = "prompt"`.

​

​

Ask Codex to use Requidex when it needs live Open API context. The server exposes read-only Open API operations, so Codex can inspect Requidex data but cannot make workflow changes in Requidex.

When prompts include company, project, agency, site, or trade names, Codex can use lookup tools to resolve those names to ids before calling filtered Open API tools.

For spend, total, count, ranking, top-N, or grouped analysis questions, Codex can use the relevant summary tool for invoices, assignments, timesheets, requisitions, expenses, or credit notes instead of fetching raw rows.

For list tools that support field selection, Codex can use the availableFields returned by list_open_api_operations or the fields shown in each tool description before setting the fields parameter.

For list tools that expose dateField, from and to apply to that selected date field. Use dateField when the user asks for start dates, end dates, week-ending dates, approval dates, confirmation dates, due dates, processed dates, or expense dates instead of creation dates.

Paginated tool calls default to 50 records, return at most 200 records per page, and can page through up to the first 10000 matching records. They include the total count so broad requests can be narrowed with filters. For count-only or existence checks on list tools, set limit=1 and read meta.total.

When the task is a product how-to, workflow, status, permission, setup, or troubleshooting question, Codex can use the search tool to find matching Requidex help guides and the fetch tool to read the full guide before answering.

For ambiguous prompts, name the server explicitly. For example: Use the Requidex MCP server to inspect the available Open API operations, then call the relevant project list tool.

​

List and summary tools support multi-company filtering, and many tools support multi-ID filtering for documented entity filters such as project, site, trade, worker, assignment, timesheet, requisition, and agency. Pass comma-separated ids where the tool description allows it. For example, company='id1,id2,id3' returns data for all three companies instead of requiring three separate calls.

List tools that support the fields parameter accept dot-path nested fields as well as top-level fields. For example, fields='worker.id,values.charge.total,values.charge.wdBasic' returns only those nested timesheet fields instead of the full values object.

List tools that support dateField apply from and to to the selected date field. For example, use dateField='weekEnding' for timesheet week filters, dateField='dateAccepted' for requisition agency acceptance filters, and dateField='issueDate' for invoice issue-date billing periods.

All summary tools support multi-dimensional aggregation through the groupBy parameter and grouped result sorting through sortBy, sortOrder, and limit. Use groupBy to break down results by one or more dimensions such as company, trade, agency, purchaseOrder, status, category, or month. For example, groupBy='company,trade' returns spend per trade per company in one call instead of N×M separate calls, and groupBy='agency' with sortBy='finalTotal' and limit=5 returns the top five agencies by invoice value. Allowed values vary by endpoint and are documented in each summary tool description.

The recruitment metrics list tool can return server-side aggregates by setting metric='timeToFill' or metric='workersOverHours'. These modes support agency and period filters, groupBy values such as agency, project, month, and week, compound groupBy values such as company,agency, the IQR outlier rule for time-to-fill, and a configurable weekly hours threshold for workers-over-hours.

Combining multi-ID filtering with groupBy enables powerful cross-entity analysis. For example, summarize_assignments with company='id1,id2,id3' and groupBy='trade,month' returns assignment spend broken down by trade and month across three companies in a single API call.

​

​

This connection signs in with the Requidex OAuth flow, which is available to hiring-company admin accounts. Agency and desk accounts cannot connect through this OAuth flow.