Mayla Debug Mcp Google Calendar2

ai.smitheryPublished by smithery.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Schedule and manage Google Calendar events directly from your workspace. Check availability, view…

The publisher's own server: 222wcnm Bilistalkermcp

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that lets an assistant schedule and manage Google Calendar events from your workspace.

What you can do
Schedule and manage Google Calendar events directly from the workspace, including checking availability and viewing calendar information. The manifest lists no individual tools, so the exact set of actions is not documented.
When to use it
Useful when you want an assistant to create or adjust calendar events and check availability without leaving the conversation.
Requirements
A remote endpoint at server.smithery.ai over streamable HTTP. An Authorization header carrying a Smithery bearer token is declared. No environment variables or packages are listed.
Before you install
The server asks for a bearer token in the Authorization header, so treat it as a secret. Calendar actions may create or change events; the manifest does not document which operations write data or what is shared with third parties.

Installation

In SourceWeft

  1. Open Mayla Debug Mcp Google Calendar2 in the dashboard and add it to a workspace.
  2. 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/ai.smithery%2Fmayla-debug-mcp-google-calendar2/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.

{
  "mcpServers": {
    "mayla-debug-google-calendar2": {
      "type": "http",
      "url": "https://server.smithery.ai/@mayla-debug/mcp-google-calendar2/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Smithery integrations