Skip to main content
Glama
SLA.directory MCP Server

SLA.directory MCP Server

by self9dmin

SLA.directory MCP server

An MCP server that lets AI assistants query SLA.directory in context: uptime commitments, service credits, claim windows, and per-service SLAs for cloud and SaaS vendors.

It reads the public SLA.directory API at runtime (with a short cache). No API key, no data bundled.

Tools

  • search_vendors(query): find vendors and services by name or category.

  • get_vendor(slug): full SLA record for one vendor.

  • get_service_sla(slug, service?): per-service SLAs (e.g. AWS S3 vs EC2), optionally filtered.

  • compare_vendors(slugs[]): key terms side by side (uptime, max credit, claim window, auto-credit).

  • list_categories() and vendors_in_category(category).

Vendor lookups are fuzzy (e.g. "Amazon Web Services" resolves to aws), answers are concise and cited (every result carries the official source URL and verification date), and tools are marked read-only so assistants can call them freely.

Related MCP server: GetMonitor MCP Server

Prompts

Ready-made flows you can pick in the client:

  • sla_review(vendor): summarize one vendor's SLA (uptime, credits, claim process, exclusions, weakest services).

  • compare_for_renewal(vendors): compare several vendors for a renewal decision.

  • weakest_services(vendor): find a vendor's lowest-uptime services for error-budget planning.

Use it

Run with Node 18+ (no install needed once published):

npx sla-directory-mcp

Claude Desktop / Cursor

Add to your MCP config:

{
  "mcpServers": {
    "sla-directory": {
      "command": "npx",
      "args": ["-y", "sla-directory-mcp"]
    }
  }
}

Then ask things like "What's AWS S3's SLA?", "Compare Stripe, Adyen, and PayPal SLA credits", or "Which security vendors offer automatic credits?"

Run from source

npm install
npm run build
node dist/index.js     # stdio server

Point it at a different API base with SLA_API_BASE (defaults to https://sla.directory/api/v1).

License

MIT. SLA data served by the API is licensed CC-BY-4.0 by SLA.directory. Always confirm against the vendor's official SLA before relying on this data for contractual or financial decisions.

Available Tools

6 tools
compare_vendorsCompare vendorsA
Read-only

Compare key SLA terms across several vendors (uptime, max credit, claim window, automatic credits, service count), each with its source.

Inputs: vendors (required).

get_service_slaGet per-service SLAA
Read-only

Get per-service SLAs for a vendor (many platforms publish a separate SLA per service). Optionally filter to one service by name.

Inputs: vendor (required), service.

get_vendorGet vendor SLAA
Read-only

Get a vendor's SLA (uptime, credit policy, claim process, per-service SLAs). Accepts a slug or a vendor name (fuzzy). Returns a cited summary by default; pass format:'raw' for the full record.

Inputs: vendor (required), format.

list_categoriesList categoriesA
Read-only

List all SLA.directory categories with vendor counts.

Inputs: no named parameters.

search_vendorsSearch vendorsA
Read-only

Search SLA.directory for vendors and services by name or category (e.g. 'datadog', 'storage', 'payments'). Returns slugs to look up.

Inputs: query (required).

vendors_in_categoryVendors in categoryA
Read-only

List vendor summaries in a category (use list_categories for the slug, e.g. 'finance-and-payments').

Inputs: category (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: comparing vendors, fetching per-service SLAs, retrieving vendor details, listing categories, searching, and listing vendors by category. There is no overlap in functionality.

    Naming Consistency4/5

    Most tools use a verb_noun pattern (compare_vendors, get_service_sla, get_vendor, list_categories, search_vendors). However, 'vendors_in_category' uses a noun_preposition_noun structure, breaking the pattern slightly.

    Tool Count5/5

    With 6 tools, the set is well-scoped for an SLA directory. It covers essential operations without being too numerous or too few, providing a focused interface.

    Completeness5/5

    The tools cover searching, browsing by category, retrieving vendor details, per-service SLAs, and cross-vendor comparison. This represents a comprehensive read-only surface for the domain, with no obvious gaps.

    Related MCP Connectors

    Related MCP Servers