Connect apps and local tools on desktop
Choose remote connectors or local MCP extensions and verify access.
Use a service account you control and a harmless test item. A connector must speak MCP; pasting a generic REST endpoint into its settings does not turn it into a tool. A REST-only service needs an MCP wrapper or application-side tool handling.
1. Choose the right connection
Remote connectors reach a hosted MCP service and usually use OAuth. Local extensions run an MCP process on your computer, for example to reach selected local files. Choose the official directory entry where possible, and review its publisher, requested access, and organization policy.
2. Add a remote connector
Open the Connectors area (Customize > Connectors in the new experience; some accounts use Settings > Connectors). Select a listed service or the available custom-connector option and enter the provider’s documented MCP server URL. Complete its authentication flow. Custom connectors and organization-wide setup depend on plan and admin policy.
3. Install a local extension
Go to Settings > Extensions, choose Browse extensions, inspect an entry, and install it. Fill in its required settings, such as an allowed folder or service credential. A custom .mcpb package uses Extensions > Advanced settings > Install Extension. Install only packages whose source and permissions you have reviewed.
4. Confirm tools, then test a read
Use the + menu and Connectors to inspect the tools available to the conversation. Ask for a specific read-only item and verify it against the source. If tools are missing, check authentication, required settings, administrator restrictions, then restart the desktop app. Remove or disconnect unused integrations and revoke service access when appropriate.
Read the test document I specify using the connected tool.
Tell me which tool you used and include the source link.
Do not send messages or modify records.Practice & self-check
Connect one service or local extension, prove a read-only result, and identify its disconnect control.
When you’re done, take a moment to check:
Read the official sources
CLI instructions checked against official documentation; API examples tested with simulated responses. Product-account walkthroughs were not performed.