# daemoon [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/daemoon-dev/daemoon  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/daemoon

## Description
One PAT, any MCP agent: Vercel, GitHub, Cloudflare, Supabase, GCP — unified dev infra gateway.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "daemoon": {
    "url": "https://daemoon.dev/api/mcp"
  }
}
```

## Documentation

## What the daemoon MCP server does

The daemoon MCP server acts as a shared gateway between MCP clients and multiple development and infrastructure services. After providers are connected through the Daemoon dashboard, an agent can call provider-specific tools through one MCP endpoint and one bearer token.

Supported connected providers include Vercel, GitHub, Supabase, Cloudflare, Google Cloud, Stripe, Resend, OpenAI, Anthropic, and npm. Example operations include listing Vercel projects, creating deployments, listing GitHub repositories, running Supabase SQL, creating Cloudflare DNS records, listing Google Cloud services, creating Stripe payment links, sending Resend email, listing OpenAI models, creating Anthropic messages, and viewing npm package information.

## How it works

The hosted endpoint is `https://daemoon.dev/api/mcp`. It uses MCP Streamable HTTP with protocol version `2025-06-18` and exposes JSON-RPC `tools/list` and `tools/call` operations. Clients authenticate with an `Authorization: Bearer dmn_...` header after a token is generated in the Daemoon dashboard.

Daemoon handles provider authentication separately. OAuth 2.0 with dynamic client registration and PKCE is also available for clients that prefer that flow.

## Setup and configuration

Generate an MCP token at `daemoon.dev/dashboard`, then add an HTTP MCP server to the client using the endpoint and bearer header. Claude Code can register it with `claude mcp add --transport http`; Cursor provides an HTTP option under its MCP settings. Cline, Continue, Zed, and other MCP clients can use the same endpoint configuration.

Daemoon can also be self-hosted. The documented development flow clones the repository, copies `.env.local.example` to `.env.local`, adds Supabase and provider OAuth credentials, installs npm dependencies, and runs `npm run dev`. The database schema is provided in `sql/0001_init.sql`.

## Tools and capabilities

Tool names are grouped by provider. Examples documented in the README include:

- `vercel.list_projects` and `vercel.create_deployment`
- `github.list_repos` and `github.create_repo`
- `supabase.list_projects` and `supabase.run_sql`
- `cloudflare.list_zones` and `cloudflare.create_dns_record`
- `gcp.list_projects` and `gcp.list_services`
- `stripe.list_products`, `stripe.list_customers`, and `stripe.create_payment_link`
- `resend.send_email` and `resend.list_domains`
- `openai.list_models` and `openai.chat_completion`
- `anthropic.create_message`
- `npm.whoami`, `npm.list_packages`, and `npm.view`

The connector interface lets each provider define its authentication validation and tool definitions. Provider credentials remain in the Daemoon vault, and the project documents envelope encryption using per-token data-encryption keys, a master key, and AES-256-GCM. Provider connections and agent tokens can be revoked separately.

## Limitations and notes

The hosted service requires a generated Daemoon token and a client that can connect over HTTP MCP. Provider access depends on configuring the relevant provider credentials and permissions.

The repository is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/daemoon/readme_