
Daemoon
io.github.jaylee7777Published by GitHub account jaylee7777v1.2.0Updated Oct 24, 2026
One PAT, any MCP agent: Vercel, GitHub, Cloudflare, Supabase, GCP — unified dev infra gateway.
Overview
Daemoon is a remote MCP gateway that gives an AI coding agent one token to reach Vercel, GitHub, Cloudflare, Supabase, GCP and other dev infrastructure.
- What you can do
- List and manage Vercel projects and create deployments, and list or create GitHub repositories and branches through one gateway token. Inspect Supabase projects and run SQL, and list Cloudflare zones or create DNS records. List Google Cloud projects and services. Work with Stripe products, customers and payment links, send email through Resend, and call OpenAI and Anthropic models. Check npm identity, packages and package details.
- When to use it
- Useful when an AI coding agent needs to deploy, create repos or tables, change DNS, or query cloud projects across several providers without pasting a separate token into each config file. Best for developers who already use Claude Code, Cursor or another MCP client and want one sign-in and one token for all connected infrastructure.
- Requirements
- A remote MCP endpoint reached over Streamable HTTP or OAuth 2.0. A Daemoon account signed in through Google or magic link, each provider connected once in the browser, and a Daemoon PAT sent in the Authorization header. Provider-side credentials such as Cloudflare PATs, a GCP service account JSON, or Stripe and npm keys are supplied when connecting each provider.
Installation
In SourceWeft
- Open Daemoon in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.jaylee7777%2Fdaemoon/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"daemoon": {
"type": "http",
"url": "https://daemoon.dev/api/mcp"
}
}
}README
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.
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:
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
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:
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.
Source: README.md at commit 1508451
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts