Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/netlify/context-and-toolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/netlify/context-and-tools/netlify-mcp-servers-connecting-clients)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-mcp-servers-connecting-clients"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-mcp-servers-connecting-clients/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-mcp-servers-connecting-clients"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-mcp-servers-connecting-clients.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00875 |
| Opus 5 | $0.00007 | $0.00438 |
| Sonnet 5 | $0.00003 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
netlify-mcp-servers-connecting-clients scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connecting Clients
Your server is a remote HTTP endpoint (https://<site>.netlify.app/mcp). Modern clients connect to it natively over Streamable HTTP. The mcp-remote bridge — which most older tutorials lead with — is now a fallback, not the default. Its own README says to drop it once your client supports remote servers.
Native connection (preferred)
Claude Code — native Streamable HTTP, custom headers supported:
claude mcp add --transport http my-mcp https://<site>.netlify.app/mcp \
--header "Authorization: Bearer <token>"
Cursor — native Streamable HTTP. Add to mcp.json:
{
"mcpServers": {
"my-mcp": {
"url": "https://<site>.netlify.app/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Claude Desktop / claude.ai — add a Custom Connector (Settings → Connectors → Add). Connectors are built around OAuth (see below). For a server that authenticates with a static bearer token rather than OAuth, the connector UI may not give you a place to set that header — in that case use the mcp-remote fallback for Desktop.
mcp-remote fallback
For clients that only speak stdio, or can't set headers natively, mcp-remote bridges a local stdio MCP server to your remote HTTP one:
{
"mcpServers": {
"my-mcp": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://<site>.netlify.app/mcp",
"--header", "Authorization: Bearer <token>"
]
}
}
}
The bearer token sits in plaintext in this config file — treat it like any other on-disk secret, and revoke + reissue if it leaks.
Local testing with the MCP Inspector
Before wiring up a real client, exercise the server directly:
npx @modelcontextprotocol/inspector
Connect via Streamable HTTP to http://localhost:8888/mcp (under netlify dev) or your deployed URL, add an Authorization: Bearer <token> header, and confirm tools list and call. This isolates "is my server correct?" from "is my client configured right?".
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 81 lines · 14 tokens per session scan A 114391e42aed
netlify-mcp-servers-connecting-clients is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 875 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.