Skip to main content

Connect to the Zocks MCP Server with Microsoft Copilot

How to connect Microsoft Copilot to the Zocks MCP server via Copilot Studio to access your meeting intelligence directly in Microsoft 365 Copilot.

Use the Zocks MCP server to bring your meeting intelligence directly into Microsoft Copilot. This lets you ask open-ended questions about client conversations, surface insights from conversations, and interact with Zocks data in the AI tools you already use.

Use cases

The Zocks MCP server makes your client intelligence available directly inside Microsoft Copilot. You can ask natural questions and get synthesized answers grounded in your actual meeting data.

With the Zocks MCP, you can:

  • Surface a client's motivators, concerns, and goals across all past meetings

  • Retrieve everything discussed with a household on any topic over a given time period

  • Score and evaluate your most recent advisor meetings

  • Identify financial planning gaps for any household

  • Track client sentiment and engagement trends over time

  • Scan meeting transcripts for compliance and suitability concerns

  • Identify referral opportunities hidden in client conversations

  • Build discovery talk tracks and coaching tools from real advisor meetings

  • And more!

How it works

The Zocks MCP server is a remotely hosted service that makes your firm's meeting intelligence available to any AI client that supports the Model Context Protocol. When you ask Microsoft Copilot a question about a client or meeting, the Copilot agent recognizes that it needs Zocks data, queries through MCP, and responds using your actual transcripts and AI-generated summaries.

When connected, the server:

  • Authenticates users via OAuth 2.0 through your Zocks login - meaning no passwords shared with Microsoft

  • Provides access only to meetings and data the authenticated user is already authorized to see in Zocks

  • Allows Copilot to interpret your question naturally while Zocks supplies the grounded, sourced meeting data

Note: Copilot handles question interpretation and language generation. Zocks provides the underlying intelligence. This means you can ask open-ended questions like "What did the Johnson family discuss about college planning?".

Prerequisites

Before any user in your organization can connect to Zocks' MCP server:

  • Copilot access must be enabled in Zocks. Follow steps described in this article.

  • Each connecting user must have an active Zocks account with access to the relevant meetings.

  • Microsoft 365 Copilot license for every user who will use the agent, including the admin doing setup.

  • Access to Microsoft Copilot Studio (copilotstudio.microsoft.com) with a Power Platform environment and permission to create agents. The admin must have the Environment Maker or System Administrator role in the Power Platform environment.

Connect Microsoft Copilot to Zocks MCP

Microsoft Copilot (via Copilot Studio)

Unlike Claude and ChatGPT, Zocks is not available as a one-click connector in Microsoft Copilot's native app directory. Instead, a Copilot Studio admin builds and publishes a custom agent that connects to the Zocks MCP server directly. Once the agent is deployed to the organization, each user authenticates with their own Zocks account the first time they use it.

Step 1 - Enable Copilot in Zocks (Zocks admin)

Follow steps described in this article.

Step 2 - Build the agent in Copilot Studio (Copilot Studio admin)

All steps in this phase are performed in Copilot Studio.

Step 2a - Create a new agent

  1. Go to copilotstudio.microsoft.com and sign in with your Microsoft 365 admin account.

  2. Make sure you are in the correct Power Platform environment. The current environment is shown in the top-right corner — select it to switch if needed.

  3. On the Home page, in the description box, enter: Help financial advisors access Zocks meeting intelligence, client insights, and conversation summaries.

  4. Copilot Studio uses this description to automatically generate a name, description, and instructions for the agent. Once it finishes provisioning, the agent Overview page opens.

  5. Update the agent name to Zocks.

  6. Replace the auto-generated instructions with the following, then select Save:

    You are a financial advisory assistant with access to Zocks, a meeting intelligence platform. When a user asks about a client, household, advisor, or meeting, use the Zocks MCP tools to retrieve the relevant data before answering. Always ground your answers in data retrieved from Zocks. Do not make up client information. If Zocks returns no data, say so clearly.

Step 2b - Add the Zocks MCP server as a tool

  1. In the left navigation, select Tools (or scroll to the Tools section on the Overview page).

  2. Select + Add a tool.

  3. In the panel that opens, select + New tool.

  4. Select Model Context Protocol. The MCP onboarding wizard opens.

  5. Fill in the server details:

    • Server name: Zocks

    • Server description: Provides access to Zocks conversation intelligence. Use this to answer any question about a client, meeting, or household or to analyze conversation insights.

  6. Under Authentication, select OAuth 2.0.

  7. For the OAuth 2.0 type, select Dynamic discovery. Copilot Studio will automatically discover all of Zocks' OAuth endpoints — no manual entry of client IDs, secrets, or token URLs is needed.

  8. Select Create. Copilot Studio registers the MCP server and creates a Power Platform custom connector for it in the background.

  9. The Add tool dialog appears. In the Connection dropdown, select Create a new connection, then select Create. A browser window opens — sign in with your Zocks account to authorize the connection.

  10. Once the connection is created, select Add and configure. You will see a list of all Zocks MCP tools available to the agent. Leave all tools enabled and select Add to agent.

Note: The connection you create here is your personal admin connection used for testing. Each user in your organization creates their own connection when they first use the published agent - they authenticate with their own Zocks account at that point.

Step 2c - Test the agent before publishing

  1. Select Test in the top-right corner to open the test chat panel.

  2. Try a question such as: "What did the Johnson household discuss about retirement planning in their last meeting?"

  3. On first use in the test panel, the agent will prompt you to enable the connection. Select Open connection manager, then select Connect, then Submit. Return to the test panel and select Retry — the agent will now call Zocks and return a grounded answer.

  4. If the agent responds without calling Zocks (i.e., it says it doesn't know or makes something up), verify that the tool description is detailed and specific. The AI uses the tool description to decide when to invoke Zocks — a vague description leads to it being skipped.

Step 3 - Publish and deploy to the organization (Copilot Studio admin + Microsoft 365 admin)

Step 3a - Publish the agent

  1. In the top menu bar, select Publish.

  2. On the Publish page, review the details and select Publish to confirm. A green banner confirms success. Publishing makes the agent available for deployment — it is not yet visible to users.

Step 3b - Connect to the Microsoft 365 Copilot channel

  1. After publishing, select Channels in the top menu bar.

  2. Select the Microsoft 365 Copilot tile.

  3. Select Add channel to confirm. The agent is now connected to Microsoft 365 Copilot.

Step 3c - Deploy org-wide

  1. In the Microsoft 365 Copilot channel settings, select Availability options.

  2. Select Show to everyone in my org.

  3. Review the submission checklist, then select Submit for admin approval and confirm. The agent enters a pending state while your Microsoft 365 admin reviews it.

  4. The Microsoft 365 admin receives the submission in the Microsoft 365 Admin Center under the Copilot agent management section. They review the agent's name, description, and permissions, then approve it.

  5. Once approved, the agent appears in the Built by your org section of the Microsoft 365 Agent Store and is discoverable by everyone in the organization.

Step 4 - User setup: connect your Zocks account

Once the agent is deployed, each user completes a one-time sign-in to connect their own Zocks account. Zocks uses OAuth 2.0, so users are redirected to the Zocks login page — they never share their Zocks password with Microsoft.

  1. Open Microsoft 365 Copilot (or select the Copilot icon in any Microsoft 365 app).

  2. Select the agent icon in the chat composer and choose Zocks from the list, or type @Zocks to address the agent directly.

  3. Ask any Zocks-related question, for example: "What are the top planning concerns for the Miller household?" The agent will prompt you to sign in before retrieving your data.

  4. Select Sign in to Zocks in the agent's response. A browser window opens, redirecting you to the Zocks login page.

  5. Sign in with your Zocks credentials (the same login you use at app.zocks.io).

  6. On the Zocks authorization page, review the permissions requested, then select Allow. These are read-only permissions — the agent can read your meeting data but cannot create, edit, or delete anything in Zocks.

  7. You are redirected back to Copilot. The agent retries your question automatically and returns an answer using your Zocks data. Your account is now connected — you will not need to sign in again.

Troubleshooting

  • Authentication error during sign-in — Verify you are signing in with the same account you use for Zocks. Check that your Zocks account is active and in good standing.

  • Copilot Studio agent does not call Zocks tools — Check that the tool's Server description is detailed and specific. The agent's AI orchestrator uses the description to decide when to call Zocks. A vague description (e.g., just "Zocks") often causes the agent to skip the tool entirely. Update the description to include keywords like "client", "meeting", "household", "transcript", and "advisor".

  • Copilot Agent returns an error when connecting to Zocks MCP — Double-check that the Server URL in Copilot Studio is exactly https://mcp.zocks.io/v1/mcp. A trailing slash or typo will cause a connection failure.

  • Users cannot find the Zocks agent in Microsoft 365 Copilot — The agent has not yet been approved and deployed by a Microsoft 365 admin, or the user's role is not included in the Roles with access setting in Zocks (Step 1). Check both the admin approval status and the Zocks permissions.

For additional help, contact Zocks Support at [email protected]

Did this answer your question?