mcpbeat Sign in

Meridian MCP Server

by the-meridian Your server? Claim it
answering

Meridian is answering right now. Last checked 11 min ago.

Plans, deploys, logs, webhooks and API alerts for Shopify apps built on Meridian.

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
170 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Meridian 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 11 min ago.

run in your terminal
claude mcp add meridian --transport http https://mcp.the-meridian.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.the-meridian.ai/mcp
~/.codex/config.toml
[mcp_servers.meridian]
url = "https://mcp.the-meridian.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "meridian": {
      "url": "https://mcp.the-meridian.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "meridian": {
      "type": "http",
      "url": "https://mcp.the-meridian.ai/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://mcp.the-meridian.ai/mcp streamable-http sign-in 130 ms 11 min ago

Alternatives to Meridian

same job, measured the same way
Sota
by sota-deploy

Deploy web apps via AI agents with sota.io. 9 tools for deploy, logs, env, and more.

local only
AppCrane
by gitayg

Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.

369 installs/wk local only
Vercel
by pulsemcp

MCP server for Vercel — manage deployments and view build and runtime application logs.

99 installs/wk local only
microservices.sh
by microservices

MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

65 installs/wk answering
InstaPods
by instapods

Deploy and manage web apps on InstaPods: create pods, push files, run commands, read logs.

answering
SnapDeploy
by somdip-2310

Deploy and manage SnapDeploy apps from your AI assistant: builds, logs, env vars, add-ons, domains.

91 installs/wk local only
Tv MCP
by skdonthi

Build, deploy, and debug web apps on Samsung Tizen and LG webOS Smart TVs from any MCP client

10 installs/wk local only
AppHandoff
by teamk2k

Milestones, handoff tickets, project context, and deploy signals for AI-built apps over MCP.

answering

Meridian — questions

Answers built from our own checks of this server.

Why is there no tool list for Meridian?
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 Meridian 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 170 ms. The bar chart above shows every period we have measured.
How do I connect Meridian?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Meridian?
No API key is involved. Meridian 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 Meridian?
It answers our handshake in 170 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.