ifr_generate_workpaper — ifrCoworker MCP Tool
ifr_generate_workpaper
(ifr generate workpaper) is one of 21 tools on the
ifrCoworker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ifr_generate_workpaper from your client
- Claude Code ifrCoworker ifr_generate_workpaper run in your project directory
- Claude Desktop ifrCoworker ifr_generate_workpaper ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ifrCoworker ifr_generate_workpaper ~/.cursor/mcp.json
- VS Code ifrCoworker ifr_generate_workpaper .vscode/mcp.json
- Zed ifrCoworker ifr_generate_workpaper ~/.config/zed/settings.json
- Windsurf ifrCoworker ifr_generate_workpaper ~/.codeium/windsurf/mcp_config.json
- Cline ifrCoworker ifr_generate_workpaper ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ifrCoworker ifr_generate_workpaper ~/.gemini/settings.json
- Grok ifrCoworker ifr_generate_workpaper .mcp.json (in your project root)
- ChatGPT ifrCoworker ifr_generate_workpaper Settings → Connectors → Advanced → Developer mode
- Claude.ai ifrCoworker ifr_generate_workpaper Settings → Connectors → Add custom connector
- LangChain ifrCoworker ifr_generate_workpaper pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ifrcoworker https://mcp.ifrcoworker.com
Other tools on this server
- ifr_schema
- ifr_validate
- ifr_calculate
- ifr_apply_ias10
- ifr_route_event
- ifr_input_schema
- ifr_period_checklist
- ifr_period_end_batch
- ifr_batch_validate
- ifr_ingest_document
- ifr_propose_mapping
- ifr_flag_result
- ifr_explain_result
- ifr_disclosure_checklist
- ifr_replay
- ifr_ecl_provision_matrix
- ifr_cgu_impairment
- ifr_check_quota
- ifr_amortisation_schedule
- ifr_calculation_sheets
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.