Cloudflare AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Cloudflare AI AI

Anthropic just bought the company that generates most production MCP servers

Anthropic acquired Stainless on Monday for a reported $300M+. Most coverage is framing this as a developer tools acquisition. Stainless is best known for generating the official Python and Node SDKs that ship with OpenAI, Google, Meta, Cloudflare, and Anthropic. The SDK story is real. The MCP side is the part that matters here. Stainless was one of the first vendors to extend their compiler to produce MCP servers from the same OpenAPI specs that produce their SDKs. MCP hit ~97M monthly SDK downloads by December 2025 and around 10,000 production servers by early 2026. A lot of that production code was Stainless-generated. Anthropic now owns the dominant MCP server generator. What actually changed hands on Monday: The engineering team. Roughly 40-50 people including founder Alex Rattray, who previously built Stripe's patented SDK generation system. Now reporting to Katelyn Lesse in Anthropic's Platform Engineering org. The technology. The generator, the templates, the language-specific runtimes, the OpenAPI extensions Stainless invented for SDK-specific edge cases. The hosted product is winding down. New signups stopped Monday. New SDK and MCP server generations stopped Monday. Existing customers keep what they've already generated but the pipeline is closed. My read: this is closer to what Google did with Kubernetes than to a normal acquisition. Anthropic created MCP. Anthropic donated MCP to the Linux Foundation last December. Anthropic now owns the dominant implementation toolchain. The protocol is vendor-neutral on paper. The implementation toolchain isn't. Six months of Anthropic M&A starts looking less coincidental: December 2025: Bun, the JS runtime, pulled into Claude Code February 2026: Vercept, computer-use AI April 2026: Coefficient Bio, ~$400M healthcare AI May 2026: Stainless, SDK and MCP plumbing They're not buying training infrastructure or GPU clusters. They're buying the integration layers around the model. The bet seems to be that frontier models are converging faster than anyone expected, so the moat is everywhere except the model. If you're building on MCP today, tooling quality probably improves. Stainless's generator was already the cleanest in the space and the team that built it is now at Anthropic. Patterns will standardize faster as Stainless-derived templates become the de facto reference. The flip side is concentration risk. Cloudflare's MCP server framework, Pulse MCP, and the open-source generators Stainless released during the transition all become strategically important if you want any diversity in your stack. Sources: Anthropic announcement Why Anthropic actually did this, and migration math Curious whether Stainless ending up inside Anthropic reads as good news (better tooling) or concentration risk (one company owns the standard and the reference implementation) from your seat. submitted by /u/Ok-Constant6488 [link] [comments]

built a CLI for ChatGPT so I could script it from the terminal

wanted to ask ChatGPT questions and generate images from shell scripts without using a third-party API key. so I built a CLI that wraps the same endpoints chatgpt.com uses, with browser-based OpenAI SSO for auth (Camoufox for the Cloudflare check). what it does: chat ask "question" and pipe the answer wherever chat image "prompt" to generate, plus a download command list past conversations and models every command has a --json flag so it slots into agent pipelines. it's part of a bigger open-source project that auto-generates CLIs from any website's HTTP traffic, MIT licensed: https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/chatgpt I built it, not affiliated with OpenAI. uses the same endpoints the web app uses, so things can break when ChatGPT pushes changes. submitted by /u/zanditamar [link] [comments]

Why claude code doesn’t have SSH?

submitted by /u/Alternative-Way-3685 [link] [comments]

temporal-mcp: wall-clock awareness for LLMs, with OAuth

One of the small failure modes I keep hitting with agent stacks is that the model has no idea how much time passed between turns. It'll greet you with "good morning" at 11 PM, or pick up a conversation three weeks later as if no time has passed, or compute "today's data" off whatever fragment of context happens to be in scope. Built a minimal MCP server to fix it. Two tools: temporal_tick and temporal_peek. They return elapsed-time-since-last-turn, day-rollover detection, and a fresh-thread flag, both as a human-readable header and as JSON. Ways to use: Local stdio: pip install temporal-mcp (works with Claude Desktop, Cursor, Cline, Zed, Claude Code) Hosted with OAuth (claude.ai / ChatGPT): visit https://temporal-mcp.dev/connect, click "Generate OAuth Credentials", paste into your custom connector. Full OAuth 2.0 with PKCE and refresh tokens, but no signup, the credential pair is the identity. (Verified working in claude.ai) Hosted with raw bearer (any client that supports custom headers): Authorization: Bearer against https://temporal-mcp.dev/mcp. The token gets SHA-256'd; we never see the plaintext. Self-host: Cloudflare Workers deploy in workers/ in the repo, free tier covers ~100k req/day. Grok/xAI: https:temporal-mcp.dev/mcp/ (Verified working in Grok) MIT, ~150 lines of stdlib Python on the local side, ~400 lines of TypeScript on the hosted side (engine + OAuth provider), both with tests. Listed in the official MCP Registry. Smithery and Glama submissions in flight. Curious to hear how folks would use the JSON day_rollover and delta_sec signals I've been using them for context decay and resume detection but there are probably more interesting use cases. Source: github.com/MirrorEthic/temporal-mcp submitted by /u/MirrorEthic_Anchor [link] [comments]

PullMD v2.4.1 is out - claude.ai web custom connector works natively now, plus what 2 weeks of your feedback turned into

Two weeks ago I posted PullMD here. 385 upvotes, around 60 comments, a bit over 20 GitHub issues, and 7 releases (v1.1.3 → v2.4.0) in 14 days. That was a great experience - and this sub in particular has been a genuinely good place to share something. So: thanks! Quick refresher for anyone who missed the first post: PullMD turns any URL into clean Markdown via MCP, fully self-hosted. Three services in Docker (main app + Trafilatura sidecar + optional Playwright sidecar for JS-heavy pages), zero third-party LLM calls, ships an MCP server so Claude Code / Claude Desktop / claude.ai web can pull clean content directly instead of parsing HTML in your context window. This post is what's new and how to get it. What's new claude.ai web + Claude Desktop work natively now This is the biggest unlock from v2.x. The claude.ai web custom-connector dialog and Claude Desktop's custom-connector dialog now both work against self-hosted PullMD instances. So you can point claude.ai at your own homelab box, hit "Add custom connector," and it works end-to-end. Setup is two env vars: OAUTH_JWT_SECRET=$(openssl rand -hex 32) PUBLIC_URL=https://your-host.example.com Restart. Then in claude.ai web → Settings → Connectors → Add custom, point at https://your-host.example.com/mcp. The connector dialog discovers the server's metadata, registers itself, and walks you through a consent screen. Same flow works in Claude Desktop. Under the hood: standard OAuth 2.1 Authorization Code flow with PKCE-S256 and Dynamic Client Registration - RFC-compliant so any spec-compliant MCP client should work, not just claude.ai/Desktop. Opt-in: if OAUTH_JWT_SECRET isn't set, behavior is identical to v1.x. The Anthropic-side claude-ai-mcp#237 proxy bug I flagged in EDIT2 of post 1 has cleared on their end - though in hindsight, a forgotten custom WAF rule on my side was likely the actual culprit anyway. Verified end-to-end against both dialogs. Multi-user auth Until v2.0, PullMD was effectively single-tenant - a personal homelab tool, open like a barn door to anyone who landed on it. v2.0 adds three auth modes via PULLMD_AUTH_MODE: disabled - the default. Identical to v1.x. No login, no API key required. Right if you're the only one using your instance and you trust your network. single-admin - one user, password-protected, no self-signup. Right for a homelab box where you want the GUI gated but don't want to manage users. multi-user - self-signup at /signup, per-user history isolation, per-user API keys. Right for a shared instance (team, office, friend group). API keys are pmd_ , sent as Authorization: Bearer pmd_xxx, managed at /settings. Share links (/s/:id) stay public in all modes - the whole point of a share link is to be shareable. Minimal upgrade for a shared instance: PULLMD_AUTH_MODE=multi-user PULLMD_ADMIN_EMAIL=you@example.com PULLMD_ADMIN_PASSWORD=change-me-please PullMD works on more sites A bunch of things in v1.2 and v2.2 together close gaps where PullMD used to silently return half-articles, empty bodies, or garbled text: Future PLC family (windowscentral.com, tomshardware.com, techradar.com, pcgamer.com, gamesradar.com, t3.com) used to return mangled content because Readability got confused by recommendation widgets stuffed mid-article and an aria-hidden paywall pattern. The default site-recipes shipped with v2.2 strip both, no config needed. GitHub Issues pages used to return only the original issue body - the JS-rendered comment thread never made it in. The default recipe for */*/issues/* now forces Playwright with wait_for: .js-comment-body, so you get the full comment tree. Sites that fingerprinted the old hardcoded Chrome 131 UA now extract cleanly - UA rotation pulls from a real-world UA pool that updates regularly (v1.2). Pages with navigator.webdriver-style anti-bot detection go through more often - the headless-Chromium sidecar bundles playwright-stealth (v2.2). Sites without an explicit charset declaration (a lot of older German news sites, for example) no longer return mojibake - charset is detected from the byte stream when the response is silent (v1.2). If you have a specific site that still misbehaves, v2.2 lets you (or your Claude Code) write your own recipe - declarative JSON with four rule categories (preprocess, fetch, select, extractor). Drop it at data/site-recipes.json and your rules layer on top of the defaults. There's also a /api/recipes/status endpoint for monitoring. Web GUI: rendered Markdown view + persistent settings Two smaller improvements in the browser frontend (the PWA you get when you open your PullMD instance directly): Rendered Markdown toggle. The result header now has a Raw | Rendered switch, so you can read what you pulled as formatted HTML directly in the browser instead of squinting at the source. Raw stays the default; your choice persists across sessions (v2.4). Settings persist across reloads - frontmatter toggle, comments toggle, comment-depth input.

I built a self-hosted memory layer for Claude that runs free on Cloudflare — open source

https://preview.redd.it/touwnxi2z80h1.png?width=1774&format=png&auto=webp&s=b4bf6c2e1f096f692562a2b8b27e72dc2f9cb1c0 Claude forgetting everything between sessions was driving me crazy, so I built a fix. It's a Cloudflare Worker that acts as an MCP server — four tools: remember, recall, list_recent, forget. Claude calls them automatically based on instructions in your system prompt. You set it up once and stop thinking about it. The part I'm most happy with is how recall works. Every note gets vector-embedded using Workers AI (bge-small-en-v1.5) and stored in Cloudflare Vectorize. So when Claude searches your memory, it's matching by meaning, not keywords. Store "users drop off at checkout" and recall it later with "onboarding problems" — it finds it. What I used Claude for building this: Wrote most of the MCP server implementation in TypeScript Helped me work through the Vectorize + D1 architecture Generated the iOS Shortcuts templates and bookmarklet Wrote the README (Claude writing docs for a Claude memory tool felt appropriate) Stack: Cloudflare Workers + D1 (SQLite) + Vectorize + Workers AI. The whole thing runs on Cloudflare's free tier for personal use. One-click deploy button in the repo. Works with Claude Desktop, Claude Code, and claude.ai (via custom connectors). Repo: https://github.com/rahilp/second-brain-cloudflare Happy to answer questions about the implementation — the semantic search piece especially has some interesting tradeoffs worth discussing. submitted by /u/rahilpirani5 [link] [comments]

Attention - Opus 4.7 is english only. USing foreign languages (here German) burns tokens

I am a pro subscriber. I developped a not too sophisticated prompt in German. Then I wanted to to a quality check... Sonnet just did the job. Opis 4.6 did the job but two graphs in the output were incomplete. Opus 4.7 extended... I used a fresh session, 0% and bang it consumed the whole session tokens in seconds where the other models took around 5 minutes to complete the task. I asked it... On German consuming your whole session limit. This one's real and not a bug per se, it's how tokenization works: Claude tokenizes text. English text averages roughly 1 token per 0.75 words. German averages closer to 1 token per 0.5 words — sometimes worse — because of compound nouns ("Aktienmarktanalyse" tokenizes into more pieces than "stock market analysis"), umlauts, and less training-data coverage. For the same semantic content, a German prompt + German response can consume 1.5× to 2× the tokens of the English equivalent. Combined with tool calls, web searches, and a long Excel-building output, that adds up fast. Session limits on Claude.ai are token-based, not message-based. So yes — running this exact workflow in German legitimately eats more of your quota. Workarounds: prompt in German but ask for the response/output in English (the spreadsheet labels could stay English while we converse in German), or ask me to be terser. Anthropic is aware of the multilingual token-cost issue but it's a structural property of the tokenizer, not something I can fix on my end. The prompt: Please provide me with a forecast for the stocks of The Trade Desk, Coreweave, and Cloudflare for the next 6 months. Also analyze the impact of earnings misses and fundamental data such as margin growth and the market’s overreaction to minor corrections. The result should be an Excel spreadsheet. Create a chart covering the last 24 months and a forecast for the next 6 months, then a chart for the last 30 days and a forecast for the next 30 days. Then do the same again for the last 7 days and the next 7 days. Also include the options (calls and puts) on the three stocks mentioned, any short interest, and the positioning of major investors in the 13F filings. In english opus 4.7 extended consumes 37% of the session, 4.6 did 33% and Sonnet around 28%. In German.. 100% in seconds. The other models I could even feed with 3 page prompts, those which materialize as text file when pasting them... this is completely ridiculous. submitted by /u/WickOfDeath [link] [comments]

When a critical Linux kernel privilege escalation was publicly disclosed, Cloudflare's security and engineering teams detected, investigated, and mitigated the threat across our global fleet, confirmi

When a critical Linux kernel privilege escalation was publicly disclosed, Cloudflare's security and engineering teams detected, investigated, and mitigated the threat across our global fleet, confirming zero customer impact. https://t.co/oDgoPxnAZs

HR is no longer just administration. Cita James explains how People Teams became true business partners, and why early experience matters for anyone starting in the field. Watch the episode and subs

HR is no longer just administration. Cita James explains how People Teams became true business partners, and why early experience matters for anyone starting in the field. Watch the episode and subscribe to the podcast: https://t.co/k7dbUqVuPR https://t.co/Am1MAhNKQ7

Choosing the right security services can feel impossible when existing tools don't meet your needs. How can organizations effectively tackle these hurdles? Join us for an insightful webinar with Har

Choosing the right security services can feel impossible when existing tools don't meet your needs. How can organizations effectively tackle these hurdles? Join us for an insightful webinar with Harshad Kadam from Indeed, who will illustrate how they leverage Cloudflare's https://t.co/4wWfhuDuqq

U.S. Public Sector missions are moving at the speed of AI. But with rapid adoption comes a critical question: Is your agency’s data staying within your "Zero Trust" boundary? 🛡️ Shadow AI and data e

U.S. Public Sector missions are moving at the speed of AI. But with rapid adoption comes a critical question: Is your agency’s data staying within your "Zero Trust" boundary? 🛡️ Shadow AI and data exfiltration are real risks, but they shouldn't stop your progress. Join us for an https://t.co/bws5fxitFi

DNSSEC failure broke the .de TLD, risking millions of German domains. See how 1.1.1.1 used "serve stale" and Negative Trust Anchors to restore resolution during the incident. Read the full technical b

DNSSEC failure broke the .de TLD, risking millions of German domains. See how 1.1.1.1 used "serve stale" and Negative Trust Anchors to restore resolution during the incident. Read the full technical breakdown. https://t.co/FtyON7H3QQ

Leaders' top challenge: Deploying changes across all regions and maintaining global compliance (70%). 🌐 Read more in the 2026 Cloudflare App Innovation Report: https://t.co/hWEu20DFTd https://t.co/

Leaders' top challenge: Deploying changes across all regions and maintaining global compliance (70%). 🌐 Read more in the 2026 Cloudflare App Innovation Report: https://t.co/hWEu20DFTd https://t.co/u7vyf9AQw3

SASE is built for simplicity and scale. Join Cloudflare experts on May 12th at 12pm CT for an efficient path to modernizing remote access. Learn how to rapidly roll out ZTNA and navigate migration wi

SASE is built for simplicity and scale. Join Cloudflare experts on May 12th at 12pm CT for an efficient path to modernizing remote access. Learn how to rapidly roll out ZTNA and navigate migration with proven, real-world examples. Register here: https://t.co/uE9Lv1t3yt https://t.co/fKRneEqMbI

Protect your remote and office-based teams with one scalable DNS policy. See how Cloudflare simplifies your secure access service edge (SASE) implementation: https://t.co/41oOebZ4MV https://t.co/rxm

Protect your remote and office-based teams with one scalable DNS policy. See how Cloudflare simplifies your secure access service edge (SASE) implementation: https://t.co/41oOebZ4MV https://t.co/rxmllWVSW1