mcpbeat Sign in

Plixana MCP Server

answering

Plixana is answering right now. Last checked 1 min ago.

Operate the Plixana CRM from any AI: contacts, deals, quotes, WhatsApp and metrics.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
447 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Plixana every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add crm --transport http https://plixana.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "crm": {
      "url": "https://plixana.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.crm]
url = "https://plixana.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "crm": {
      "url": "https://plixana.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "crm": {
      "url": "https://plixana.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://plixana.com/api/mcp streamable-http sign-in 845 ms 1 min ago

Alternatives to Plixana

same job, measured the same way
SigParser
by sigparser

Query contacts, companies, relationships, and communication metrics from SigParser.

answering
Eutexa CRM
by eutexa

Search contacts, track deals, create tasks and log notes in your Eutexa CRM workspace.

answering
Opik MCP Server
by comet-ml

Interact with Opik prompts, traces, datasets and metrics through the Model Context Protocol.

70 installs/wk local only
Ezstat MCP Server
by ezstat

Track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible.

87 installs/wk local only
Sable Platform + HyperDX Observability
by sable-inc

Manage Sable AI voice agents, query HyperDX logs and metrics, and deploy — all from your IDE

local only
Octoperf
by octoperf

Drive OctoPerf load testing from any AI agent: import, edit, validate, run scenarios, read metrics.

answering
Blazingcdn MCP
by blazingcdn

Manage BlazingCDN from AI agents: CDN zones, cache, metrics, domains, cloud storage and video CDN

251 installs/wk local only
Warpmetrics
by warpmetrics

Connect AI assistants to Warpmetrics — query runs, calls, costs, and outcomes.

40 installs/wk local only

Plixana — questions

Answers built from our own checks of this server.

Why is there no tool list for Plixana?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Plixana working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 447 ms. The bar chart above shows every period we have measured.
How do I connect Plixana?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Plixana?
No API key is involved. Plixana answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Plixana?
It answers our handshake in 447 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.