vibemcp

VibeMCP is a token-efficient MCP server that unifies Gmail and Microsoft 365 access behind a single interface. It streams data using the TOON format by default, with optional JSON output available via the format parameter. The server exposes a suite of tools for account management and email/calendar operations across both ecosystems, including adding Google and Microsoft accounts, listing messages, sending emails, and managing labels. Start by authenticating with Google and/or Microsoft, then use the built-in tools to fetch emails, calendar events, or perform common email actions. The server can be driven from an MCP client via standard commands, and you can request outputs in either TOON or JSON depending on your needs for token efficiency.

Prerequisites:

• Node.js 18+ (recommended)
• npm or corepack available

Installation steps:

1. Ensure Node.js is installed. Verify with: node -v npm -v
2. Run the MCP client setup using npx (no local install required) as shown in the Quick Start:

# Quick start (run the server via npx)
npx -y @vibetensor/vibemcp

3. Alternatively, if you want to pin a local version or install locally:

# Install the package locally (optional)
npm install @vibetensor/vibemcp
# Run the server (adjust path if needed)
node node_modules/@vibetensor/vibemcp/server.js

4. Configure credentials via environment or a .env file and start the server using the configuration example in the mcp_config section. For developer setup, follow the documentation at vibemcp.vibetensor.com for Google Cloud and Azure setup.

Tips and notes:

• The server supports both TOON and JSON outputs via a format parameter; TOON is more token-efficient.
• Environment variables for Google and Microsoft OAuth are required to authenticate accounts; you can place them in a .env file in your working directory or in ~/.vibemcp/.env.
• If you are using the provided mcp_config, ensure the env block is populated with your credentials before starting.
• The npm package name for this Node.js MCP server is @vibetensor/vibemcp.
• If you encounter rate limits or OAuth consent prompts, ensure your Google Cloud and Azure app registrations are configured with appropriate redirect URIs and consent screens as per the documentation.