MCP servercom.luthersystems.insideout/mcp
Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements.
Overview
Score?
UNRATED 0.681
of what a free look can see, on 32 looks
Looks
36
last 3 hr ago
Tools
24
More info
URL
app.luthersystems.com/v1/insideout-mcp
streamable-http
Says it is
insideout-agent v2.0.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.681 · highest on record 0.8561
Toolsfrom sha256:580b4daa97…ad23a6
| Tool | Schema |
|---|---|
| awsinspect INSPECTION: Inspect AWS infrastructure for a deployed project
⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed).
Check convostatus for hasDe |
input · no output |
| awsinspect_batch BATCH INSPECTION: run up to 32 AWS inspect probes in one call.
⚠️ **PREREQUISITE**: Same as awsinspect — deploy attempt required.
Check convostatus for hasDeployAttempt=true before |
input · no output |
| convoawait Wait for a pending response from Riley after a convoreply timeout.
🎯 USE THIS TOOL WHEN: convoreply returned a timeout error.
This allows you to continue waiting for the response |
input · no output |
| convoinspect INSPECTION: View a session's conversation transcript and metadata
Returns the full message history (user / assistant / tool turns) plus the session's meta — workflow step, cloud, d |
input · no output |
| convoopen WORKFLOW: Step 1 of 4 - Start infrastructure design conversation
Open an InsideOut V2 session and receive the assistant's intro message.
The response contains a clean message from |
input · no output |
| convoreply WORKFLOW: Step 2 of 4 - Continue infrastructure design conversation
Send a user message to the active InsideOut session and receive the assistant reply.
The response contains a cle |
input · no output |
| convostatus INSPECTION: View the current infrastructure stack for a session
Returns the current state of the user's infrastructure design including:
**Components** - Selected infrastructure s |
input · no output |
| credawait Wait for the user to securely connect their cloud account and subscribe to Luther Systems.
Polls until credentials appear on the session.
🎯 USE THIS TOOL WHEN: tfdeploy returns an |
input · no output |
| gcpinspect INSPECTION: Inspect GCP infrastructure for a deployed project
⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed).
Check convostatus for hasDe |
input · no output |
| gcpinspect_batch BATCH INSPECTION: run up to 32 GCP inspect probes in one call.
⚠️ **PREREQUISITE**: Same as gcpinspect — deploy attempt required.
Check convostatus for hasDeployAttempt=true before |
input · no output |
| help Get workflow guidance for using InsideOut infrastructure tools.
Call help() for a compact overview, or help(section=...) for a detailed guide.
Sections: workflow, tools, examples, |
input · no output |
| stackdiff Structured diff showing what would be deployed if the user ran tfdeploy now.
Returns component-level changes (added/removed/modified), field-level details, and pricing deltas.
Def |
input · no output |
| stackrollback Create a draft version by reverting to a previous version's config.
Copies components, config, and pricing from the target version. If a draft already exists, updates it in-place ( |
input · no output |
| stackversions List all stack versions for a session (newest first).
Shows version history including version number, status (draft/confirmed/applied), change summaries, and timestamps.
Use this |
input · no output |
| submit_feedback FEEDBACK: Submit feedback, bug reports, or feature requests to Luther Systems
Use this tool to forward user feedback directly to the Luther Systems team. This includes bug reports, |
input · no output |
| tfdeploy WORKFLOW: Step 4 of 4 - Deploy infrastructure to the cloud
Deploy infrastructure by starting a Terraform job for an InsideOut session.
This tool initiates the actual deployment pro |
input · no output |
| tfdestroy DESTROY: Tear down previously deployed infrastructure
Destroys infrastructure by calling the Oracle destroy endpoint for a session that has a prior successful deployment.
IMPORTANT |
input · no output |
| tfdrift DRIFT CHECK: Run a read-only drift detection check
Checks whether deployed infrastructure has drifted from the expected Terraform state.
This is a read-only operation — it does NOT |
input · no output |
| tfgenerate WORKFLOW: Step 3 of 4 - Generate Terraform files from completed design
Generate Terraform files from an InsideOut session that has completed infrastructure design.
⚠️ PREREQUISITE |
input · no output |
| tflogs MONITORING: Fetch Terraform deployment logs with pagination
Fetches logs from a running or completed Terraform deployment job.
For **completed jobs**: uses REST endpoint for instan |
input · no output |
| tfoutputs INSPECTION: Retrieve Terraform outputs from a completed deployment
Returns structured output values (VPC IDs, endpoints, cluster names, etc.) after a successful deploy.
Sensitive o |
input · no output |
| tfplan PREVIEW: Run terraform plan to preview infrastructure changes
Runs a terraform plan for an InsideOut session without applying any changes.
This lets the user review what will be cr |
input · no output |
| tfruns INSPECTION: List all Terraform deployment runs for a session
Returns job IDs, statuses, types (apply/destroy), and timestamps for every run.
Use this to see deployment history, fin |
input · no output |
| tfstatus MONITORING: Quick status check for Terraform deployments
Check the current status of a Terraform deployment job.
Use this tool to quickly check if a deployment is running, complete |
input · no output |
Verify it yourself
npx teppi-check https://app.luthersystems.com/v1/insideout-mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ27FZPGG5DGAK4X6TNCN7