StudioMeyer Crew

io.studiomeyerPublished by studiomeyer.ioOfficial publisherv2.8.0Updated Oct 27, 2026

Agent personas for Claude. 16 tools, 13 personas, 3 workflows. Zero extra API cost. Free.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

Remote MCP server that adds agent personas, 16 tools and 3 workflows to Claude, with no extra API cost.

What you can do
  • Provides agent personas for Claude, described as 13 in total.
  • Exposes 16 tools, though the individual tools are not listed in the available material.
  • Offers 3 predefined workflows.
  • Advertised as adding no extra API cost and being free.
When to use it
Worth considering if you want to give Claude a set of predefined personas and workflows rather than building them yourself, and you are comfortable connecting to a hosted third-party endpoint.
Requirements
A remote MCP endpoint at crew.studiomeyer.io over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Authentication is required via OAuth, so you sign in to a third-party service; review what account access it requests. The tool list is not published, so what the 16 tools can do, and whether any of them write or send data, is not documented here.

Installation

In SourceWeft

  1. Open StudioMeyer Crew in the dashboard and add it to a workspace.
  2. Connect the required 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%2Fcrew/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "studiomeyer-crew": {
      "type": "http",
      "url": "https://crew.studiomeyer.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.8.0LatestSep 16, 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 Studiomeyer integrations