MCP Apps let Dokki Copilot or an Agent use an external service through an account you authorize. Use this guide to connect, use, review, and disconnect those accounts. For the comparison between AI Clients, Workspace MCP Connectors, MCP Apps, Chat Channels, and Agent MCP, start with Connect.
What an MCP App is
An MCP App is an outbound connection from Dokki to an external service such as GitHub, Slack, Gmail, a calendar, a drive, an issue tracker, or another supported toolkit.
The connection belongs to the Dokki user who authorizes the external account.
Dokki may use OAuth, an API Key form, or another provider-specific credential flow.
The external provider's own roles and permissions continue to apply.
Other workspace members do not automatically inherit the connected account.
A dedicated external MCP server configured for one installed Agent belongs under that Agent's MCP tab, not MCP Apps.
Connect an MCP App
Open Workspace → Extensions → Connect → MCP Apps.
Search for the service by name.
Open the service and choose Connect.
Complete the provider's OAuth page or credential form.
Confirm that the intended external account and Organization are selected.
Return to Dokki and wait until the connection shows active.
Start with a read-only task and verify which account answered.
If a provider is temporarily unavailable or authorization remains pending, retry the existing flow instead of creating duplicate connections.
Connection ownership and access
Two independent permission systems must allow every task:
Dokki permissions decide which workspace context, resources, and Agent instructions may be used.
External-provider permissions decide which repositories, channels, mailboxes, calendars, drives, projects, or actions the connected account may use.
Access on one side never expands the other. A connected GitHub account cannot reveal a private Dokki document, and access to a Dokki document cannot grant repository access.
Use an MCP App from Copilot
Ask for a specific service, target, and action. When the interface supports app mentions, select the MCP App explicitly so the current turn loads only the relevant external tools.
“Read the open issues in the connected repository and summarize them in this document.”
“Draft an email from this project brief, but do not send it.”
“List tomorrow's calendar events and add preparation tasks to this table.”
Before a mutation, confirm the external account, repository, channel, mailbox, calendar, drive, or project. A drafted request is not proof that the provider accepted the change; read the result back.
Use an MCP App from an Agent
Open the Agent control panel and review its purpose and instructions.
Limit the Agent's Dokki workspace access.
Confirm which user's MCP App connection the Agent will act through.
Review schedules, unattended triggers, and delivery destinations.
Run a manual read-only task first.
Inspect both the Agent run and the external provider result before allowing recurring mutations.
Agent instructions cannot override Dokki or provider authorization. Removing the workspace, account connection, or Agent permission can stop later runs.
Import through a connected app
Some providers also support Dokki's guided import and one-way sync flow.
Open the destination folder and choose Import.
Select or manage the provider connection.
Choose individual items, supported URLs or ids, or explicitly confirm a broad import.
Choose one-time import or one-way sync when available.
Review queued, running, completed, and failed items.
Open completed Dokki resources from the result links.
Disconnecting the app stops future imports or refreshes. It does not delete Dokki resources already created.
Confirm consequential actions
Dokki may require confirmation before sending a message, changing external data, publishing content, or performing another consequential action.
Before confirming, identify the acting user or Agent, Dokki source context, selected MCP App and external account, external target, requested mutation, and verification method.
Review active connections
Provider and external account identity.
Connection status and last successful use.
Duplicate connections pointing to different accounts.
Which Copilot or Agent workflows still depend on the connection.
Whether the account still belongs to the correct person or team.
Disconnect or reconnect
Disconnect when the account is wrong, access is no longer required, credentials may be exposed, an Agent or automation is retired, or the provider requests reauthorization.
Reconnect when the provider reports expired or invalid authorization. Verify the external account again after reconnecting because an existing browser session can select a different account.
Disconnecting stops future Dokki use of the connection. It does not undo messages, issues, files, events, imports, or other changes already created.
Troubleshooting
App is not listed — search by provider name or toolkit slug; it may be unsupported or temporarily unavailable.
Authorization page does not open — restart from Connect → MCP Apps and allow the provider sign-in window.
Connection stays pending — complete the provider page, return to Dokki, and refresh status without creating duplicates.
Wrong external account — disconnect, sign into the intended provider account, and reconnect.
Copilot cannot see the app — confirm it is active, select or mention it explicitly, and start a new turn so tools refresh.
Agent cannot use the app — check Agent configuration, workspace access, acting-user ownership, schedule identity, and connection status.
Read works but write fails — check provider write permission, protected targets, and required confirmation.
Dokki resource is unavailable — fix Dokki workspace or resource access; the MCP App cannot bypass it.
Import stopped updating — review both the provider connection and the import or sync status.
Safe connection practices
Connect the smallest external account that can complete the task.
Prefer explicit app selection over loading every available external tool.
Keep credentials inside the hosted authorization flow or approved secure form.
Never paste API keys or bearer tokens into documents, chats, Agent instructions, or memory.
Review unattended Agent schedules after any connection change.
Disconnect stale accounts and confirm future calls fail.
Treat important external writes as complete only after provider readback.