Extensions — Google, GitHub, Discord, Telegram, Linear & custom MCP

Open Settings → Extensions

In VibeFuse, open Settings and pick Extensions under the Library group (same group as Skills, Notes, Widgets, and Marketplace). Status-bar MCP pills also jump here. This tab is Extensions — not Tools.

Built-in cards stay on the list even when disconnected. Each branded card shows a live pill (disabled / connecting / ready · tool count / error). Enable a server and VibeFuse starts it, lists its tools, and hands them to Jarvis and voice. Disconnect stops that process; servers also stop when the app quits.

How connections work

• Google Workspace and Google Drive share one OAuth client. Sign in once; both cards reuse the saved account.
• GitHub, GitHub Copilot, and GitHub Project Manager use a personal access token (classic or fine-grained).
• Discord is a local Java 17+ MCP (stdio JAR). Linear is Linear’s hosted MCP. Telegram is a Bot API gateway.
• Add MCP Connection appends a custom stdio card (default npx -y @modelcontextprotocol/server-filesystem).
• The same tool list is available in the Jarvis widget and through the voice dock. Catalog: Jarvis tools.

Google

Section title in the app: Google — “Gmail, Calendar, Docs, Sheets, and Drive — one Google account for the AI.” Two cards share the same OAuth client.

Google Workspace

Card title Google Workspace. Help line: Gmail, Drive, Calendar, Docs, Sheets, and more (signed-in email prints after the first login). Service chips: Google account, Gmail, Drive, Calendar, Docs, Sheets, Tasks, Slides, Meet, Contacts.

• Connect / Disconnect — starts or stops the Workspace MCP (~24 tools: mail, calendar, Drive, Docs, Sheets, Tasks, Slides, Meet, Contacts).
• Sign in with Google — first-time OAuth popup. After a saved login the button reads Use saved Google account.
• While OAuth or MCP start is in flight the sign-in button shows Waiting….
• If Drive or Gmail calls fail with “API has not been used…”, click Enable Workspace APIs for the shared Cloud project, then reconnect.

Google Drive

Card title Google Drive. Help line: Read Drive files via MCP · same OAuth as Workspace. Chips: Google account + Drive. This card is read-only Drive (~3 tools). Same Connect / Disconnect and Sign in with Google / Use saved Google account buttons as Workspace.

Ready status looks like Google Drive MCP connected · 3 tools ready for the AI. To list files, Jarvis prefers the built-in list_google_drive_files tool (see Jarvis tools).

GitHub + GitHub Copilot

Section title: GitHub — “Repos, issues, pull requests, and Copilot coding tools via a personal access token.” Two PAT cards.

GitHub

Card title GitHub. Chips: Repos, Issues, Pull requests, Users. Paste a PAT (classic or fine-grained with repo, read:org, and issues), then Connect. Disconnect stops the local GitHub MCP. The field label is GitHub personal access token (ghp_… or github_pat_…). Create a token from the card’s Create a token link.

Jarvis also has a built-in github tool that uses this PAT (preferred for “list my repos”). MCP tools (mcp_github_*) cover advanced repo, issue, and PR work after Connect.

GitHub Copilot

Card title GitHub Copilot. Help: Copilot coding agent, reviews, and Spaces via Copilot MCP. Chips: Copilot agent, Copilot Spaces, Issues. Field: GitHub / Copilot personal access token. Leave it blank to reuse the GitHub card token. Needs a Copilot-capable account. Connects to the hosted Copilot MCP. Connect / Disconnect as usual. Copilot MCP cannot list your user repos — use the GitHub card or the github tool for that.

GitHub Project Manager

Own section: GitHub Project Manager — “Local MCP for GitHub Projects v2, sprints, PRDs, and agent orchestration.” Card title matches. Local Node MCP from kunwarVivek/mcp-github-project-manager at C:\vibefuse\mcp-github-project-manager. Requires Node.js 20+.

• PAT field (this card or reuse the GitHub card). Token needs repo and project scopes.
• Default owner (user or org) and Default repository — default project target for the tools.
• Connect / Disconnect. First connect may clone, install, and build the package.
• Jarvis tools are mcp_github-project-manager_*. Prefer those over mcp_github_* for Projects v2 boards, sprints, milestones, and PRD/task planning.

Discord

Section: Discord — “Local Discord bot MCP (Java stdio) — messages, channels, roles, and moderation.” Card title Discord. Local MCP from SaseQ/discord-mcp. Needs Java 17+ on the machine (no Docker). Paste a Discord bot token, then Connect. Optional Default server ID so tools can omit guildId.

• Chips: Messages, Channels, Members, Roles, Voice, Events.
• Legacy HTTP bind is port 8091 (http://127.0.0.1:8091). The published JAR is stdio; VibeFuse runs it as a local Java MCP process.
• Missing Java shows: Java 17+ is required to run Discord MCP. Docker is not used.
• Jarvis calls mcp_discord_*. Omit guildId so the default server is used. If you pass it, use a digit string, never a JSON number.

Telegram — bot gateway to Jarvis (not MCP)

Section: Telegram — “Message Jarvis from Telegram. The bot forwards your texts to the desktop agent and sends the reply back.” Card title Telegram. Help: Bot API gateway. This is not an MCP server. After Connect, allowlisted senders talk to the same Jarvis that lives on the canvas.

• Create a bot with @BotFather, paste the Telegram bot token, then Connect.
• Message the bot /start. Add your numeric user ID under Allowed Telegram user IDs.
• Buttons: Connect / Disconnect, Save allowlist, Allow last sender (after a message arrives).
• Chips: Messages, Desktop agent, Allowlist.
• Screenshot and video replies use telegram_screenshot and telegram_video — not a Terminal screen grab. See Jarvis tools.

Linear — hosted MCP

Section: Linear — “Issues, projects, and comments via Linear’s hosted MCP.” Card title Linear. Connects to Linear’s official hosted MCP at https://mcp.linear.app/mcp with a Bearer token. OAuth developer token preferred; API key is the optional fallback. No OAuth callback is required.

• Fields: OAuth developer token (lin_oauth_…) and API key (optional fallback) (lin_api_…).
• Chips: Issues, Projects, Teams, Documents.
• Connect / Disconnect. Jarvis tools are mcp_linear_* (issues, projects, cycles, comments, teams).
• The Linear canvas widget uses the same token; queries stay under Linear’s GraphQL complexity cap so the widget loads instead of failing.

Custom — Add MCP Connection

Section: Custom — “Run any MCP server by command. Enable, edit, or remove each connection.” Footer button: Add MCP Connection. New cards default to command npx and arguments -y @modelcontextprotocol/server-filesystem.

Any stdio MCP that speaks the protocol works: filesystem, databases, your own server. Tools appear to Jarvis as mcp_<name>_* after the process is ready.

Not on Extensions — Local Servers

These are not Extensions cards. Start them from Settings → Local Servers:

• HyperFrames Studio — HTML-to-video on http://127.0.0.1:4567, workspace C:\vibefuse\hyperframes.
• Skill Seekers — docs-to-skill presets. Jarvis tools are mcp_skill-seekers_* after Local Servers is connected. When someone asks if a skill exists, Jarvis should execute_skill with skillId=skill-seekers-lookup first. Guide: Write a skill.
• Crawl4AI + SearXNG — local scrape/search used by web_search, firecrawl_search, firecrawl_scrape, and firecrawl_map.
• Piper TTS and Whisper STT — also Local Servers, not Extensions.

Jarvis and voice use the same connections

The left-rail / catalog widget is Jarvis (com.vibefuse.custom-agent). It shares the voice assistant’s tool list: canvas tools plus every connected Extensions MCP and Telegram gateway. Full catalog: Jarvis tools. All 14 Settings tabs: Settings.

Troubleshooting

Related