GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
제작자가 쓴 설명(영어 원문)
Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://app.luthersystems.com/v1/insideout-mcpClaude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"insideout": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/luthersystems/insideout-mcp:v0.36.3"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add --transport http insideout https://app.luthersystems.com/v1/insideout-mcpclaude mcp add insideout -- docker run -i --rm docker.io/luthersystems/insideout-mcp:v0.36.3프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"insideout": {
"url": "https://app.luthersystems.com/v1/insideout-mcp"
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"insideout": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/luthersystems/insideout-mcp:v0.36.3"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"insideout": {
"type": "http",
"url": "https://app.luthersystems.com/v1/insideout-mcp"
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"insideout": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/luthersystems/insideout-mcp:v0.36.3"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://app.luthersystems.com/v1/insideout-mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 도메인 insideout.luthersystems.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.36.3)은 6개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: GitHub, Desktop Commander, Cloudflare MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Cloud infrastructure automation. Describe your application in natural language and InsideOut will design, configure, deploy, and manage production-ready backend infrastructure -- in minutes, not weeks.
Works standalone or integrated directly into AI app builders via MCP.
npx skills add luthersystems/insideout-agent-skills
Works with Claude Code, Codex, Cursor, Kiro, Windsurf, and 30+ other tools.
[View on Skills.sh](https://skills.sh/luthersystems/insideout-agent-skills/insideout) | [Try the web app](https://insideout.luthersystemsapp.com/) -- no install required.
Setting up cloud infrastructure is slow, error-prone, and requires deep DevOps expertise. Teams spend weeks on plumbing -- networking, security, storage, scaling configuration -- before writing a single line of product code.
InsideOut eliminates this. You describe your application; InsideOut handles the rest: architecture design, Terraform generation, cost estimation, deployment, and ongoing management.
Before InsideOut: Weeks of manual infrastructure setup, Terraform authoring, and cloud configuration. With InsideOut: Backend infrastructure deployed in minutes, managed continuously.
| Capability | Manual Terraform | InsideOut |
|---|---|---|
| Time to deploy | Days to weeks | Minutes |
| Security defaults | Manual | Automatic |
| Cost visibility | Post-deploy billing | Pre-deploy estimates |
| Observability setup | Manual | Day one |
| AI app builder integration | None | Native (Claude Code, Codex, Kiro, Antigravity) |
| Terraform ownership | Yes | Yes (generated, exportable) |
Once installed, just ask:
"Build me a scalable backend for my golang microservices app on AWS with a DB and auth."
InsideOut will:
You: "I need infrastructure for an e-commerce platform, 1k monthly users on AWS"
Riley: "I'd recommend ECS for your containers, RDS PostgreSQL for your database, ElastiCache Redis for sessions, and an ALB. Estimated cost: ~$350/month. Want me to adjust anything?"
You: "Looks good, generate the Terraform"
[Generates production-ready Terraform files]
You: "Deploy it"
[Deploys to AWS, streams logs in real-time]
| User | Use case |
|---|---|
| Solo developers | Ship a production backend without DevOps expertise |
| Startup engineering teams | Move from idea to deployed infrastructure in minutes |
| AI app builders | Integrate infrastructure automation directly into AI-native development workflows |
| Enterprise teams | Standardise infrastructure with best practices and cost controls |
| DevOps / platform engineers | Faster architecture and IaC workflows |
If you'd rather describe what you want than manually wire it together -- this is for you.
| Path | Best for | Install |
|---|---|---|
| This repo (recommended for Codex) | Portable skill across multiple AI tools | npx skills add luthersystems/insideout-agent-skills |
| [Claude Code plugin](https://github.com/luthersystems/insideout-claude-code) | Best native Claude Code experience | /plugin marketplace add luthersystems/insideout-claude-code |
| [Kiro power](https://github.com/luthersystems/insideout-power) | Best native Kiro experience | Add power from GitHub: luthersystems/insideout-power |
| [Web app](https://insideout.luthersystemsapp.com/) | No install required | Open in browser |
npx skills add luthersystems/insideout-agent-skills
For the full plugin experience (slash commands, agents, hooks, auto-approve):
/plugin marketplace add luthersystems/insideout-claude-code
/plugin install insideout
npx skills add luthersystems/insideout-agent-skills --agent codex
Activate by typing $insideout -- Codex will detect the missing MCP server and prompt you to install it automatically.
Fallback: If the auto-install doesn't trigger, run:
codex mcp add insideout --url https://app.luthersystems.com/v1/insideout-mcp
npx skills add luthersystems/insideout-agent-skills --agent cursor
Then add the MCP server to your Cursor MCP config:
{
"mcpServers": { "insideout": { "type": "http", "url": "https://app.luthersystems.com/v1/insideout-mcp" } } }
npx skills add luthersystems/insideout-agent-skills --agent windsurf
Add MCP via Windsurf MCP Marketplace or manually in settings.
For the full power experience (steering files, design pattern guides, auto-approve):
luthersystems/insideout-powernpx skills add luthersystems/insideout-agent-skills --agent antigravity
Then add the MCP server in Antigravity: "..." menu → MCP Servers → Manage MCP Servers → View raw config:
{
"mcpServers": { "insideout": { "serverUrl": "https://app.luthersystems.com/v1/insideout-mcp" } } }
Note: Antigravity uses
serverUrl, noturl.
git clone https://github.com/luthersystems/insideout-agent-skills.git
cp -r insideout-agent-skills ~/.agents/skills/insideout
The ~/.agents/skills/ directory is the standard cross-tool location. Most AI coding tools will detect skills here automatically.
| Category | AWS | GCP |
|---|---|---|
| Compute | EC2, ECS, EKS, Lambda | Compute Engine, Cloud Run, GKE, Cloud Functions |
| Database | RDS PostgreSQL, DynamoDB, ElastiCache, OpenSearch | Cloud SQL, Firestore, Memorystore |
| Networking | VPC, ALB, CloudFront, API Gateway | VPC, Load Balancing, Cloud CDN, API Gateway |
| Storage | S3 | Cloud Storage |
| Security | WAF, KMS, Secrets Manager, Cognito | Cloud Armor, Cloud KMS, Secret Manager, Identity Platform |
| Messaging | SQS, MSK (Kafka) | Pub/Sub |
| Observability | CloudWatch, Managed Grafana | Cloud Logging, Cloud Monitoring |
| AI/ML | Bedrock | Vertex AI |
| CI/CD | CodePipeline, GitHub Actions | Cloud Build |
| Backup | AWS Backup | GCP Backups |
Architecture patterns: AI Stack, Microservices, Serverless. Azure support is upcoming.
Describe your application in natural language. InsideOut generates the architecture, configuration, and Terraform. Review, tweak, and deploy -- all from one place.
Get cost estimates for your exact stack before committing. No surprise bills; pricing is surfaced at design time.
Security best practices applied automatically. Observability configured from day one -- no retroactive setup needed.
You own the generated Terraform files. Use InsideOut defaults or override any setting. No lock-in; the output is standard infrastructure-as-code.
Luther Systems sets up and manages critical infrastructure. Ongoing updates and operational support included.
InsideOut uses a multi-agent AI system behind a single MCP server:
| Agent | Role |
|---|---|
| Riley | Infrastructure advisor -- leads the design conversation |
| Hippo | Cost estimation and pricing optimization |
| Joy | User experience and requirement gathering |
| Etch | Terraform code generation |
| Core | Architecture validation and best practices |
| Axel | Deployment orchestration |
From your perspective, you're talking to Riley. The other agents work behind the scenes. These capabilities are exposed as tools inside your AI environment, so you use them conversationally.
See SECURITY.md for detailed data flow documentation.
InsideOut uses a library of battle-tested, standard Terraform modules composed for common infrastructure patterns.
Can I use InsideOut without the InsideOut UI? Yes. InsideOut integrates with Claude Code, Codex, Kiro, Antigravity, and any MCP-compatible AI development environment, allowing you to design, price, and deploy infrastructure directly from your editor without opening the InsideOut interface.
Do I own the generated Terraform? Yes. InsideOut generates standard Terraform files that you own and can export, modify, or use independently of the platform.
Can I override the default configuration? Yes. InsideOut applies best-practice defaults but every setting is overridable. You control the final configuration before deployment.
What clouds does InsideOut support? AWS and Google Cloud Platform. AWS has the deepest support with the widest range of resource types. Azure support is upcoming.
Is InsideOut suitable for AI application backends? Yes. InsideOut explicitly supports AI stack architectures and is designed to work within AI-native development environments like Claude Code, Codex, Kiro, Antigravity, and other MCP-compatible tools.
How does pricing work? Cost estimates for your exact stack are surfaced before deployment. Contact Luther Systems for platform pricing: contact@luthersystems.com
Luther Systems is an enterprise infrastructure and automation company founded in 2015, headquartered in London, UK. Our mission is to accelerate the advent of the automated enterprise.
Founded by a team who spent years automating complex processes for some of the world's largest financial institutions, Luther Systems builds platforms that bring enterprise-grade infrastructure and operations to teams of every size.
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요