Eyevinn Open Source Cloud vs MCP Server Terraform
A side-by-side look at the Eyevinn Open Source Cloud and MCP Server Terraform MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
Eyevinn Open Source CloudCloud Platforms · Remote HTTP/SSEDeploy open-source services and your own apps on Open Source Cloud (OSC, osaas.io).37FairAuth: not declaredVerdict: choose Eyevinn Open Source Cloud for cloud platforms work over a hosted endpoint; choose MCP Server Terraform for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
EChoose Eyevinn Open Source Cloud when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
Choose MCP Server Terraform when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tf_validate, tf_plan, tf_output.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E Eyevinn Open Source Cloud | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 37/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Eyevinn Open Source Cloud | View MCP Server Terraform |
Tools & capabilities
Eyevinn Open Source Cloud tools
No tool names declared yet. Check the project README from the listing page.
MCP Server Terraform tools 11
tf_validateValidate Terraform configuration files for syntax and internal consistency. Does not access remote state or APIs.tf_planRun terraform plan and return a human-readable diff of what will change. Safe — makes no changes to infrastructure.tf_outputRead Terraform output values from the current state. Returns all outputs as JSON, or a specific output by name.tf_preflightCheck which cloud providers are used in a Terraform workspace and verify authentication status for each. Call this before plan or apply to catch credential issues early.tf_driftDetect infrastructure drift — resources that were changed outside of Terraform (e.g. manually in the cloud console). Runs a refresh-only plan and reports differences between state and reality. Read-only, makes no changes.tf_applyApply Terraform changes to real infrastructure. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → runs terraform plan, shows the diff, returns without applying. 2. Call with confirmed=true after reviewing the diff → actually applies the changes. Never pass confirmed=true without first showing the plan output to the user.tf_destroyDestroy all Terraform-managed infrastructure in the workspace. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → shows the destroy plan (what will be deleted). 2. Call with confirmed=true after the user explicitly approves → destroys everything. This is irreversible. Always show the plan and get explicit user approval first.tf_stateManage Terraform state. Supports the following operations: - list: List all resources in state - show: Show attributes of a specific resource - mv: Move/rename a resource in state (use with care) - rm: Remove a resource from state without destroying it (destructive)tf_resourceResource-level state operations: - import: Bring an existing cloud resource under Terraform management (requires address + id) - taint: Mark a resource for recreation on next apply (requires address) - untaint: Remove the taint mark (requires address) - refresh: Sync state with real infrastructure (accepts drift into state)tf_initInitialize a Terraform working directory. Downloads providers and modules. Run this before plan or apply on a fresh workspace.tf_workspaceManage Terraform workspaces. Supports: - list: List all workspaces and show which is active - show: Show the current workspace name - select: Switch to a workspace - new: Create a new workspace
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Eyevinn Open Source Cloud
{
"mcpServers": {
"eyevinn-open-source-cloud": {
"url": "https://www.osaas.io/mcp"
}
}
}
MCP Server Terraform
{
"mcpServers": {
"rajeevsirohi-mcp-server-terraform": {
"command": "npx",
"args": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
}
Frequently asked questions
Eyevinn Open Source Cloud is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. MCP Server Terraform belongs to Cloud Platforms and uses a local stdio subprocess. Pick Eyevinn Open Source Cloud for cloud platforms work and MCP Server Terraform for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Eyevinn Open Source Cloud is listed as free. MCP Server Terraform has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add eyevinn-open-source-cloud and rajeevsirohi-mcp-server-terraform as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Eyevinn Open Source Cloud has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Server Terraform has 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars.
