Skip to main content
Glama

Daemoon

One login. Every infrastructure. Built for AI coding agents.

daemoon.dev · MCP server · Vercel · GitHub · Cloudflare · Supabase · GCP


Daemoon is the simplest way to give your AI coding agent (Claude Code, Cursor, etc.) access to all your dev infrastructure. Connect each provider once in your browser, then any agent gets unified, secure tool access via a single MCP token.

Why

You're prototyping with Claude Code. The agent wants to deploy a Vercel project, create a Supabase table, push a GitHub branch. Today you paste five different tokens into five different config files — and every new agent / repo / teammate starts over.

Daemoon ends that. One sign-in connects everything. One token wires the agent.

[You]                                    [Daemoon]                   [Providers]
  │                                          │                            │
  ├── Sign in once (Google) ─────────────────▶                            │
  ├── Connect Vercel · GitHub · CF · Supabase ▶─── OAuth · PAT ───────────▶
  ├── Generate MCP token ────────────────────▶                            │
  │                                          │                            │
  ▼                                          ▼                            ▼
 Claude Code / Cursor / any MCP client ⇄ /api/mcp ⇄ vault ⇄ live provider APIs

Related MCP server: clavis-mcp-server

Install

Generate your token at daemoon.dev/dashboard, then paste this into your Claude Code chat:

Install the Daemoon MCP server for me by running:
claude mcp add --transport http daemoon https://daemoon.dev/api/mcp --header "Authorization: Bearer dmn_..."

Claude runs the install. Done.

Connected providers

Provider

Auth

Sample tools

Vercel

OAuth (1-click)

vercel.list_projects, vercel.create_deployment

GitHub

OAuth (1-click)

github.list_repos, github.create_repo

Supabase

OAuth + PAT

supabase.list_projects, supabase.run_sql

Cloudflare

PAT

cloudflare.list_zones, cloudflare.create_dns_record

Google Cloud

Service Account JSON

gcp.list_projects, gcp.list_services

More providers (Stripe · Resend · Linear · …) on the roadmap. PRs welcome.

How it's secure

  • Envelope encryption — every provider token is wrapped with a per-token DEK, then by a master key. AES-256-GCM end to end.

  • No raw secrets in your repo, no env vars to leak. Tokens live in the Daemoon vault; the agent never sees them, only the responses.

  • Revoke any token in one click. Per-provider disconnect, per-agent PAT revoke.

Self-host

Daemoon is open-source. Clone, set env vars, deploy to your own Vercel:

git clone https://github.com/daemoon-dev/daemoon
cd daemoon
cp .env.local.example .env.local   # add your Supabase + provider OAuth creds
npm install
npm run dev

Schema in sql/0001_init.sql.

Architecture

  • Next.js 15 App Router on Vercel (icn1 region).

  • Supabase for auth (Google + magic link) + Postgres vault.

  • MCP HTTP transport at /api/mcp — JSON-RPC tools/list + tools/call.

  • Connector interface in lib/connectors/types.ts: every provider implements OAuth / PAT validation + a list of tool defs. Adding a provider is one file.

Roadmap

  • More connectors: Stripe, Resend, Linear, Notion, Plausible

  • 1-click GitHub OAuth verified app (currently in Google Cloud "Testing" mode)

  • Service Account JSON → OAuth for GCP (when verified)

  • npm shim daemoon-mcp for stdio MCP clients

License

MIT. See LICENSE.

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daemoon-dev/daemoon'

If you have feedback or need assistance with the MCP directory API, please join our Discord server