Does meetergo have an MCP server?

Yes Official

meetergo maintains an official MCP server.

Verified 2026-09-29 against vendor docs
Access
Remote server
Endpoint
https://mcp.meetergo.com/mcp
Maintainer
meetergo
License
MIT
Language
TypeScript
Stars
2
Last commit
1mo ago
The receipts
Vendor-hosted https://mcp.meetergo.com/mcp

A remote server run by meetergo itself — nothing to install. Documented at developer.meetergo.com.

Official package @meetergo/mcp-server

Published on npm. The package page carries the exact launch arguments and required credentials.

Official repository meetergo/meetergo-mcp-server
★ 2 pushed 2026-08-27 MIT Maintained
Connect it

Hosted by the vendor — no install, connect over HTTP with OAuth or a token.

Add it from the terminal, then restart your session:

terminal
claude mcp add --transport http meetergo https://mcp.meetergo.com/mcp

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does meetergo have an official MCP server?

Yes. meetergo maintains an official MCP server, hosted at https://mcp.meetergo.com/mcp, distributed as @meetergo/mcp-server on npm. The source lives at meetergo/meetergo-mcp-server on GitHub.

How do I connect meetergo to Claude?

Add https://mcp.meetergo.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http meetergo https://mcp.meetergo.com/mcp" in Claude Code.

Do I need to install anything to use the meetergo MCP server?

No. It is a remote server hosted by meetergo, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.

How is this verdict verified?

Published to the MCP Registry under meetergo's verified namespace com.meetergo; developer.meetergo.com/mcp-server documents the hosted endpoint and the npm package (maintained by a meetergo.com account, source in github.com/meetergo/meetergo-mcp-server), and mcp.meetergo.com/mcp answers MCP initialize with 401. GitHub metadata is refreshed every six hours.

How we know

Published to the MCP Registry under meetergo's verified namespace com.meetergo; developer.meetergo.com/mcp-server documents the hosted endpoint and the npm package (maintained by a meetergo.com account, source in github.com/meetergo/meetergo-mcp-server), and mcp.meetergo.com/mcp answers MCP initialize with 401.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Workplace & Productivity

See all Workplace & Productivity servers →