Awslabs Nova Canvas Mcp Server

Created By
awslabsa year ago
Overview

What is Awslabs Nova Canvas MCP Server?

Awslabs Nova Canvas MCP Server is a specialized server designed for generating images using Amazon Nova Canvas, integrating AWS best practices into the development workflow.

How to use Awslabs Nova Canvas MCP Server?

To use the Nova Canvas MCP Server, install the required dependencies, configure your AWS credentials, and add the server to your MCP client configuration. You can then generate images by sending requests with customizable parameters.

Key features of Awslabs Nova Canvas MCP Server?

  • Text-based image generation with customizable parameters
  • Color-guided image generation with specific palettes
  • Workspace integration for saving generated images
  • AWS authentication through profiles

Use cases of Awslabs Nova Canvas MCP Server?

  1. Creating custom images for web applications
  2. Generating graphics for marketing materials
  3. Automating image creation for data visualization

FAQ from Awslabs Nova Canvas MCP Server?

  • What is the primary function of the Nova Canvas MCP Server?

The primary function is to generate images based on text prompts and customizable parameters.

  • Is there a cost associated with using the Nova Canvas MCP Server?

The server itself is free to use, but AWS service costs may apply based on usage.

  • How do I configure the server?

Configuration involves setting up AWS credentials and adding the server to your MCP client configuration.

Server Config

{
  "mcpServers": {
    "awslabs-nova-canvas-mcp-server": {
      "command": "uvx",
      "args": [
        "awslabs.nova-canvas-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1",
        "FASTMCP_LOG_LEVEL": "ERROR"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
awslabs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago