StudioMeyer MCP Suite

io.studiomeyerPublished by studiomeyer.ioOfficial publisherv1.0.0Updated Oct 27, 2026

8 MCP servers, 104+ tools: memory, social, PDF, email, images, calendar, scheduler, files.

The publisher's own server: StudioMeyer Crew

Overview

AI-generated overview

Remote MCP suite bundling eight servers and 104+ tools for memory, social, PDF, email, images, calendar, scheduling and files.

What you can do
  • Store and recall persistent memory across sessions
  • Work with PDFs and files, including reading and producing documents
  • Handle email and social channel activity
  • Manage calendar events and scheduled tasks
  • Process images as part of these workflows
When to use it
Worth adding when you want one hosted connection that covers several everyday assistant tasks — remembering context, handling documents, email, calendar and scheduling — instead of wiring up separate servers for each.
Requirements
A remote streamable HTTP endpoint at mcp.studiomeyer.io; no local package or runtime. Authentication is required: an OAuth 2.0 bearer token sent in the Authorization header, obtained through the provider's OAuth authorization flow.
Before you install
The single bearer token grants access to all eight bundled servers, so it covers email, social, calendar and files at once; treat it as a broad credential and keep it out of logs. Tools are not listed in the manifest, so review the actual tool set after connecting. Email, social and calendar tools can send or change data on your behalf.

Installation

In SourceWeft

  1. Open StudioMeyer MCP Suite 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/io.studiomeyer%2Fmcp-suite/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": {
    "studiomeyer-suite": {
      "type": "http",
      "url": "https://mcp.studiomeyer.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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. 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 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Studiomeyer integrations