Pencil for Omi
Connect your personal Pencil account from Omi to look up work and edit task details.
Pencil uses a public Omi app for discovery and setup, plus a personal MCP connection for each account. The store listing must be released before public installation is available. Installing the public setup app alone does not authorize your Pencil account.
Once connected, ask about your tasks and projects in Omi main chat or through a supported wearable voice flow. Omi handles speech; Pencil supplies authorized work data and tool results. Each user signs in separately and chooses one workspace. The public setup tool returns instructions only and cannot read Pencil data.
Connect
- Open Settings → Integrations → Add integration → Omi in Pencil with your workspace selected. Copy the MCP server URL.
- In Omi’s Apps screen, add a remote MCP server using that URL and name the app Pencil. The exact add-server control depends on your Omi version.
- Follow Omi’s browser sign-in. Choose the workspace and the Pencil for Omi app tool set. Permissions start with no access. Allow Tasks, Projects, and Members & teams read access; leave unrelated groups at no access.
- For task edits, allow Tasks → Read + write if Omi requests
mcp:write. A read-only OAuth request cannot grant writes. - Return to Omi. Ask “Check my Pencil connection, then show my tasks.” Check the selected workspace and results. Only then try the same request from your wearable.
Workspace Voice must be enabled for data reads. Task edits also require Voice write actions and a current editor role. The connection-check tool reports these switches without reading your tasks.
The URL is the existing hosted Pencil MCP server, normally https://app.pencil.ink/api/mcp. Self-hosted instances use their own canonical MCP URL, displayed in Settings. No Pencil Gateway or pasted API key is required.
Supported requests
| Request | Access |
|---|---|
| Check connection, identify the signed-in person/workspace | Any authorized Omi profile |
| Find tasks, read task context, list a project's tasks | Tasks: read |
| Find projects and read project summaries | Projects: read |
| Resolve a person's name for assigned-work queries | Members & teams: read |
| Edit a task title, priority or due date | Tasks: write plus mcp:write |
The tool set exposes pencil_connection, list_tasks, list_assignee_tasks, get_task_context, list_projects, get_project, list_project_tasks, list_members, resolve_member, and a restricted update_task. Individual permissions may hide tools. Omi must read the task first and supply its updatedAt as expectedUpdatedAt for edits. A concurrent change returns a conflict; read again and reassess the requested edit.
Examples: “Ask Pencil what is assigned to me,” “Show tasks in Mobile,” and “Make task T-42 high priority.” Specify an exact date and timezone when setting a due date. Ambiguous references need clarification.
This version does not create tasks or ideas, change task status, assign work, approve requests, run agents, deploy code, or import ambient conversations. The separate Android qualification plan covers a broader future voice pilot.
Access and disconnect
Your OAuth grant selects one workspace and retains its existing Pencil permissions. The Omi tool set is an additional restriction. A client calling itself Omi gains no extra access. Existing clients retain their normal tools unless you explicitly select this tool set.
See your own authorized connections in Settings → Integrations → Omi. Disconnect revokes the grant and its access/refresh tokens. Administrators retain the existing grant controls under Developer → API Keys. Remove your personal MCP app in Omi separately. Removing the public setup app alone does not revoke that separate MCP grant. Revoking Pencil access does not delete information already retained by Omi.
Reauthorization can narrow existing restrictions. To expand access or switch back to the standard tool set, disconnect and authorize a fresh grant. Access also stops when the grant owner loses workspace membership.
Troubleshooting and voice qualification
An authorized connection or an on-screen reply does not prove pendant capture or headphone playback. Test the actual wearable, phone, app version and headphones while unlocked and locked. Omi may summarize responses; verify task edits in Pencil.
If requests begin failing after a previously successful session, reconnect through Omi. Do not bypass token expiry or rotation. Omi's rotating-token persistence fix remains under upstream review; a deployed fix and repeated refresh/reload checks are still required before claiming reliable long-lived wearable use.
If no data tools appear, check your grant's Tasks, Projects and Members permissions. Older Omi connections use their existing tool sets until reauthorized. A permission error or timeout is not a successful edit: read the task to determine its current state before another attempt.
This integration sends deliberate tool inputs to Pencil. Omi continues to process and retain its own conversations according to its settings. Pencil connection activity timestamps describe OAuth/MCP access, not audio success.