A side-by-side look at the AllMCPs Server and Nable MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AllMCPs Server for aggregators work over a hosted endpoint; choose Nable for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
ALLMCPS_MCP_URL.search_mcp_servers, get_mcp_install_config, recommend_mcp_stack.connect_aws, connect_azure, get_cost_summary.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Cloud Platforms |
| Quality signal | 85/100 · Excellent | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ALLMCPS_MCP_URL | None listed |
| Verified owner |
search_mcp_serversSearch the AllMCPs directory for Model Context Protocol (MCP) servers by keyword or category.get_mcp_install_configGet the exact claude_desktop_config.json setup snippet and documentation for a specific MCP server by ID.recommend_mcp_stackRecommend a curated multi-tool MCP server stack for a specific developer role or workflow (e.g. "fullstack", "data science", "devops").list_mcp_categoriesList all categories available in the AllMCPs directory along with server counts.get_boost_pricingGet pricing and features for boosting / featuring an MCP server on AllMCPs.com.boost_mcp_serverInitiate a sponsorship / boost order for an MCP server by ID, returning a Stripe checkout session URL and x402 invoice.get_boost_statusCheck current boost status, verified badge level, and sponsorship expiration for an MCP server by ID.submit_mcp_serverProgrammatically submit a new MCP server repository to AllMCPs.com for indexing and review. Supports the same optional enrichment fields as the human submission form — fill in whichever you can confidently determine from the repository (README, package.json, code) to produce a fully flushed-out listing. Omit anything you are not confident about rather than guessing; all enrichment fields are optional and unrecognized enum values are simply dropped, not rejected.verify_mcp_claimVerify ownership and claim an MCP server listing by checking GitHub README badge, website badge, or DNS TXT record. Works two ways: (1) fully unattended — pass `agentToken` from confirm_mcp_agent (or set an `Authorization: Bearer <token>` header if your client supports it), no human sign-in needed; or (2) if called with neither, requires the caller to already have an active AllMCPs browser session. Unattended agents should use register_mcp_agent + confirm_mcp_agent first.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"allmcps-server": {
"command": "npx",
"args": [
"-y",
"allmcps-server"
],
"env": {
"ALLMCPS_MCP_URL": "YOUR_ALLMCPS_MCP_URL_HERE"
}
}
}
}
{
"mcpServers": {
"nable": {
"command": "uvx",
"args": [
"nable"
]
}
}
}
| Community listing |
| GitHub stars | 4 | 19 |
|---|
| Directory activity | 59 views 20 installs 1 upvotes | 1 views 0 installs 0 upvotes |
|---|
| Tools | 11 | 10 |
|---|
| Full listing | View AllMCPs Server | View Nable |
|---|
register_mcp_agentconfirm_mcp_agentExchange the 6-digit code emailed by register_mcp_agent for a durable bearer token (90-day TTL). Pass the returned token as `agentToken` on verify_mcp_claim, or set it as an `Authorization: Bearer <token>` header on subsequent MCP requests if your client supports that.connect_awsConnect an AWS account from inside your MCP client, no terminal needed.
Propose-then-confirm and local-only. It reads AWS credentials that already
exist on this machine (named profiles, environment, the default chain),
verifies each against STS, and connects the one you choose. It never creates,
modifies, or deletes anything in your AWS account, and credentials stay on
this machine.
Call it with no arguments first to see which accounts are available (nothing
is stored). Then call it again with account_id set to the one to connect.
Examples:
- "Connect my AWS account"
- "Use the credentials on this machine to connect AWS"connect_azureGuide connecting Azure while keeping the service-principal secret off the model.
Azure has no local credentials nable can safely auto-detect, so connecting
needs a client secret. Unlike connect_aws and connect_gcp (which read
credentials already on the machine, so nothing sensitive passes through this
conversation), an Azure secret would have to be pasted into the chat to reach
a tool argument, which routes it through the model provider. nable does not do
that. This tool returns the Cloud Shell script and has you finish the connect
in your OWN terminal with `finops setup azure`, which encrypts the secret into
your local vault. The model never sees the secret.
Examples:
- "Connect Azure"
- "How do I connect my Azure subscription?"get_cost_summaryGet total spend summarized by service, account, and region.
Examples:
- "How much did we spend last month?"
- "Give me an AWS cost summary for January"estimate_change_costCost preflight for a proposed change: what it costs and whether it fits budget.
Agent-native. Call this BEFORE applying an infrastructure change to get a machine
verdict (ok / warn / over_budget / no_budget) plus the monthly and annual cost
delta and the budget headroom. Read-only: it estimates and checks, it never applies
anything.
Describe the change one of these ways:
- terraform_plan_json / terraform_plan_file / tf_dir : a Terraform plan
- helm_diff : output of `helm diff upgrade` or a values.yaml diff
- monthly_delta_usd : a known monthly cost delta (escape hatch for any change the
estimators don't parse, e.g. "launch a db.r6g.4xlarge")
budget_name selects which budget to check against; default is the first active
budget. With no budget configured the verdict is "no_budget" and the cost delta is
still returned.
Good triggers: "will this fit my budget", "what will this terraform/helm change cost
before I apply it", "cost preflight", "can the agent afford this change".
Examples:
- "What would this change cost per month?"
- "Preflight the cost of this terraform plan"connect_gcpConnect a Google Cloud billing account from inside your MCP client, no terminal.
Propose-then-confirm and local-only. It reads Google Cloud credentials that
already exist on this machine (GOOGLE_APPLICATION_CREDENTIALS or gcloud
Application Default Credentials), lists the open billing accounts they can
see, and connects the one you choose. It never changes anything in GCP, and
credentials stay on this machine.
Call it with no arguments to see the billing accounts available (nothing is
stored). Then call it again with billing_account_id set to connect one.
Examples:
- "Connect my Google Cloud billing"
- "Use my gcloud login to connect GCP"list_connected_providersList every cloud, SaaS, and LLM provider nable knows, each marked connected or
not-configured, plus the active plan. The starting point for "what am I
connected to" and for spotting which connector still needs credentials
(each not-configured entry names the setup command to run).
Examples:
- "Which providers are connected?"
- "Is GCP set up yet?"check_ai_budgetAdvisory gate: before a big task, is the agent about to blow its AI budget?
Call this before an expensive run. Returns a verdict (ok / warn / over), the
reason, and a recommendation. Advice only, it never blocks; relay the verdict and
let the human decide. Pass estimated_next_tokens to test whether the next task
would tip a token budget over.check_action_policyAdvisory policy gate: should a proposed remediation action proceed?
The request-path guardrail, advisory. Describe a remediation action you are
considering (action_type), optionally with the change to cost (a Terraform plan,
a helm diff, or a known monthly delta), and nable returns a machine verdict
against your human-authored policy:
- allow: reversible, allowlisted, and within budget. A human can apply it.
- escalate: a one-way door (delete, terminate, buy a commitment) or an
over-budget / large-cost change. A human must review it first.
- block: the action type is not in your allowlist.
ADVICE ONLY. nable never applies the action, a human does. This is the
propose-only guardrail; nable does not auto-execute anything.
action_type examples: rightsizing, tag_fix, stop_idle, spot_migration, ticket
(reversible); idle_cleanup, purchase_commitment, terminate_instance, delete_resource
(one-way). Policy knobs via env: FINOPS_POLICY_MAX_AUTO_USD,
FINOPS_POLICY_ALLOWED_ACTIONS (comma-separated). Read-only.
Good triggers: "can the agent do X", "is this action within policy", "should I
apply this fix", "is it safe to auto-apply this".
Examples:
- "Is this apply within policy?"
- "Check this change against our cost guardrails"what_can_nable_doShow everything nable can do, tailored to what you've connected.
Call this when the user asks "what can you do?", "what features do you have?",
"what should I try first?", "show me what's available", or "help". Always call
it right after a user connects their first account, so they see what just
became possible. Pass detailed=True to also list the underlying tool names.
Examples:
- "What can nable do?"
- "List your capabilities"nable_setup_statusAgent-driven onboarding: what is connected, what credentials are already on
this machine, and the exact command to connect each remaining provider.
Call this when the user asks to connect a provider, says setup is incomplete,
or asks what they are missing. Detected ambient credentials (gcloud login,
env keys, ~/.modal.toml) mean the connect is ONE terminal command with no
secrets involved; run it for the user or hand them the command.
Rules for the agent, and they are hard rules:
- NEVER ask the user to paste an API key or secret into the chat. For
paste-a-key providers, have them run the setup command in their own
terminal; it deep-links the key page and stores the key locally.
- Prefer the zero-secret paths: `finops connect` (batch-connects everything
detected) and `finops setup gcp` / ambient AWS, where no secret ever
passes through the conversation.
Examples:
- "Connect my GCP costs"
- "What providers am I missing?"