DGC v0.51.0 is out
Navigate
Install DGC
DGC v0.51.0Edit on GitHub ↗
Features/Plugins, apps and MCP

install a plugin, connect an app, and what a connector brokers

Plugins, apps and MCP

#

A plugin is a package you install into DGC: skills, an MCP server, or both. An app is a third-party service one of those servers reaches — GitHub, Notion, Linear, Sentry, Supabase, Stripe. MCP is the wire underneath: every tool a plugin adds arrives as mcp__<server>__<tool>, and MCP servers covers the protocol, the remote bridge and the execution boundaries.

Nothing is installed until you install it, and nothing reaches a service until you sign in to it. Two first-party packages — default templates and plugin management — ship inside DGC, so installing those fetches nothing.

Where they live

#

The editor owns the browsing surface. Settings ▸ Plugins has three lanes:

  • Plugins — what is installed, with its state: Installed, Setup required, or Connected.
  • Apps — the individual services those packages reach, each naming the plugin behind it.
  • Mods — your own mods, as /mods lists them.

Settings ▸ MCP servers holds the servers themselves, the same catalog as /mcp.

Cloudflare is one of them: its own hosted analytics server with its own browser sign-in, granted read access only, so a Pip can read a site's traffic with no approval.

Browse directory opens the curated catalog. Every entry names its licence and, separately, what DGC actually verified — which is often less than "it works": a package whose structure was checked but whose authenticated tools were never exercised says exactly that. Manage marketplaces adds another catalog, and the filter separates DGC curated from Personal and from anything you added.

Opening a package to read what it contains works while DGC is working, and so do installing it, removing it, and adding or refreshing a marketplace. A plugin changes what DGC can do — tools and skills, which a running turn picks up at its next model request — never what it is allowed to do. Stop ends the turn, not an install you started beside it.

The terminal does the same work without a browser:

dgc plugin list
dgc plugin search notion
dgc plugin install notion
dgc plugin sign-in notion
dgc plugin installed
dgc plugin uninstall notion
dgc plugin marketplace list
dgc plugin marketplace add SOURCE

Installing one

#

A plugin's files are copied into ~/.dgc/plugins at install. Its skills land in DGC's discovery root and show up in /skills as soon as installation finishes. They are not part of the DGC source tree and stay under their own upstream licence, which is why an entry whose terms need your agreement asks for it before anything is copied — --accept-license ID in the terminal.

Nothing in a package runs on install, and a file arrives without its executable bit. A package's hooks, agents, commands, language servers and output styles are not imported at all, and the install review names each one it is ignoring. A script that survives runs later only through the normal approval you give any command. The package is bounded: at most 40 skills, 64 KiB per SKILL.md, and 8 MiB per file with 64 MiB and 4,000 files across the whole package.

DGC reads the .claude-plugin/plugin.json and .codex-plugin/plugin.json layouts, so a package written for Claude Code or Codex installs here — but only the skills and the MCP servers inside it come across.

Some catalog entries are withdrawn rather than offered, and you will not see them in the directory at all. Figma's remote server requires a client it has approved and DGC is not one of them. An offer DGC cannot honour is worse than no offer, so it is taken out rather than left to fail at the sign-in. One you already installed, or one that arrives from a marketplace you added yourself, does show — with the reason on its card.

Installing is not connecting. Connect starts whatever sign-in the plugin declares — a browser handoff, or the key it takes. A plugin can sit installed for as long as you like with its server disconnected, and the model is told exactly that rather than left to infer it: installed, MCP configured but not connected in this session.

App connectors

#

Five entries are connectors rather than single services: Composio, Zapier, Arcade and Make, plus n8n for workflows on your own instance. You authorize your accounts inside that service, and its one MCP server then reaches all of them. Composio's card says where: connect and manage your apps in Composio For You → Connect Apps, then come back and ask DGC to use them. App permissions, account selection and revocation stay there. Uninstalling the connector here revokes nothing upstream.

A pasted connector token is kept in the editor's secret storage under DGC's own MCP bearer variable and bound to the exact URL it was given for, never written to the config file. A URL carrying credentials, a query or a fragment is refused outright.

Two consequences, and DGC now states both rather than leaving you to discover them:

  • The work happens in their cloud. A connector holds the app's credentials and runs the app request on its own servers — including when your model is running locally on this machine. Their terms govern that part, not DGC's.
  • A connected connector may reach a service that has no plugin of its own here. The roster the model reads used to report per-plugin connectivity and nothing else. It read Figma: MCP not connected as Figma is unreachable — with a connected Composio one line below holding the very Figma account it needed — wrote that premise into its own sub-agent's brief, and offered to work from screenshots sent by hand. A connected connector now says that it brokers the accounts you authorized in its own service, and the model is told to search it with mcp_search before telling you a service needs credentials, or a screenshot it cannot obtain. A connector whose server is down advertises none of this.

A rate-limited call from one of these servers now says it was rate-limited. It used to arrive as the same opaque payload as a missing credential, which is the other half of why a busy service read as a locked one.

Asana, Docusign and Zoom: your own app

#

Asana's, Docusign's and Zoom's MCP servers admit only apps registered with them; Asana and Docusign also need a secret, which an open-source app can't ship. So you create an app for DGC in your own account, as the vendors document for coding tools. Settings → Plugins → Apps → Connect shows each step:

  • Asana: in My apps, create an app named DGC of type MCP app; under OAuth add the redirect URL DGC shows (http://localhost:3334/oauth/callback, with a Copy button); under Manage distribution choose your workspace; then paste the client ID and client secret.
  • Docusign: in Apps and Keys, add an app and integration key named DGC, choose User Application: Yes, add a secret key, and add the redirect URI DGC shows (http://localhost:3335/oauth/callback); then paste the integration key and secret key. A developer (demo) account works at once. A production account accepts the app only after Docusign's Go-Live review and your Docusign admin's approval for MCP.
  • Zoom: in the Zoom App Marketplace, build a General app named DGC, User-managed; under App Credentials turn on Use Public Client OAuth; add the address DGC shows as the OAuth redirect URL and to the OAuth allow list (http://127.0.0.1:3336/oauth/callback: Zoom asks for 127.0.0.1 here, not localhost); add the scopes DGC lists (meetings, recordings, search and Docs); then paste the development public client ID. There is no secret. DGC asks Zoom for no scopes of its own: the ones you added to the app decide what it can do. You need to be the Zoom account's owner or an admin, or have the Zoom for developers role, and the app works for members of your own Zoom account.

The secret is kept in the editor's secret storage and handed to DGC in an owner-only file when it connects; the sign-in that follows is kept in your system keychain like any other. Reopening the setup keeps the saved secret if you leave it blank.

Google Workspace: Gmail, Calendar, Drive, Docs and Slides

#

It appears in Settings → Plugins once Google approves DGC's Google app. Until then only the accounts DGC has added can sign in, and they install it by name: dgc plugin install google-workspace.

Google runs an MCP server for each of its apps (a Developer Preview), and DGC signs in to them with DGC's own Google app: there is nothing to set up at Google. Settings → Plugins → Google Workspace → Install lets you choose the apps; you then sign in with Google once, for all of them, and the sign-in is kept in your system keychain. In a terminal: dgc plugin install google-workspace --apps gmail,calendar (all five without --apps).

Each app asks Google for these permissions, and nothing else:

  • Gmail: read your email; write drafts and send email. Google's Gmail tools make drafts; none of them sends.
  • Google Calendar: see your calendars, when you're free, and your events. It can't create, change or answer events.
  • Google Drive: read all your Drive files; create files, and change only the ones DGC made or you opened with it.
  • Google Docs and Google Slides: the Drive permissions, and read and edit your documents or presentations.

A Google tool that needs more than this (labelling or deleting mail, say) answers that Google didn't allow it, naming the permission; DGC never widens the sign-in by itself. Choosing another app later asks Google once more, for that app's permissions.

While Google reviews DGC's app, only accounts DGC has added as testers can sign in, and Google signs them out every 7 days. DGC then says so in those words: "Google signs you out every 7 days while DGC's Google app is in testing: sign in again". Choose Connect on the plugin's page to sign in again.

The app's id is public and ships with DGC. Google also wants the app's secret when you sign in, and that is not in DGC's source: DGC fetches it from https://vibedgc.com/oauth/google-client.json while you sign in, uses it only if it is for the same app, and keeps it with your sign-in in the keychain, where refreshing finds it. It never goes into config.json, a log, an event or anything the model sees. Uninstalling the plugin asks Google to revoke DGC's access and deletes the sign-in.

Microsoft: Outlook mail, Outlook calendar and OneDrive

#

Microsoft has no MCP server that a personal account can use, so DGC has its own: it runs inside DGC and calls Microsoft Graph, Microsoft's official API. Nothing is downloaded, and no community server is involved. Settings → Plugins → Microsoft Outlook and OneDrive → Install lets you choose the apps and your kind of account (Personal for Outlook.com, Hotmail or Live; Work or school for a Microsoft 365 account); you then sign in with Microsoft once, for all of them, and the sign-in is kept in your system keychain. In a terminal: dgc plugin install microsoft --apps mail,calendar --account personal (all three apps and a personal account without the options). dgc plugin sign-in microsoft --account work switches to the other kind of account.

Each app asks Microsoft for these permissions, and nothing else (every sign-in also asks to stay signed in and to see your name and email address):

  • Outlook Mail: read and organize your email (search, read, draft, move); send email as you.
  • Outlook Calendar: read and change your calendar (list, create, change, answer and delete events).
  • OneDrive: read and change your OneDrive files (search, read text, download into the project, upload new files, replace one you name).

Reading runs like any tool. Sending email, creating, changing, moving or deleting anything is a change, approved like DGC's other changes; a Pip asks before each one. A tool answers in plain words when Microsoft refuses something, throttles DGC (it waits as long as Microsoft asks, a few times) or a list has more pages (next_page).

Signing in. DGC opens Microsoft's sign-in page in your browser and listens on http://localhost for it to come back. Where this computer has no browser (a session over SSH, a Linux machine with no desktop), DGC shows a code instead: open microsoft.com/devicelogin on any device and enter it. dgc plugin sign-in microsoft --code asks for a code even where a browser could open. A personal account signs in at Microsoft's consumers sign-in server and a work or school account at organizations, and each refreshes where it signed in.

DGC's Microsoft app isn't publisher-verified yet, so Microsoft's sign-in page marks it unverified. A personal account can still approve it there. In a company, people can't approve it themselves: an admin approves DGC once, for everyone. When that is what stops you, DGC says "Your organization needs an admin to approve DGC for Microsoft 365 first" and gives the link to send them. When Microsoft ends a sign-in (you removed DGC's access, or it went unused for months), DGC says so in plain words; choose Connect to sign in again. Microsoft has no way for an app to sign itself out, so uninstalling deletes the sign-in from this computer and tells you where to remove DGC's access too (account.live.com for a personal account, myapps.microsoft.com for a work one).

The same server also runs on its own for any MCP client on this computer, with the sign-in the plugin keeps: python -m dgc.microsoft_graph mail calendar onedrive. It can't sign in by itself.

Uninstalling

#

Uninstall removes the package, its skills, and the servers DGC created for it. A server you edited by hand, or one another plugin also uses, is kept and named in the result — DGC created neither and will not delete either. Plugins and connectors share one flat namespace, so a name belongs to exactly one of them; two things can no longer both claim it and leave skill folders behind that nothing owns and nothing can remove.

What a plugin cannot do

#

A plugin's skills are instructions. They grant nothing: no permission, no account, no tool. Its tools are ordinary MCP tools, and every call passes through permission requests, lifecycle hooks, cancellation, redaction and output bounds like any other; plan mode does not execute them. Reference text a server returns cannot activate a skill or hand itself a tool.

What does deserve care is the server process. Treat a configured server command as a trusted executable: it starts unsandboxed in your workspace, and DGC cannot mediate that process's own filesystem or network activity through tool permissions. See MCP servers.

Documentation