Cairo Coder

Created By
kasarlabsa year ago
The most powerful open-source Cairo code generator.
Overview

What is Cairo Coder?

Cairo Coder is a powerful open-source code generator designed to assist developers in creating Cairo code and smart contracts for the Starknet and Ethereum ecosystems.

How to use Cairo Coder?

To use Cairo Coder, you can run the MCP server directly with the command: npx -y @kasarlabs/cairo-coder-api. Ensure you have your API key configured in the environment variables.

Key features of Cairo Coder?

  • Generate smart contracts and Cairo code effortlessly.
  • Refactor and optimize existing code.
  • Implement specific features and complete TODOs in your code.
  • Access contextual information about the Starknet ecosystem and best practices.

Use cases of Cairo Coder?

  1. Writing new Cairo smart contracts.
  2. Refactoring existing Cairo code for optimization.
  3. Learning about Starknet and its features through contextual assistance.
  4. Implementing specific functionalities in smart contracts.

FAQ from Cairo Coder?

  • What is required to run Cairo Coder?

You need Node.js version 18 or higher and an API key to use the Cairo Coder API.

  • Can I contribute to Cairo Coder?

Yes! Contributions are welcome, and you can check the contribution guidelines on the GitHub repository.

  • Where can I find support?

You can create issues on GitHub or refer to the MCP documentation for assistance.

Server Config

{
  "mcpServers": {
    "cairo coder": {
      "command": "npx",
      "args": [
        "-y",
        "@kasarlabs/cairo-coder-mcp"
      ],
      "env": {
        "CAIRO_CODER_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kasarlabs
Star
-
Language
-
License
-
Category

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)

a day ago