MCP.Market

Meridian MCP server

by meridian-silkdev·io.github.meridian-silkdev/meridian-mcp·v0.1.2
No reviews yet

MCP server for Meridian: services, requests, workflow, payments, meetings for founders.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed Meridian yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Meridian tools (16, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • advance_step

    Advance the current step for a request to the next step (completes current step and moves currentStepId). Validates phase transitions.

  • create_meetingwrite action

    Create a meeting with title, scheduledAt (ISO), duration minutes, optional serviceRequestId, and invite selection (customer/provider). Creates Teams meeting via Graph and sends invites immediately.

  • create_service_requestwrite action

    Create a new service request. Needs serviceId (or slug) and answers matching the service formConfig.

  • get_payment_status

    Get payment state for a service request (Payment row: amount, status, provider, serviceRequestId unique). Returns verification status — never trust redirect alone.

  • get_service

    Get a single Meridian service by id or slug, including formConfig and delivery steps.

  • get_service_request

    Get a single service request by id, including current step, phase, and requestSteps.

  • get_workflow_status

    Get the workflow state for a request: current phase, current step, and all requestSteps with status (PENDING/IN_PROGRESS/COMPLETED). Status is derived from currentStepId → phase.

  • list_categories

    List Meridian service categories (name, slug, icon, isActive, sortOrder, countryCode).

  • list_meetings

    List meetings. Filter by serviceRequestId, status, or participant userId. Meetings are created with a fixed title/time/duration and explicit invites (customer/provider/both).

  • list_request_steps

    List all RequestSteps for a request in order, including key, phase, assignedTo, stepType, status, startedAt, completedAt.

  • list_service_requests

    List service requests. Filter by status (DRAFT, REQUIREMENTS, ADMIN_VALIDATION, PROVIDER_ACCEPTANCE, QUOTE, PAYMENT, DELIVERY, FULFILLMENT, COMPLETED, DISPUTED, CANCELLED), customerId, providerId.

  • list_services

    List Meridian services. Filter by category slug, active flag, or country code (e.g. TN, FR, PT).

  • meridian_status

    Check Meridian API connectivity (MERIDIAN_API_URL + MERIDIAN_API_KEY) and list available tools/resources. No params.

  • respond_to_meeting

    Record RSVP for a meeting (ACCEPTED/DECLINED/PENDING). Declining records your answer but does NOT cancel the meeting.

  • update_request_statuswrite action

    Advance or set a request's status. Prefer advance_step for workflow transitions. Use only when you know the target phase is valid.

  • verify_payment

    Verify a payment with the provider (Flouci for Tunisia — local wallet/card — or Stripe for international cards). Triggers server-side verification — redirect back to the portal alone is never proof of payment.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan21 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 42 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Meridian compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,243 servers
Tools
16
the typical server has 7
Tools that change things
19%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
28
more than 15% of 12,306 servers with a package

What its tools let an agent do: 13 read · 2 create · 1 change

Install Meridian in Claude Code, Cursor or VS Code

Runs npx -y @meridiantoolkit/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add meridian-mcp -- npx -y @meridiantoolkit/mcp
Add to Cursor

What the publisher says

From the Meridian repository's README, as published. We do not edit it. Read it on GitHub

@meridiantoolkit/mcp

MCP server for the Meridian business-services platform. Exposes services, service requests, workflow steps, payments and meetings as Model Context Protocol tools and resources. MCP is a protocol, not a host-specific plugin format — this server runs unchanged in Claude Code, Codex CLI, Claude Desktop, pi, or any other MCP-compatible client.

Listed on the official MCP Registry as io.github.meridian-silkdev/meridian-mcp, and on Glama.

Install

cd meridian-mcp
npm install
npm run build

Or once published:

npx @meridiantoolkit/mcp

Configure

Copy .env.example or set env vars directly:

More: /.well-known/agent-configuration exposes Agent Auth discovery (capability-based, short-lived JWTs, device-auth/CIBA approval). Agents can use either a long-lived mrd_ key or scoped Agent Auth grants — see meridian-skills meridian-api skill.

Without MERIDIANAPIKEY every tool still responds — it explains what endpoint would be called and what to configure, so the server is safe to run in dry-run / demo mode.

Run

npm start            # stdio MCP server
npm run dev          # watch mode via tsx

Claude Code

claude mcp add meridian -- node /absolute/path/to/meridian-mcp/dist/index.js
# or, once published:
claude mcp add meridian -- npx -y @meridiantoolkit/mcp

Or drop a .mcp.json in your project root (shareable with a team, checked into git):

{
  "mcpServers": {
    "meridian": {
      "command": "npx",
      "args": ["-y", "@meridiantoolkit/mcp"],
      "env": {
        "MERIDIAN_API_URL": "http://localhost:3000",
        "MERIDIAN_API_KEY": "..."
      }
    }
  }
}

Codex CLI

Codex reads MCP servers from ~/.codex/config.toml (or a project-scoped .codex/config.toml for a trusted project):

[mcp_servers.meridian]
command = "npx"
args = ["-y", "@meridiantoolkit/mcp"]
env = { MERIDIAN_API_URL = "http://localhost:3000", MERIDIAN_API_KEY = "..." }

Or via the CLI: codex mcp add meridian -- npx -y @meridiantoolkit/mcp. The same config is shared by Codex CLI, the IDE extension, and the ChatGPT desktop app.

Codex has no plugin/skill system (unlike Claude Code and pi) — its equivalent of meridian-plugin/meridian-skills is just this MCP server plus project guidance. Copy AGENTS.md.example into your project's AGENTS.md for the same tool-usage guidance the skills packages give elsewhere.

Claude Desktop / pi

Add to your MCP config (Claude Desktop: claudedesktopconfig.json; pi: .pi/settings.json → mcpServers, or pi --mcp):

{
  "mcpServers": {
    "meridian": {
      "command": "node",
      "args": ["/absolute/path/to/meridian-mcp/dist/index.js"],
      "env": {
        "MERIDIAN_API_URL": "http://localhost:3000",
        "MERIDIAN_API_KEY": "..."
      }
    }
  }
}
pi --mcp meridian-mcp/dist/index.js
# or via npx after publish
npx @meridiantoolkit/mcp

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Meridian: common questions

Is Meridian MCP server safe?
Mostly: it is graded B (77/100). Read the Meridian safety report
How do I install Meridian?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Meridian need an API key?
Yes. The registry entry asks for MERIDIAN_API_KEY.
Is Meridian maintained?
The last commit was 62 days ago (2026-09-04). The latest release is v0.1.2.
How does Meridian compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,243 servers); tools 16 (the typical server has 7); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.