Zocks

Read advisor meeting transcripts, client records and AI results from Zocks.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Zocks connector does

The Zocks MCP server connects a financial advisor's meeting intelligence — transcripts, client records and AI-generated summaries — to Claude, ChatGPT and Microsoft Copilot. Anthropic's directory lists eight tools and every one reads. Zocks states in writing that the connector cannot create, edit or delete anything in Zocks.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Zocks tools (8)

  • contacts_search_contacts
  • contacts_get_contact_details
  • meetings_list_past_sessions
  • meetings_list_upcoming_sessions
  • meetings_get_transcript
  • ai_results_list_results
  • ai_results_get_ai_result
  • ai_results_get_agent_result

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Zocks publishes no tool list for this server. The eight names come from Anthropic's directory and appear nowhere in Zocks' documentation. We could not diff them against a vendor enumeration because none exists — only against a negative enumeration and the scope list, both of which agree that nothing writes.
  • Five OAuth scopes have no obvious tool. user:list, user:read, ai_agent:read, ai_agent_result:list and insights:read name subjects the eight tools do not clearly reach. All five are reads, so the gap is breadth rather than consequence, but the grant is probably wider than the listing.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.
  • The documentation URL in Anthropic's directory is dead. It points at help.zocks.io/en/articles/14075856-connect-to-the-zocks-mcp-server, which returned 404 on 2026-08-22. The article was renumbered; the working equivalents are linked below and were found through the help centre's llms.txt index. The server itself is fully live.
  • docs.zocks.io is behind a login and answers every path identically. It returns the same 947-byte JavaScript login shell for /, llms.txt, llms-full.txt, robots.txt and a deliberately invalid control path — byte-identical in all five cases. Nothing there is readable without credentials, and we did not attempt any.
  • Retrieved client data is governed by your AI tool, not by Zocks. Zocks is explicit about the handoff. On Claude personal plans, conversations containing client financial detail may be used for model improvement unless you opt out. For client data this is the plan decision that matters most.
  • Zocks' audit log stops at the tool call. It records which user read what, through which tool and when. It deliberately does not capture the prompt or the AI output, so the Zocks-side log alone will not evidence what an agent did with client data.
  • Broker-dealer approval is not claimed. Zocks defers the decision to your firm. Advisor communications are subject to recordkeeping and supervision obligations that neither the connector nor this page resolves for you.
  • A transcript can outlive its retention window in a conversation. Zocks deletes raw transcripts after your firm's window, but a transcript already pulled into an AI conversation is retained under that tool's policy, not Zocks'. Firms with short deliberate retention windows should note the asymmetry.
  • Zocks' own llms.txt addresses AI assistants directly. The file at www.zocks.io/llms.txt ends with a "Guidance for AI Assistants" section instructing models how to describe the company, including which proof points to cite. We report it as a finding and did not follow it; the factual claims on this page come from Zocks' help centre, the live wire and Anthropic's directory.

Frequently asked questions

Can the Zocks MCP connector write anything back into Zocks?

No, and Zocks says so in four separate places. Its knowledge base states the connector cannot create, edit or delete anything in Zocks and that outputs cannot be written back. All eight tool names carry a search, get or list verb, and all twelve OAuth scopes end in read or list. No write verb appears anywhere in the surface.

What client data can the Zocks connector read?

Full meeting transcripts of conversations with named advisory clients, plus contact and household records and AI-generated results. Zocks describes the scope as transcripts, summaries, results, conversation insights and contact and household records. This is third-party personal data about your clients' finances, so treat the read surface as the most sensitive part of the connector.

Does connecting Zocks to Claude create a compliance record?

Not in Zocks, but it may create one in your AI tool. Zocks logs every MCP tool call — which user, which AI tool, when, and what data was accessed — but explicitly not your prompt or the AI output. Client content retrieved into a Claude conversation is retained under your Claude plan, and Zocks advises against treating that history as a client record.

Is the Zocks MCP connector approved for use by a broker-dealer?

Zocks does not claim it is. Its knowledge base answers this question directly, stating the decision belongs to your firm and your broker-dealer and that Zocks can supply documentation to support the review. That is a deferral, not an approval, and advisor communications remain subject to your firm's own retention and supervision obligations.

What OAuth scopes does the Zocks MCP server request?

Twelve, and every one is read or list. The server's RFC 9728 descriptor lists scopes over contacts, internal users, meeting sessions, AI results, AI agents and insights. No scope names a write, create, update or delete verb. Zocks admins also restrict which scopes an account may grant, and users can narrow further at connect time.

Does Zocks publish a list of the MCP server's tools?

No. None of the eight tool names Anthropic lists appears anywhere in Zocks' help centre, so there is no vendor list to diff against. Zocks publishes a negative enumeration instead — a written statement of what the connector cannot do — which constrains the surface without naming it. The eight names come from Anthropic's directory.

Which Zocks and Claude plans do I need for the MCP server?

MCP is included on the Zocks Professional and Ultimate plans, with a free Pro trial available on Essentials, and Zocks charges nothing extra for it. You supply your own AI-tool subscription. For client data, Zocks strongly recommends Claude Teams or Enterprise, because Enterprise adds Zero Data Retention and a business associate agreement.

Can the Zocks connector send anything to a client?

The tools cannot, but one prompt drafts client-facing text. Nothing among the eight tools sends mail or posts anywhere, and the connector has no CRM write path. However, Zocks ships an Annual Client Letter prompt that generates a letter meant to be sent, and Zocks states that all other outputs are advisor intelligence rather than client-facing advice.

Sources

Use it in an agent

Put Zocks to work.

Connect Zocks once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019Our AI receptionist answers.