Reported issues for iconnect
Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to iconnect.
Most discussed
list_notes, search_notes, list_reminders, search_reminders fail with output validation error; update_note approval prompt never surfaces
Environment
AirMCP: latest via npx airmcp macOS: 26.3.1 Node.js: 25.8.2 MCP Client: Claude Desktop (Cowork mode) npx airmcp doctor: 19 passed, 2 warnings (Swift bridge not built, npm registry check)
Bug 1: Output validation errors on list/search tools list_notes, search_notes, list_reminders, and search_reminders all fail with: MCP error -32602: Output validation error: Tool [tool_name] has an output schema but no structured content was provided These tools declare an output schema, but the se
Read the thread · 2026-03-28 · closed · external user · 2 comments
Document all environment variables in README
What
Add an "Environment Variables" section to the README listing all `AIRMCP_*` and `GEMINI_API_KEY` variables with descriptions and defaults.
Why
The variables are defined in `src/shared/constants.ts` and `src/shared/config.ts` but there's no user-facing reference. Users have to read source code to discover configuration options.
How
- Grep `src/shared/constants.ts` and `src/shared/config.ts` for all `process.env` references
- Create a table in README with: Vari
Read the thread · 2026-03-15 · closed · 1 comment
Improve error messages when macOS permissions are missing
What
When a tool fails because of missing macOS permissions (Automation, Full Disk Access, etc.), the error message should clearly tell the user which permission is needed and how to grant it.
Current Behavior
JXA throws generic errors like `osascript error: Application isn't running` or `-1743` (permission denied).
Expected Behavior
Catch common JXA error codes and return actionable messages:
- `-1743`: "Permission denied. Grant Automation access: System Settings > Privacy
Read the thread · 2026-03-15 · closed · 1 comment
bug(finder): search_files / recent_files return 0 results when folder is omitted (Zod v4 .default() bypasses the ~ transform)
Summary
When folder is omitted, search_files and recent_files always return {"total": 0, "files": []}. Passing folder explicitly — including "~" — works correctly. The default value never goes through the ~ → $HOME transform.
Environment
- airmcp 2.16.5 (installed via
npm install -g airmcp) - macOS 26.5 (Darwin 25.5.0), Apple Silicon
- zod 4.4.3 (bundled dependency)
Reproduction
Call search_files over stdio with a query that is known to match:
| arguments | res
Read the thread · 2026-08-21 · open · external user · 0 comments
test(reminders): add script ↔ outputSchema shape contract (*_EXAMPLE) for reminders JXA scripts
Problem
tests/script-shape-contract.test.js guards against a silent drift class: scripts.ts changing the JSON it emits without the matching outputSchema update (or vice versa). Runtime tests mock runJxa, so the mock return value becomes structuredContent verbatim — they cannot catch this drift.
That contract currently exists only for messages, shortcuts, and health. The reminders module has outputSchema-bearing tools (list_reminders, search_reminders, read_reminder, list_rem
Read the thread · 2026-07-29 · closed · 0 comments
Calendar tools can return empty results after permission grant because EventKit store is not refreshed
AirMCP Version
2.11.0
Module
calendar
What happened?
Summary
First is first: I am not a programmer or use github. I asked Hermes to fix the issue a generate a report. So this is it. If you find it useful I can report another bug it detected.
On macOS, AirMCP calendar access can appear to succeed, but list_calendars returns an empty list ([]) even though the user has multiple calendars, including normal local and remote/subscribed calendars.
This appears to be a Swift/
Read the thread · 2026-04-24 · closed · external user · 0 comments
Most recent
The remaining reports are on the project's issue tracker.