Skip to main content
Glama
440,667 tools. Updated 2026-08-11 01:45

"Prisma" matching MCP tools:

  • check_package

    Zephex

    Check a public registry package before install or version bump — frameworks (next, react, vite), payments (stripe), auth (next-auth, clerk), ORMs (prisma, drizzle). task=check: exists, slopsquat, deprecation, CVEs (pass version); task=upgrade|migrate: breaking_changes + migration_steps from release notes; task=security: CVEs for your version. Returns summary, data, next_calls, meta.credits (5 hosted). No project path — just package name + version. Call BEFORE npm install or bumping next/stripe/prisma. NOT for repo layout (get_project_context), import search (find_code), tests (check_test), architecture (explain_architecture), live URLs (audit_headers). Example: check_package({ package: 'next', task: 'upgrade', from_version: '14.2.0' }). Read-only.
    Connector

  • zaira_compare_tools

    Zaira Labs Guide

    Compare 2-3 developer tools side by side. Returns each tool's full Markdown-KV entry separated by "===". Alternatives and worksWith are enriched with tagline + agent-readiness for resolved slugs. If any requested slugs are not found, they appear in a trailing "Note: slugs not found: ..." line; the comparison still returns for the ones found. Examples: - Three search engines: {slugs: ["meilisearch-oss", "algolia", "elasticsearch-oss"]} - Two ORMs: {slugs: ["drizzle-orm", "prisma"]} - Three auth providers: {slugs: ["auth0", "clerk", "keycloak"]} - Hosted vs self-hosted for the same vendor: {slugs: ["redis-cloud", "redis-oss"]} — shows deployment trade-off - Postgres engine vs hosted offerings: {slugs: ["postgresql", "supabase-cloud", "cockroachdb-cloud"]} Edge cases: - Cross-category comparisons (e.g., {slugs: ["auth0", "redis-cloud"]}) are allowed but rarely useful. Same-category comparisons answer "which should I pick?" better; cross-category answers "these coexist in my stack" — a compatibility question. - Minimum 2 slugs, maximum 3. Four or more is a validation error; for more, run pairs. - Invalid or unknown slugs are listed under "slugs not found"; the partial comparison returns for valid ones. - Duplicate slugs in the array are deduplicated. - A few tools are single entries (no -cloud/-oss split): stripe, auth0, firebase, twilio, openai-api, pinecone, algolia. Don't pass "stripe-cloud" — it doesn't exist. Risk: read-only, closed-world, idempotent — no state change possible.
    Connector

  • list_packages

    @imqueue

    The complete, authoritative catalogue of documented @imqueue packages, each with a one-line summary and its exact install command. Call this BEFORE adding any @imqueue dependency: search_docs can only find a package you already suspect exists, and this is the list. Covers typed RPC over a message queue, the Redis queue engine, the `imq` CLI, jobs and scheduling, Prisma and Sequelize database toolkits, method caching, tag-invalidated caching, PostgreSQL LISTEN/NOTIFY, Zod validation, OpenTelemetry or Datadog tracing, async logging, GraphQL N+1 batching across services, CIDR/IP checks and HTTP rate limiting. Some pairs are mutually exclusive — pg-prisma vs pg-sequelize, opentelemetry vs datadog — and installing both of a pair breaks silently, so read the `pick` rule on those entries before choosing.
    Connector

  • search_docs

    @imqueue

    Search the official @imqueue docs (guides, tutorial, CLI manual, articles) and every exported symbol of every @imqueue package that publishes a generated API reference, returning the most relevant pages with their URLs. Each result names the package it belongs to. Takes a plain question or an exact symbol name such as 'RedisQueue.send', 'PgPubSub.listen' or 'watcherCheckDelay'. Answers 'how do I do X in @imqueue' and confirms a signature before code is written against it. Every result carries the page URL, which get_doc reads in full. Some capabilities are covered by two mutually exclusive packages — @imqueue/pg-prisma vs @imqueue/pg-sequelize, @imqueue/opentelemetry vs @imqueue/datadog — so for a query like 'tracing' or 'database', call list_packages for the choosing rule rather than taking whichever package ranks first, and pass `package` here to search within the one you settled on.
    Connector

  • wallet_helper

    Prism — Data Enrichment for AI Agents

    Return step-by-step instructions for setting up x402 USDC autopay for this MCP server. Use this if a paid tool returned a 402 error or you're onboarding a new agent that needs to pay for API calls. Free.
    Connector

Matching MCP Servers

  • Prisma MCP Server by prisma

    Prisma MCP Serverofficial

    prisma
    F
    license
    -
    quality
    D
    maintenance
    Enables AI agents to manage Prisma Postgres databases and database workflows, including creating databases, running migrations, executing SQL queries, and managing backups, through natural language.
    47

Matching MCP Connectors

  • mcpOAuth

    MCP server for managing Prisma Postgres.

  • phi-longevity-prism

    Analyze biomarker panels with an MD-led clinical engine. Guideline-cited. Synthetic data only.

  • full_prism_report

    phi-longevity-prism

    PAID TOOL ($4.99 USDC on base via the x402 protocol). Everything analyze_biomarkers does, plus: multi-track compare/contrast analysis (up to 4 condition tracks), a panel-based Phi Score estimate with per-pillar breakdown, partner options, and a rendered report (markdown) to deliver to your owner. Call WITHOUT `payment` to receive x402 payment terms; pay; retry with the base64 payment payload in `payment`. For research/education with SYNTHETIC or de-identified data only. Do NOT submit protected health information (PHI). This endpoint is stateless and does not store inputs.
    Connector

  • import_schema

    SeedBase Test Data

    Import a database schema into a project from pasted content: SQL DDL (CREATE TABLE …, raw pg_dump/mysqldump schema output works), SQL INSERT dumps, CSV/TSV, JSON, or ORM model code (Django, Prisma, SQLAlchemy, …). Replaces the project's current schema.
    Connector

  • analyze_biomarkers

    phi-longevity-prism

    Analyze a SYNTHETIC biomarker panel with Phi Longevity's PRISM engine. Returns tiered, guideline-cited recommendations. For research/education with SYNTHETIC or de-identified data only. Do NOT submit protected health information (PHI). This endpoint is stateless and does not store inputs.
    Connector