streamable-httpMITupdated 2mo ago
One login. Every infrastructure. Built for AI coding agents.
What can you do with daemoon?
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
Install
Generate your token once at daemoon.dev/dashboard, then point your agent at https://daemoon.dev/api/mcp with header Authorization: Bearer dmn_....
Claude Code
Paste this in the Claude Code chat β Claude runs the install:
Install the Daemoon MCP server for me by running:
claude mcp add --transport http daemoon https://daemoon.dev/api/mcp --header "Authorization: Bearer dmn_..."
Cursor
Settings β MCP β Add server β HTTP:
- URL:
https://daemoon.dev/api/mcp - Headers:
Authorization: Bearer dmn_...
Cline / Continue / Zed / any MCP client
Add an HTTP MCP server pointing at https://daemoon.dev/api/mcp with the bearer token header. Supports MCP Streamable HTTP (protocol 2025-06-18) and OAuth 2.0 (DCR + PKCE) for clients that prefer it.
Machine-readable
https://daemoon.dev/.well-known/mcp.jsonβ server cardhttps://daemoon.dev/llms.txtβ agent-readable summaryhttps://daemoon.dev/.well-known/oauth-protected-resourceβ RFC 9728https://daemoon.dev/.well-known/oauth-authorization-serverβ RFC 8414
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 |
| Stripe | PAT (Secret key) | stripe.list_products, stripe.list_customers, stripe.create_payment_link |
| Resend | PAT | resend.send_email, resend.list_domains |
| OpenAI | PAT | openai.list_models, openai.chat_completion |
| Anthropic | PAT | anthropic.create_message |
| npm | PAT (Automation / Granular) | npm.whoami, npm.list_packages, npm.view |
More providers (Linear Β· Sentry Β· PostHog Β· Neon Β· Upstash Β· β¦) 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 (
icn1region). - Supabase for auth (Google + magic link) + Postgres vault.
- MCP HTTP transport at
/api/mcpβ JSON-RPCtools/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-mcpfor stdio MCP clients
License
MIT. See LICENSE.
Install
Add daemoon to your client. Pick the one you use.
claude mcp add --transport http daemoon https://daemoon.dev/api/mcpcodex mcp add daemoon --url https://daemoon.dev/api/mcp{
"mcpServers": {
"daemoon": {
"url": "https://daemoon.dev/api/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"daemoon": {
"type": "http",
"url": "https://daemoon.dev/api/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"daemoon": {
"url": "https://daemoon.dev/api/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"daemoon": {
"serverUrl": "https://daemoon.dev/api/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance22/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 72 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint β no local install
Version history
| Versions | Published |
|---|---|
| 1.2.0Latest | Jun 18, 2026 |
| 1.1.0 | Jun 18, 2026 |
| 0.9.4 | Jun 18, 2026 |