Back to MCP Directory
Connections & Capabilities
Connects To
GitHubAWSS3
Capabilities
readwrite
Quickstart
Install
npx @fireflyai/firefly-mcpConfig
{
"mcpServers": {
"firefly": {
"command": "npx",
"args": ["-y", "@fireflyai/firefly-mcp"],
"env": {
"FIREFLY_ACCESS_KEY": "your_access_key",
"FIREFLY_SECRET_KEY": "your_secret_key"
}
}
}
}Exposed MCP Tools (2)
safe
Resource DiscoveryDiscovers resources across connected cloud and SaaS accounts.
Primarily a read-only operation.
moderate
Resource CodificationConverts discovered resources into Infrastructure as Code (Terraform).
Generates code that, if executed, can modify infrastructure.
Safety Assessment
The Firefly MCP server is relatively safe for resource discovery and codification when API keys are securely managed and IaC changes are thoroughly reviewed. However, the risk increases if API keys are exposed or if the server is used to directly apply infrastructure changes without proper controls.
- Uses API keys for authentication, providing a degree of access control.
- Focuses on resource discovery and codification, which can be primarily read-oriented.
- Supports integration with Infrastructure as Code tools, promoting controlled deployments.
- Can be configured to run in read-only mode, limiting potential for destructive actions.
- Requires storing API keys, which can be a security risk if not managed properly.
- Codification into IaC could lead to unintended infrastructure changes if not reviewed carefully.
- Server exposes an endpoint that, if compromised, could allow unauthorized resource discovery.
- Lack of built-in RBAC beyond API keys limits fine-grained access control.
