Zeeg

me.zeegPublished by zeeg.meOfficial publisherv2.0.0Updated Oct 24, 2026

Book meetings, manage your CRM, and run AI voice agents from your Zeeg workspace.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Zeeg's remote MCP server lets an assistant book meetings, manage CRM records and run AI voice agents from a Zeeg workspace.

What you can do
Book meetings and manage scheduling from the assistant's conversation with the Zeeg workspace tools. Manage CRM records such as contacts and related customer data. Run and operate AI voice agents within the same workspace. The manifest lists no individual tools, so exact capabilities should be confirmed in Zeeg's documentation.
When to use it
Useful when you already work in Zeeg and want an assistant to schedule meetings, keep CRM data current, or operate voice agents without switching apps.
Requirements
A remote server reached at the Zeeg API endpoint over streamable HTTP. OAuth authentication is required, so a Zeeg account and an OAuth authorization flow are needed. No environment variables or headers are declared.
Before you install
The server can change workspace data: booking meetings and editing CRM records are write actions, and voice agents may contact people. Access is granted through OAuth, so review the scopes requested during authorization. Customer data handled by the assistant is sent to Zeeg.

Installation

In SourceWeft

  1. Open Zeeg in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/me.zeeg%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zeeg": {
      "type": "http",
      "url": "https://api.zeeg.me/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v2.0.0LatestOct 11, 2026
  2. v1.0.0Sep 27, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.