Auth0 AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

Auth0 AI AI

I built a space strategy MMO that Claude can play natively via MCP

The Elevator Pitch PSECS is a multiplayer space game designed for AI agents. Claude connects via MCP and can explore sectors, mine resources, research technologies, manufacture items, trade on a market, and fight other players' fleets. No GUI needed — Claude IS the interface. It's free to start and the universe is persistent. Website: https://www.psecsapi.com MCP Server: https://mcp.psecsapi.com/mcp I'm currently experimenting with playing in Cowork so that it can automate game play. How was it built? I had been working on this project for years off and on (mostly off) and had gotten less than half of the game's v1 systems working. In mid-December, I got Claude Code for the first time and it was off to the races! In the last 3 months, I have: Finished the game engine for v1 Implemented an API, CLI, and MCP server for multi-modal playability Created the web site and integrated with Auth0 Completed all of the tech tree content building Deployed to Azure in containers via Github pipelines And much more All of this was powered by Claude Code! What did I learn along the way? Context management is both a science and an art - though it may be less pertinent now that we have the 1M models superpowers:brainstorm is incredibly powerful, but needs to be forced into expansive progression Use it first to define a "product spec with no implementation details" Then feed that back in to brainstorm and tell it to produce the "design" Then feed both of those back into writing-plans and have it create a separate md doc for each task/phase/whatever. Ralph Loops **work very well** when properly built I wrote a whole server (again, written by Claude Code) to manage loops for me (see https://github.com/dbinky/ralph-o-matic) that also has skills to help create "good" loop prompts --dangerously-skip-permissions really isn't that dangerous if you are working through a superpowers-based workflow Anyway... I'd love to hear some feedback on what your agents think of it! And if you have any specific questions about my workflow, I'd be happy to answer! submitted by /u/Dr-whorepheus [link] [comments]

I built a drop-in OAuth provider so your personal FastMCP server works on every Claude platform

I spent way too long on this so figured I'd share. I have a mem0-based memory server, basically a personal knowledge vault that Claude can read and write to. Getting it working on Claude Code was easy. Getting it working on Claude.ai web, mobile, AND Desktop? Not so much. The problem is auth. Claude.ai custom connectors need full OAuth 2.1. FastMCP gives you an in-memory test provider (useless in production) or a proxy that requires setting up Google/GitHub/Auth0 as an identity provider. I don't want to set up Auth0 for a server only I use. So I wrote a single-file auth provider that handles it. No external services, no account with a third party, just a Python file you drop next to your server. It does DCR, PKCE, token persistence, the whole OAuth dance. Redirect URIs are locked to claude.ai and localhost so random people can't auth against your server even though client registration is open (Claude.ai requires open registration, that one took a while to figure out). Some things that bit me along the way that I couldn't find documented anywhere: - FastAPI's BaseHTTPMiddleware silently breaks streaming responses. Spent hours on that one. - If your tools are named things like add_memory or search, Claude will use its own built-in memory instead of calling your tools. You have to prefix them distinctively. - Neon Postgres (and probably other serverless DBs) drops idle connections. If you create one connection at startup your tools will randomly start failing after a few minutes. - DCR is disabled by default in FastMCP. Without it /register returns 404 and Claude.ai just silently fails to connect. No error message, nothing. Anyway, it's on GitHub: github.com/crumrine/fastmcp-personal-auth One Python file, MIT licensed. If you have a FastMCP server and want it working on all the Claude platforms without setting up a whole identity provider, this might save you a weekend. submitted by /u/B4dPanda [link] [comments]

I built ClaudeNest entirely with Claude Code — a remote launcher for Claude Code's remote-control sessions

Hey everyone, I built ClaudeNest to solve a specific friction point with Claude Code's remote control feature. I use remote control daily — interacting with Claude Code through claude.ai while it runs on my dev machine. But I always had to be at my machine to start the session. If I was away from my desk, I was stuck. ClaudeNest is a remote launcher that lets you start and manage Claude Code remote-control sessions from anywhere, including mobile. The entire project was built with Claude Code. I directed the product decisions and reviewed output (well some... most... ok some of it), but Claude Code did the architecture, planning, and wrote every line of code. How Claude Code built it: - Architecture from scratch: I described the problem and Claude Code designed the three-component system — a lightweight agent on the dev machine, a SignalR backend as a command relay, and a React web dashboard. Claude made key decisions like using outbound-only connections from the agent (no port forwarding), native AOT compilation for a single-binary agent, and deliberately not streaming terminal I/O since Claude's own remote-control handles that. - Wrote all the code across multiple sessions: The .NET backend (ASP.NET Core + EF Core + SignalR), the React/TypeScript frontend (Vite + Tailwind), the native AOT agent with cross-platform service installers (macOS/Windows/Linux), Auth0 integration, Stripe billing, database migrations — all Claude Code. - High-level review passes between features: After completing features, I'd ask Claude Code to review the full codebase for performance, security, and bugs. These passes caught real issues — like EF Core write queries missing change tracking (silently not saving), a memory leak in the agent's session manager causing ~56GB growth, and auth edge cases. These weren't part of any single feature session — they were separate review sweeps across the whole codebase. - Built its own coding standards: As patterns emerged, Claude Code documented conventions in the project's CLAUDE.md file so future sessions would be consistent. Things like controller patterns, entity conventions, test structure, frontend component reuse rules. Each new session built on prior decisions without me re-explaining context. - Full test infrastructure: Claude Code set up integration tests with WebApplicationFactory, Testcontainers for SQL Server, test auth handlers, and database seed helpers — then wrote tests for each controller. What ClaudeNest does: - A small agent runs on your dev machine(s) and connects outbound to the ClaudeNest backend - From the web dashboard (works great on mobile), you browse your project folders and launch remote-control sessions - Once running, you interact through claude.ai as normal — ClaudeNest doesn't touch your code or terminal output What it doesn't do: - Doesn't access your source code, API keys, or Claude credentials - Doesn't proxy or relay terminal I/O - It's purely a remote launcher and session manager Sign up at https://claudenest.com, pair your agent, and you're running. The entire codebase is open source if you want to verify exactly what runs on your machine: https://github.com/gordonbeeming/ClaudeNest submitted by /u/Gordon-Beeming [link] [comments]