multi-account-netlify-mcp
Related Servers
Alternatives to multi-account-netlify-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code and Codex to work with multiple accounts of the same MCP server at once, such as two Gmail inboxes or several Slack and Notion workspaces. It presents a single toolset where every tool takes a required account argument, with per-account OAuth sign-in and credentials isolated in the macOS Keychain.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a single local MCP endpoint that connects Gmail, GitHub, Slack, Notion, and Linear once, with multiple accounts per service, so any AI agent can use per-agent tokens, policies, and optional result filtering without re-authenticating.1 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables coding-agent clients to use one local MCP endpoint that routes calls to isolated per-account workers, shares a single tool surface across sessions, and applies per-account policies and key pools.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to connect once to a local MCP endpoint and access tools from all configured MCP servers, add or remove connectors live, and generate sandboxed connectors for services that lack one. It centralizes multi-server access while keeping credentials isolated and calls logged without recording arguments or results.MIT
- AlicenseAqualityAmaintenanceLocal, open-source multi-account MCP broker — one endpoint, every account. Add credentials once and switch identity without reconnecting, from any LLM client.59MIT
- AlicenseNot gradedqualityCmaintenanceRuns each MCP server once and lets any number of AI agents connect over HTTP with their own keys, per-tool grants and audit logging, plus a shared task list, shared memory and agent-to-agent requests. Enables agents to work as a coordinated team without duplicating processes, credentials or work.4 npmMIT
TDQS
Scored across 10 tools
Each tool is scoped to a distinct Netlify domain (user, deploy, team, project, extension, observability) and cleanly split into read vs. write, so boundaries are clear. The only ambiguity is that each tool multiplexes many sub-operations internally, and netlify-coding-rules overlaps thematically with everything as a pre-step advisory tool.
Tools follow a strong, predictable pattern: netlify-<domain>-services-<reader|updater>, which makes read vs. write obvious at a glance. The lone outlier is netlify-coding-rules, which breaks the pattern but is clearly a different kind of tool.
Ten tools is well-scoped for a multi-domain Netlify server, and the dispatcher pattern lets each tool cover several operations without surface bloat. No tool feels redundant or padded.
Read coverage is thorough across user, deploy, team, project, extension, and observability, and core writes exist (deploy-site, create-new-project, manage-env-vars, forms, extension install change). Notable gaps remain, including team/member management writes, project or site deletion, and DNS management, but agents can work around most of these.