vifo

vifo is an MCP server. Any agent that speaks MCP — Claude, ChatGPT, Claude Code, Cursor and others — can connect to it with one address. Until vifo appears in the Claude and ChatGPT directories, you add it yourself as a custom connector. It takes about two minutes; this page walks through every click.

What you need

• The server address: https://vifo.app/mcp — that is the only thing you type.
• A vifo account — or not even that. When the agent connects, a vifo page opens and asks you to sign in with a one-time email code, the same sign-in as the website. Any email works; first sign-in creates the account.
• Nothing else. Authorization is standard OAuth and registers automatically; leave any client ID / client secret fields empty.
• On the agent side, custom connectors are usually a paid-plan feature — Claude Pro / Max / Team / Enterprise, ChatGPT Plus and up with Developer mode, Gemini with Google AI Pro / Ultra, Perplexity Pro / Max. Grok and WorkBuddy take them on the free tier. Availability can differ by region; each section below says what it needs.

Claude (web, desktop and mobile)

Connectors added on claude.ai follow your account, so one setup covers the Claude desktop and mobile apps too.

1 · Open the Connectors settings

Click your initials at the bottom-left → Settings → Connectors (direct link: claude.ai/settings/connectors). Scroll past the directory and click Add custom connector.

2 · Fill in the two fields

Name: vifo (any name you like — it is what the tool menu shows). Remote MCP server URL: https://vifo.app/mcp. Leave Advanced settings alone and click Add.

3 · Connect and sign in to vifo

vifo now appears under Your connectors. Click Connect. A vifo page opens: enter your email, type the code we send you, then press Allow the connection. You are sent back to Claude and the connector shows as connected.

4 · Use it in a chat

In a new chat, open the + / Tools menu under the message box and make sure vifo is switched on. Then just talk: “Start a new trip — Kyoto, five days.” and send photos. Claude will ask before it writes anything the first time.

Claude Code

One command in the terminal, then authenticate once:

claude mcp add --transport http vifo https://vifo.app/mcp
claude          # inside the session, run /mcp and pick vifo → Authenticate

The browser opens the same vifo sign-in page; after Allow the connection the tools are available in every project.

ChatGPT

ChatGPT calls custom MCP servers connectors and only shows the option once Developer mode is on. It is available on Plus, Pro, Business, Enterprise and Edu plans; on Business / Enterprise a workspace admin may have to enable it.

1 · Turn on Developer mode

Profile menu → Settings → Apps (called Connectors in older versions) → Advanced settings → switch on Developer mode.

2 · Create the connector

Back on the Apps page, click Create. Fill in: Name vifo; a short Description (anything); MCP server URL https://vifo.app/mcp; Authentication → OAuth (leave client ID and secret empty); tick I trust this application; click Scan Tools if the dialog offers it, then Create.

3 · Sign in to vifo

ChatGPT immediately opens the vifo sign-in page (or shows a Connect button — click it). Enter your email and the code, press Allow the connection, and you are returned to ChatGPT with vifo listed under your connected apps.

4 · Use it in a chat

In the message box click + → More → vifo to attach it to the conversation (in Developer mode ChatGPT will not pick it up on its own). Then describe the trip and send photos. ChatGPT asks for confirmation before write actions.

Photos in ChatGPT: vifo receives the bytes the agent uploads through its tools, not the files you drop into the chat. If ChatGPT says it cannot upload a file, use Claude, Claude Code or a local agent for the photo step — ChatGPT still works for notes and organising.

Gemini (web and mobile, via Spark)

The Gemini app takes custom MCP servers through Gemini Spark. You need a Google AI Pro or Ultra subscription, a personal Google Account (work/school accounts are excluded for now), be 18+, and have Keep Activity switched on. You add the server on the web only; once added it works in the Gemini mobile app too.

1. Open gemini.google.com → bottom-left Settings & help → Connected Apps (if you do not see it, go through Personal Intelligence first).
2. Under Custom apps for Spark, paste https://vifo.app/mcp into Add a custom app link (or click Add a custom app) and press Next. Leave Advanced features closed — vifo registers itself.
3. Follow the prompts: the vifo sign-in page opens; enter the email code and press Allow the connection.
4. In a Spark chat type @ and pick vifo so Gemini uses it for that prompt. To revoke later: Connected Apps → the app → Unlink, or your Google Account’s Linked apps page.

Grok (web, iOS and Android)

Grok calls this Bring Your Own MCP; it is available on the free tier and on all three platforms.

1. Web: open grok.com/connectors. Phone: Settings → Connectors.
2. Click New Connector → Custom, name it vifo, paste https://vifo.app/mcp, Add.
3. Grok sends you to the vifo sign-in page; email code, Allow the connection. Back in Grok the connector shows as connected and is usable in every chat.

Perplexity (web, desktop and mobile)

Custom connectors are on Pro, Max and Enterprise. One connector serves every model Perplexity routes to.

1. Settings → Connectors → + Custom connector → choose Remote.
2. Name vifo, Server URL https://vifo.app/mcp, authentication OAuth, transport Streamable HTTP; acknowledge the risk note and Add.
3. Click the new card to authorize — vifo sign-in, email code, Allow the connection. In a thread, enable the connector from the sources / tools menu.

Tencent WorkBuddy (Windows and macOS)

WorkBuddy’s connectors are MCP underneath. Remote servers with standard MCP OAuth are supported, with automatic token refresh. (The phone app is a remote control for the desktop session, so the server is configured on the computer.)

1. Settings → MCP → Add MCP Server.
2. Type HTTP (remote), name vifo, URL https://vifo.app/mcp; leave headers and tokens empty and save.
3. WorkBuddy opens the vifo authorization in your browser — email code, Allow the connection. The tools appear in the chat; ask “what tools do you have?” to check.

If your build has no dialog for it, add this to ~/.workbuddy/mcp.json and restart:

{
  "mcpServers": {
    "vifo": { "type": "http", "url": "https://vifo.app/mcp" }
  }
}

Other agents

• Mistral Le Chat / Vibe: Work → Connectors → + Add Connector → Custom MCP Connector → paste the URL; auth is auto-detected as OAuth 2.1. Administrator-only (on personal plans that is you).
• Codex: codex mcp add vifo --url https://vifo.app/mcp then codex mcp login vifo.
• Cursor / Windsurf / Kimi Code / Qwen Code / any MCP client with OAuth: add a remote (HTTP) MCP server at https://vifo.app/mcp and complete the browser sign-in when prompted.
• Not yet possible: the consumer Microsoft Copilot, Doubao, Kimi and Qwen chat apps do not accept custom MCP servers today.
• Headless agents that cannot open a browser (OpenClaw, scripts, servers): create a key on the Connect page and send it as Authorization: Bearer vf_…. Keys have fixed scopes; revoke and re-issue to change them.

Troubleshooting

• The code never arrives — check spam, and wait a minute before asking for another: a single address gets a limited number of codes per hour. Still nothing? Write to hello@vifo.app.
• No “Add custom connector” / “Create” button — in Claude this needs a paid plan (and, on Team/Enterprise, an admin who allows custom connectors); in ChatGPT it needs Developer mode on; in Gemini it needs Google AI Pro/Ultra on a personal account, added from the web.
• Connector shows “disconnected” later — the authorization was revoked or expired. Click Connect / Reconnect and sign in again; nothing in your notebook is affected.
• To revoke access — remove the connector in the agent, and/or open the Connect page on vifo, where every connected app and key is listed with a revoke button.
• What the agent can see — only your own trips, photos and notes, within the scopes shown on the authorization page. Details in the Privacy Policy.