StudioMeyer CRM

io.studiomeyerPublished by studiomeyer.ioOfficial publisherv2.13.0Updated Oct 24, 2026

AI-native CRM. 37 tools: pipeline, leads, health scores, GDPR rights. EU-hosted, free tier.

The publisher's own server: StudioMeyer Crew

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

StudioMeyer CRM is a remote, AI-native CRM server that gives an assistant 37 tools for pipeline, leads, health scores and GDPR rights.

What you can do
Work with sales pipeline and deal stages through the CRM tools. Manage leads and related customer records. Read customer health scores. Handle GDPR data-rights requests. All of this runs against an EU-hosted CRM account rather than local data.
When to use it
Useful when an assistant should work directly with a CRM account: reviewing pipeline, managing leads, checking customer health, or handling GDPR rights requests without switching to the CRM interface.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required, so a StudioMeyer CRM account with OAuth sign-in is needed. No environment variables or headers are declared. A free tier is offered.
Before you install
The server can read and likely change CRM records such as leads and pipeline, and it handles GDPR data-rights requests, which involve personal data. Confirm what each tool writes or deletes before use, and note that customer data is held on the provider's EU-hosted service.

Installation

In SourceWeft

  1. Open StudioMeyer CRM 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%2Fcrm/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-crm": {
      "type": "http",
      "url": "https://crm.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.13.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