Productivity · Remote MCP server
Meridian
Persistent memory, task coordination, and HITL queue for AI coding sessions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ajc3xc/meridian- Version
- 1.0.2
- Status
- Active
- Category
- productivity
- Transport
- SSE (HTTP + Server-Sent Events), stdio (local process)
- Package
- npm
- Published
- 2026-06-02
- Updated
- 2026-06-02
- Publisher
- ajc3xc (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ajc3xc) · how
- Repository
- github.com/meridianmcp/Meridian
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://usemeridian.us/mcp/sse | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @meridianmcp/mcp | 1.0.2 | stdio |
How to connect Meridian
Meridian is a remote MCP server reached over the older SSE transport, at https://usemeridian.us/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @meridianmcp/mcp version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @meridianmcp/mcp@1.0.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"meridian": {
"command": "npx",
"args": [
"-y",
"@meridianmcp/mcp@1.0.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| MensoAI users run real tasks on your live site and show where they get stuck, with a replay of every step. | Remote · HTTPLive check: ✓ handshake |
| Meok Ev Recall Transport MCPEV-recall transport compliance - ADR Class 9 (UN3480/3481/3536/3556/3557/3558), DGSA workflow. | Local · stdio |
| MepMailTransactional email with a Resend-compatible API: send emails, manage broadcasts and domains. | Remote · HTTPLive check: sign-in required |
| MercosSales force and rep ERP on Mercos via the official API. List orders, customers, products, price tabl. | Remote · HTTPLive check: ✓ handshake |
| Meridian MCPMCP server for Meridian: services, requests, workflow, payments, meetings for founders. | Local · stdio |
| Meridian SkillsRoutes AI tasks to dynamic LLM-generated skills via an orbital classifier. | Local · stdio |
| MermailPrivacy-first email inboxes for AI agents with MCP mail tools and Composio connect/execute. | Remote · HTTPLive check: sign-in required |
| Meser10 MCPOperate the Meser 10 email and SMS platform from any MCP client. Read-only by default. | Local · stdio |