MewCP

com.mewcpPublished by mewcp.comOfficial publisherv2.0.0Updated Nov 7, 2026

One gateway, every app: Gmail, GitHub, Notion and more. Connect once, call any tool. Managed auth.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

A remote gateway that gives an assistant one connection to tools across many apps, such as Gmail, GitHub and Notion, with managed authentication.

What you can do
  • Call tools across connected apps through a single gateway
  • Work with mail, code hosting and notes-style services such as Gmail, GitHub and Notion
  • Rely on the gateway's managed authentication instead of per-app setup
  • Connect once and reach any tool the gateway exposes
When to use it
Useful when you want one assistant connection covering several unrelated apps rather than installing a separate server per service, and you are comfortable routing those app actions through a hosted third-party gateway.
Requirements
A remote streamable HTTP endpoint at the provider's gateway. A MewCP API key is required, sent as a Bearer token in the Authorization header. Network access to the gateway is needed.
Before you install
The API key is a secret sent in the Authorization header; keep it private. The gateway acts on connected apps such as Gmail, GitHub and Notion, so actions may read, send or change data in those accounts, and the provider handles authentication and sees the traffic. The manifest lists no tools, so check exactly which apps and actions are exposed before connecting.

Installation

In SourceWeft

  1. Open MewCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/com.mewcp%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.

{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestNov 7, 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.

Other Mewcp integrations