com.maennche/studio-connector
Maennche Studio
Is the Maennche Studio MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Work with Maennche Studio records after you sign in and choose a business.
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"Unauthorized"}- Endpoint
- https://mcp.maennche.com/mcp (streamable-http)
- Host
- mcp.maennche.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.maennche.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.maennche.com, PKCE S256, grants authorization_code, refresh_token.
Scopes tickets:read tickets:comment tickets:write contacts:read contacts:write companies:read companies:write notes:read notes:write documents:read documents:write tasks:read tasks:comment tasks:write files:read kb:read brand_profiles:read crm_target_lists:read crm_target_lists:write prospects:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.maennche.com/studio-connector
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention connector.
- Elaichi ai.elaichi/mcp · needs auth
- LensHub ai.lenshub/lenshub · needs auth
- PDS Project AI MPP Connector ai.projectdata/mpp-connector · needs auth
- ProvenSkills Labs ai.provenskills/labs · needs auth
- Era Context app.era/context · needs auth
- Lucid app.lucid.mcp/lucid · needs auth
- Fedlex Connector ch.fedlex-connector/fedlex-connector · alive
- Glide — wallets and US banking co.glide/banking-connector · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.