Developer · Local MCP server
Meridian Skills
Routes AI tasks to dynamic LLM-generated skills via an orbital classifier.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.LuuOW/meridian-skills- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-02
- Updated
- 2026-05-02
- Publisher
- LuuOW (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/LuuOW) · how
- Repository
- github.com/LuuOW/meridian-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | meridian-skills-mcp | 1.0.0 | stdio |
How to connect Meridian Skills
Meridian Skills runs locally from a Node.js package published to the npm registry: meridian-skills-mcp version 1.0.0. 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 meridian-skills-mcp@1.0.0. It reads these environment variables: MERIDIAN_API_URL, MERIDIAN_API_KEY (secret) and MERIDIAN_TIMEOUT_MS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"meridian-skills": {
"command": "npx",
"args": [
"-y",
"meridian-skills-mcp@1.0.0"
],
"env": {
"MERIDIAN_API_URL": "<value>",
"MERIDIAN_API_KEY": "<secret>",
"MERIDIAN_TIMEOUT_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. 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 developer servers
| Server | Runs |
|---|---|
| Mercury Spec OpsModular MCP server for dynamic prompt generation and software development analysis tools. | Local · stdio |
| Merge Conflict Forecaster MCPPredict local Git merge-conflict pressure from branch topology and changed-file overlap without... | Local · stdio |
| MergetrainQueue parallel-agent worktree branches, test together, serialize and recover Git pushes. | Local · stdio |
| MergewardenCheck whether a coding agent's changes stayed inside the scope it was given. | Local · stdio |
| Merlonix MonitoringMonitoring for agencies - uptime, SSL, DNS, blocklists, AI visibility, MCP health. 8 no-auth tools. | Remote · HTTPLive check: ✓ handshake |
| Mermaid MCP AppMCP App that renders Mermaid diagrams as interactive UI in Claude, VS Code and other MCP clients. | Local · stdio |
| MeroFoundryBuild and publish full-stack apps from your coding agent: models, rules, pages, auth, per-app MCP. | Remote · HTTPLive check: sign-in required |
| MERX - TRON Resource ExchangeTRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP. | Remote & Local · HTTP, stdioLive check: ✓ handshake |