DreamFactory MCP

Created By
dreamfactorysoftwarea year ago
DreamFactory MCP Server enables AI assistants like Claude to directly query your databases through DreamFactory's auto-generated REST APIs.
Overview

what is DreamFactory MCP?

DreamFactory MCP is a Model Context Protocol server that enables AI assistants like Claude to directly query databases through auto-generated REST APIs.

how to use DreamFactory MCP?

To use DreamFactory MCP, clone the repository, install dependencies, build the project, and configure it within the Claude Desktop application to enable the server.

key features of DreamFactory MCP?

  • Integration with AI assistants for database queries
  • Auto-generated REST APIs for seamless data access
  • Easy setup and configuration for developers

use cases of DreamFactory MCP?

  1. Enabling AI assistants to fetch and manipulate data from databases.
  2. Streamlining data access for applications using AI technologies.
  3. Facilitating rapid development of AI-driven applications.

FAQ from DreamFactory MCP?

  • What is the purpose of DreamFactory MCP?

It allows AI assistants to interact with databases using REST APIs, enhancing their capabilities.

  • Is DreamFactory MCP easy to set up?

Yes! The setup process is straightforward, with clear instructions provided in the documentation.

  • Can I use DreamFactory MCP with any database?

Yes, as long as the database is supported by DreamFactory, you can integrate it with the MCP.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dreamfactorysoftware
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

32 minutes ago