Log inSubmit server
Daemoon logo

Daemoon

Connects AI coding agents to Vercel, GitHub, Cloudflare, Supabase, GCP, and other provider APIs through one MCP token.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Daemoon

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://daemoon.dev/api/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Use the daemoon MCP server to give an MCP-compatible coding agent access to connected infrastructure providers through one authenticated endpoint. It routes tool calls from `/api/mcp` to services including Vercel, GitHub, Cloudflare, Supabase, Google Cloud, Stripe, Resend, OpenAI, Anthropic, and npm. Provider credentials are connected in a browser and stored in Daemoon's vault, so agents receive API responses rather than raw secrets. Reach for it when one agent or team needs access to several provider APIs without maintaining separate credentials in each client configuration.

Use cases

  • Connect one coding agent to several infrastructure APIs
  • Deploy Vercel projects through an MCP client
  • Run Supabase SQL without placing database credentials in agent configuration
  • Manage GitHub repositories and Cloudflare DNS records from an agent
  • Self-host a multi-provider MCP gateway on Vercel

Key features

  • Unified MCP HTTP endpoint
  • Provider-specific infrastructure tools
  • Browser-based provider connection flow
  • Vault-based credential storage
  • Bearer-token authentication
  • Self-hosting support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 35d

How Daemoon works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Daemoon

daemoon is an MCP server that connects AI coding agents to services including Vercel, GitHub, Cloudflare, Supabase, Google Cloud, Stripe, Resend, OpenAI, Anthropic, and npm. Its main tools cover deployments, repositories, SQL, DNS, cloud resources, payments, email, model access, messages, and package information.

Generate a token at the Daemoon dashboard, then configure an HTTP MCP server at `https://daemoon.dev/api/mcp` with an `Authorization: Bearer dmn_...` header. Claude Code can use the documented `claude mcp add --transport http` command.

Yes, daemoon works with Cursor through its HTTP MCP configuration. In Cursor, add a server under Settings, MCP, and Add server, then enter the Daemoon endpoint and bearer-token header.

Daemoon supports Vercel, GitHub, Supabase, Cloudflare, Google Cloud, Stripe, Resend, OpenAI, Anthropic, and npm according to the connected-providers list. Other providers, including Linear, Sentry, PostHog, Neon, and Upstash, are described as roadmap items.

Yes, the project documents self-hosting on Vercel. Clone the repository, create `.env.local` from the example file, add Supabase and provider OAuth credentials, install dependencies, and run `npm run dev`.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDaemoon AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/daemoon?style=directory)](https://allmcps.com/mcp/daemoon)
HTML Embed
<a href="https://allmcps.com/mcp/daemoon"><img src="https://allmcps.com/api/badge/daemoon?style=directory" alt="Daemoon on AllMCPs" /></a>