Future integrations — backlog

A scratch list of third-party app/service integrations eVi could grow. Nothing here is committed; the point is to capture ideas as they come up so we don't lose them. When we pick one up, it gets its own phase entry in CHANGELOG.md and the project memory.

Each entry has a one-line sketch of the integration shape: which eVi surfaces would expand (tool category + maybe a CLI subcommand) and what sort of dependency it'd pull in.

Deferred (asked-and-pushed-out)

These were mentioned in the 2026-05-27 planning session but the user chose to defer in favour of calendar reading first.

AppUse caseSketch
Home AssistantControl lights / climate / locks, query sensorsREST API + long-lived token. Tools: homeassistant_state(entity), homeassistant_service(domain, service, data). Existing homeassistant Python client, or just httpx direct.
NotionRead pages + databases, append notesOfficial notion-client. OAuth or integration token. Tools: notion_search(query), notion_get_page(id), notion_append(parent, content).
SpotifyNow-playing, search, queue + playback controlspotipy + OAuth (refresh-token flow). Tools: spotify_now_playing(), spotify_search(q, type), spotify_play(uri), spotify_queue(uri).
PlexLibrary search, what's playing, historyplexapi. Server URL + token (Plex.tv). Tools: plex_search(q), plex_recently_added(days), plex_playback_state().
SlackRead DMs/channels, search history, send messagesslack_sdk bot token or user token. Tools: slack_search(q), slack_read_channel(id, n), slack_send(channel, text). Permission-gated send.
VS CodeOpen files, see what user is editing, run tasksTwo paths: (a) eVi MCP server consumed by Cline/Continue, (b) VS Code extension that posts cursor + active-file context to eVi. Probably (a).
JetBrainsSame as VS CodeJetBrains has Beta MCP support; (a) above covers it.

Other candidates (not yet asked, but reasonable)

These came up implicitly while listing the above. Capture them while they're fresh.

AppUse caseSketch
DiscordDMs + server messagesdiscord.py (bot user) + opt-in audit log. Read-only tools first; send under permission.
TelegramDMs + botspython-telegram-bot. Bot token only — user-account TG is more invasive.
GitHubIssues, PRs, code search, releasesPyGithub or raw REST + PAT. Already covered partially by MCP github server — could ship a native tool too.
GitLabSame as GitHubpython-gitlab.
LinearIssue trackingREST + API key. Tools: linear_search, linear_issue(id), linear_create_issue(...).
Jira / ConfluenceIssue tracking + wikiatlassian-python-api. Beware: enterprise auth flows.
TrelloLightweight cardsREST + API key. Niche.
AsanaTasksOfficial Python client. Same shape as Linear.
Email — IMAP/SMTPRead + send without provider-specific OAuthimaplib + smtplib stdlib. Generic, beats per-provider integrations for users on Fastmail/Posteo/etc. (We deliberately deferred Phase 2 Gmail/M365; IMAP is the user-friendly fallback.)
RSS / AtomNews feeds, blog updatesfeedparser. Read-only. Pairs well with dream/memory.
YouTube transcriptsSummarize videosyoutube-transcript-api. No API key, just URL → transcript.
RedditRead subs, comment threadspraw + OAuth (read-only is easier).
Mastodon / BlueskySame shape as TwitterMastodon: Mastodon.py. Bluesky: atproto.
Twitter / XAPI now restrictiveSkip unless user has paid API tier.
Hacker NewsRead top stories, commentsFree API; no auth. Pairs well with morning briefings.
AnkiSpaced repetition for memorisationanki-connect (HTTP plugin) or raw .anki2 files.
ObsidianAlready shipped via sync. Possibly add a live-vault tool for in-conversation lookups.
LogseqSame shape as Obsidian, different file layout.
iMessage / SMSRead recent messagesmacOS only: ~/Library/Messages/chat.db. SQLite read tool already exists — would be a thin wrapper.
Apple RemindersRead + create tasksmacOS only: AppleScript bridge via osascript.
Things 3TasksmacOS+iOS. URL scheme for create; SQLite read for ~/Library/Containers/com.culturedcode.ThingsMac/....
TodoistCross-platform tasksOfficial Python SDK; REST + API token.
TickTickCross-platform tasksUnofficial REST clients.
OmniFocusTasksmacOS AppleScript or URL scheme.
PocketRead-it-laterPocket REST API. Mostly defunct since Mozilla's pivot.
Instapaper / ReadwiseHighlights exportReadwise has a clean REST API. Useful for dream/memory feedback.
DraftsmacOS quick captureURL scheme + iCloud Drive.
OneDrive / Dropbox / Google DriveFile accessEach has an OAuth flow; would beat IMAP-like generic-WebDAV approach.
WebDAVGeneric file accesswebdavclient3. Covers Nextcloud, ownCloud, kDrive.
Slack Tracker (Sherlock-style)Local stand-up summariesReads from Slack tool above + git tool. Composes a daily report. Could be a recipe instead of a tool.
Postgres / MySQL / SQLite via DB URLGeneric read-only DB queries beyond the current sqlite toolsqlalchemy or per-DB drivers; broaden the existing SQLite tool.
RedisCache/inspectredis-py. Mostly dev-ops use.
AWS / GCP / Azure CLIsCloud opsWrappers around aws/gcloud/az. Permission-gated.
KubernetesCluster opskubernetes client. Read-only by default; tools like kubectl_get_pods etc.
DockerLocal containersDocker SDK or shell. List, logs, exec.
TailscaleStatus, peer listtailscale CLI subprocess.
WireguardStatuswg show parse.
CalibreE-book librarycalibre CLI or calibredb script.
Apple NotesReadmacOS only — AppleScript bridge.
Goodreads / StoryGraphReading listStoryGraph has no API; Goodreads' API is sunset. Skip.
LetterboxdWatched filmsNo API. Skip until they ship one.
Last.fmMusic historyREST + API key. Pairs with Spotify.
StravaWorkoutsOAuth + REST.
Apple Health / Google Fit / Garmin ConnectBody dataApple Health export → XML (via Shortcuts); Garmin via garminconnect.
WeatherConditions / forecastopen-meteo (no key), or NWS, or OpenWeatherMap. Tool: weather(location, when).
News headlinesNewsAPI / GDELTAPI key needed for most. RSS is the no-key fallback.
WikipediaArticle excerptswikipedia-api. No key. Useful retrieval target.
arXiv / Semantic ScholarPaper search + abstractsBoth have free REST APIs.
GitHub Copilot / Cursor / CodyAI-to-AI bridgeIf you have a paid Copilot/Cursor seat, the bridge is mostly novelty — you already have eVi.
Vault / 1Password CLI / Bitwarden CLISecret retrievalop / bw CLIs. Permission-gated heavily. Useful for hooks that need credentials.
Browser historyWhat did I look at yesterdaySQLite reads against Chromium / Firefox profiles. Privacy considerations.
Browser bookmarksSearch saved linksSame shape as history.
Shell command paletteRecent commands + frequency~/.zsh_history / ~/.bash_history parse.
fzf / ripgrep / fdBetter local search than find_in_projectSubprocess wrappers; faster for non-semantic queries.

Bridges (eVi as MCP server)

Rather than building N integrations one at a time, we could publish an eVi MCP server that exposes eVi's tools (memory, index, calendar, etc.) so that other agents — Claude Desktop, Cline, Continue, Cursor — can consume them. This flips the integration story: you don't bridge into eVi from each editor, the editor's agent reaches out to eVi's tool surface.

Tracked separately as a possible Phase 31-ish item.

How to add to this list

Just edit this file and open a PR (or paste in chat — eVi will edit it). The table is plain markdown; new rows go anywhere.

Edit on GitHub ↗