CRITICAL STARTING POINT. Returns high-level game mechanics, survival timers, and economic parameters. Use this to understand how to win and avoid penalties.
Connector
466,647 tools. Updated 2026-08-19 18:41
"Canva" matching MCP tools:
- Open the FluxInk handwriting recognition canvas. The user draws freehand strokes with a stylus, finger, or mouse. The strokes are converted by one of two model families: general recognition for handwriting, math, and chemical formulas, or structure recognition for molecular structures. Use this when the user asks to handwrite, draw, sketch, ink, scribble, or scrawl something. Use this when the user wants to draw a math equation, chemical formula, or molecular structure rather than type it. Use this when the user asks for a canvas, drawing pad, handwriting input box, or whiteboard. Use this when the user wants to convert stylus or finger drawings into recognized text or markup. Do NOT use this when the user types a question, equation, or formula in chat and just wants an answer. Do NOT use this when the user uploads or references an existing image of handwriting (call recognize_image instead). Do NOT use this when the user wants a formatted document, study sheet, or layout PDF (call create_layout instead). Do NOT use this when the user wants text rendered in a personal handwriting style (call show_style_canvas instead). Do NOT use this for conversational or informational requests that need no ink input. Do NOT re-open if a FluxInk handwriting canvas is already visible from any earlier turn. Instead instruct the user to keep drawing on the existing canvas. Only set force_new=true when the user explicitly asks for a brand new, fresh, or blank canvas. Always pass the original chat message in the prompt parameter so context is preserved after recognition. After calling, write a single short acknowledgement and do NOT describe the canvas UI.Connector
- Returns the REST API contract for an AdCritter entity. Without an action parameter, returns a summary with available action names - use this to discover what you can do. With an action parameter (e.g., 'create', 'list', 'get'), returns the full details for that action: route, HTTP method, request schema, response schema, error codes, and constraints. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, canva, domain, facebook, geo, googleads, media-asset, me, plan, report, segment, settings, targeting.Connector
- Open the FluxInk natural texture ink style capture canvas. The user draws a few sample characters in a personal handwriting style. The widget then renders the requested text as a PNG spritesheet IN THAT EXACT PERSONAL HANDWRITING STYLE. Output is a downloadable spritesheet of individual handwritten glyphs that can be used as an asset (for example with image generation). Use this when the user asks to render or generate text in a personal handwriting style. Use this when the user wants a personalized handwritten note, card, letter, invitation, journal entry, or signature line that should look hand written by the user. Use this when the user wants to capture, clone, or sample a personal handwriting style and reuse it. Do NOT use this when the user just wants handwriting recognized (call show_handwriting_canvas instead). Do NOT use this for generic decorative handwritten fonts, calligraphy art, or AI generated script unrelated to the personal writing of the user. Do NOT use this to read text from an existing photo of handwriting (call recognize_image instead). Do NOT use this when the user wants a formatted document or layout (call create_layout instead). Do NOT use this for plain informational requests. Supports English and Chinese. Always pass the COMPLETE target text in the text parameter. Never truncate or abbreviate. Every character must appear in the spritesheet. Do NOT re-open if a FluxInk natural texture ink canvas is already visible from any earlier turn. Instead instruct the user to update the target text inside the existing widget. Only set force_new=true on an explicit user request for a brand new style canvas. After calling, write a single short acknowledgement and do NOT describe the UI. Once the user saves the spritesheet they can re-upload it for further design work.Connector
- Add one or more nodes to the canvas. Batch every node you want in a single call. Positions are assigned by canvas_layout_canvas afterwards — never set them yourself. Operates on one Datadef diagram, named by diagram_id. If you have not already, call get_design_guide first — it carries Datadef's size, edge, and zone standard, and diagrams built without it read poorly.Connector
- Returns guidance on diagram-creation workflow and tool selection: how to choose between Mermaid and manual element creation, and the recommended iteration workflow. Consult before building complex diagrams.Connector
Matching MCP Servers
- FlicenseCqualityCmaintenanceEnables creation and management of Canva presentations through natural language, leveraging LLM for narrative planning and integrating with Canva's API for design operations.28
- Alicense-qualityDmaintenanceA Model Context Protocol (MCP) server for Canva integration. Connect Claude Code or any MCP-compatible AI client to your Canva account to search designs, generate AI designs, edit content, manage folders, and collaborate through comments.2MIT
Matching MCP Connectors
The Canva MCP server connects AI assistants (like Claude, ChatGPT, and Cursor) to Canva's API, enabling them to create and manage designs directly within chat conversations. Key capabilities include generating new designs from prompts, autofilling templates, searching and resizing existing designs, importing files from URLs, exporting designs as PDFs or images, and managing folders and comments without switching between tools.
A decentralized 32×32 pixel-war execution grid for autonomous AI agents on Base Mainnet. Competitive game theory meets an on-chain USDC economy with native Model Context Protocol (MCP) integration.
- Creates elements on a canvas. Creates a new canvas if room_id is omitted, or adds to the existing canvas if room_id is provided. Use cases: wireframes, UI mockups, freeform illustrations, standalone shapes, and manual layouts that Mermaid does not cover well. For diagrams Mermaid can express, use add_elements_from_mermaid instead. Element types: rectangle, ellipse, diamond, arrow, line, freedraw, text, image. Rich text: the text field supports limited HTML for text elements and rectangle/ellipse/diamond shape labels. Supports the rich-text plugin HTML subset: <b>/<strong>, <i>/<em>, <u>, <br>, <div>/<p>, <ul>/<ol>/<li>, <a href>, <font color>, and <span style="color, background/background-color, font-size, font-family">. Use textAlign for left/center/right alignment; avoid unsupported HTML/CSS. TEXT IN SHAPES: use containerId on text element pointing to shape id. ARROWS: Position at EDGE of source shape. Auto-bound within 30px. Colors: strokeColor, backgroundColor (hex).Connector
- Add a single data node at an exact position, without connecting it to anything. Use when the user wants something placed somewhere specific, or when you will wire it up yourself afterwards. For building out a connected diagram, canvas_add_nodes is better — it batches and lets layout position everything. Operates on one Datadef diagram, named by diagram_id.Connector
- Draw one large labelled arrow representing a whole flow — "ingest", "serve", "publish" — instead of many thin edges saying the same thing. Use this when several things move the same way for the same reason: draw the arrow once between the two areas rather than connecting every pair. This is a visual annotation, not a connection, so it adds no edges and no fan-out. Position it in the gap between the two areas using canvas_measure_canvas. Operates on one Datadef diagram, named by diagram_id.Connector
- Draw a labelled translucent area behind existing nodes to show they belong together, without reparenting them. Use this when the grouping is a reading aid rather than real containment, when areas would need to overlap, or when a node belongs to two ideas at once — canvas_group_nodes cannot express any of those because it moves nodes into the zone. Call canvas_measure_canvas first and size the region to enclose the nodes with roughly 24px of margin. Operates on one Datadef diagram, named by diagram_id.Connector
- Query elements on a canvas. Requires room_id from a previous Canvs tool result. Returns elements matching optional filters. Use this before update_elements when making small edits to existing diagrams. If no browser has the canvas open, returns an error — ask the user to open the canvas URL in their browser and retry.Connector
- Update elements on a canvas. Requires room_id from a previous Canvs tool result. Pass elements array with id and fields to update. IMPORTANT: in each update object ONLY `id` is required; all other fields are optional patch fields. Include ONLY elements that need changes; elements omitted from the request remain unchanged on the board. Prefer this tool for SMALL edits to existing diagrams (rename/move/restyle a few elements), typically after query_elements.Connector
- Place a free-floating text box on the canvas — a caption, a callout, a section heading, a note explaining a decision. Position it with explicit coordinates from canvas_measure_canvas. Text boxes are annotations: they are not part of the data flow and take no edges. Operates on one Datadef diagram, named by diagram_id.Connector
- Merge several nodes into one summary node, keeping every connection. Use when a set of near-identical objects adds length without adding meaning — eight staging models that all behave the same become "stg_* (8)". Do not use when the individual objects are what the reader came for. Operates on one Datadef diagram, named by diagram_id.Connector
- Status check. Returns your current internal USDC ledger balance. Check this before attempting to paint.Connector
- Delete elements from a canvas. Requires room_id from a previous Canvs tool result. Pass ids array of element IDs to delete.Connector
- Creates diagram elements from a Mermaid definition. Creates a new canvas if room_id is omitted, or adds to the existing canvas if room_id is provided. Preferred over add_elements for new diagrams and large changes to existing diagrams whenever the content can be represented in Mermaid. Supports: flowchart, graph, flowchart-elk, sequenceDiagram, classDiagram, classDiagram-v2, stateDiagram, stateDiagram-v2, erDiagram, journey, gantt, pie, gitGraph, mindmap, timeline, C4Context, C4Container, C4Component, C4Dynamic, C4Deployment, sankey, sankey-beta, quadrantChart, xychart, xychart-beta, requirement, requirementDiagram, kanban, architecture, block, block-beta, packet, packet-beta, radar-beta, treemap, info. Example: "flowchart TD\n A[Start] --> B{Decision}\n B -->|Yes| C[OK]\n B -->|No| D[Cancel]"Connector
- Infrastructure: Refill internal ledger. Generates transaction data to move USDC from your wallet into the Arena's internal balance. This is required to paint pixels and saves ~70% on gas.Connector
- Competitive intelligence. Returns agent rankings by profit, paints, and win rate based on recent arena activity.Connector
- Draw edges between nodes to show how data flows. Always label the edge with what actually happens ("ingest", "dbt transform", "hourly sync") — unlabelled edges make a diagram useless. Operates on one Datadef diagram, named by diagram_id.Connector