Create a new diagram from Mermaid source — flowcharts, sequence diagrams, mind maps, ER diagrams, Gantt charts, and anything else Mermaid supports. Requires a personal access token with the "diagram" scope.
ConnectorNo auth
675,084 tools. Updated 2026-10-19 03:16
"Tools for Analyzing Code Structure and Logic to Create Flowcharts and Diagrams" matching MCP tools:
- Publish one public Markdown text post as a selected agent owned by the signed-in human operator. Use list_my_agents first to obtain the agent ID. Use the dedicated code tools for code requests and reviews; App and Cabana posts are not available through this connector release. Call only after the user explicitly confirms the exact title, body, tags, agent, and optional karma reward.ConnectorNo auth
- Get COMMENT CONTENT (text, likes) for an Instagram post. Returns the actual comment objects with text and metadata. RETURNS COMMENT DATA: id, text, username, createdAtDate, likeCount, childCommentCount. Use for reading what people said. NOT FOR USER PROFILES: To get detailed user profiles (bio, followerCount, followingCount) of commenters, use getInstagramPostInteractingUsers with interactionType="commenters" instead. IMPORTANT: postId must be in strong_id format (e.g., "3606450040306139062_4836333238") - use the full "id" value from other Instagram tools, NOT just the media_id. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. PAGING (responseType="paging"): Async paginated results (100/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. CSV (responseType="csv"): Async single CSV download, returns operationId, poll for S3 link. CODE EXECUTION: For csv mode, download CSV and use code execution to analyze full dataset. Ideal for: sentiment analysis, reading discussions, analyzing comment content, engagement patterns. Date filters: OMIT startDate/endDate parameters by default. ONLY pass these if user explicitly requests specific date range (YYYY-MM-DD format). IMPORTANT!!!!!: THE CURRENT YEAR IS 2026. When user requests relative dates (last week, last month), verify the current date from your system context and double-check the calculated dates - models often get the year wrong, searching one year earlier than intended. Optional fields: ["id", "text", "username", "createdAtDate", "likeCount"]. This is a safe, read-only tool for analyzing searchable information.ConnectorOAuth
- Get COMMENT CONTENT (text, likes) for a Tiktok post. Returns the actual comment objects with text and metadata. RETURNS COMMENT DATA: id, text, username, createdAtDate, likeCount. Use for reading what people said. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. PAGING (responseType="paging"): Async paginated results (100/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. CSV (responseType="csv"): Async single CSV download, returns operationId, poll for S3 link. CODE EXECUTION: For csv mode, download CSV and use code execution to analyze full dataset. Ideal for: sentiment analysis, reading discussions, analyzing comment content, engagement patterns. Date filters: OMIT startDate/endDate by default. ONLY pass if user explicitly requests date range. IMPORTANT!!!!!: THE CURRENT YEAR IS 2026. When user requests relative dates (last week, last month), verify the current date from your system context and double-check the calculated dates - models often get the year wrong, searching one year earlier than intended. Optional fields: ["id", "text", "username", "createdAtDate", "likeCount"]. This is a safe, read-only tool for analyzing searchable information.ConnectorOAuth
- Approve a StrategySuggestion, optionally creating the suggested Strategy. Closes the PROPOSE loop for MCP-only agents: wraps the same approve-and-create service logic as the REST ``StrategySuggestionViewSet.approve`` action instead of a manual ``suggested_config`` round-trip through the strategy create tools, which silently drops the suggestion linkage (``StrategySuggestion.created_strategy`` / hive DecisionRecord.suggestion FK provenance). ``wallet_address`` is the caller's own wallet (recorded as ``approved_by_wallet``); when ``agent_wallet_id`` also resolves to a wallet ``wallet_address`` controls, the suggested Strategy is created through the same executor dry-run gate as every other create path. ``config_overrides`` merges over ``suggested_config`` (e.g. a real ``usd_per_buy``). A wallet without a Turnkey signer still gets the strategy -- paper trade, unsigned tx per tick. Informational rationale only (rules 5-8); the created strategy still runs only through the existing engine gates. Workflow: DECIDE -> EXECUTE step -- the MCP-only closing move for get_strategy_suggestions; pair with backtest_strategy + get_risk_assessment first for the same guardrails any other create path gets.ConnectorDestructiveNo auth
- Create a form, define its fields, brand it, publish it, and return a shareable short link + QR in one step. Use for 'make me a form to collect X, give me a link and QR to share it'. The result's `share_url` is the public link and `qr_id` is the form's own dynamic QR code (image included) — never call create_qr_code or create_short_link for a form's link; pass QR design args (primary_color, eye_style, frame, logo_url, …) here to style that code in the same call. Supports on-brand styling (theme/colors/logo), a `redirect_url` after submit, conditional logic (`show_when` on a field) and branching endings (`outcomes`), and a custom domain/slug. Publishing mints a dynamic short link and QR — always dynamic, no static option, since a form has to resolve somewhere live. Notifications are a separate, paid, verified-member setting. To change a form later, use update_form.ConnectorOAuth
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.1GPL 3.0
Matching MCP Connectors
Generate cloud architecture diagrams, flowcharts, and sequence diagrams.
Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)
- Load a tool catalog: returns its intro text, usage patterns, and each tool's full JSON input schema as markdown. On surfaces that scope active tools by context this also activates the catalog's tools (elsewhere they are already callable and this just adds the enriched context — workflows, field semantics, constraints — beyond the bare schema). Prefer loading the relevant catalog before using a capability over guessing a tool name or argument shape. For domain knowledge (themes, settings, logic semantics) use `load_skill` instead. Available catalogs: - form-data: Aggregate form analytics (views, completions, drop-off). Individual submission rows: formSubmission_list. - form-appearance: Visual styling: per-mode themes (light + dark). Cover/logo via form_update. - form-behavior: Behavior settings: notification emails, completion redirect, password, retention, language, payment, webhook. - form-sharing: Share-link CRUD + custom-domain attach/detach. Required after form_publish for respondent URL. - form-translations: Multilingual draft → publish workflow for form copy. - form-lifecycle: Form lifecycle ops beyond publish: unpublish, restore-from-trash. - workspace-management: Workspace inspect + folder CRUD beyond core list verbs. - request-lifecycle: Requests: discover field keys, create (with an existing form or one built in the call), read, list, cancel, remind, replay the callback, upload a document, check Stripe and Cal.com connections. - editor-actions: Editor actions beyond getDocument/updateElement/deleteElement: format text, set logic, simulate logic. - editor-inserts: Less-common element inserts beyond the core set: time/switch/file/signature/matrix/ranking/payment/schedule-appointment/picture-choice questions, embedded/table/list content, row/repeating-group layout, calculated/hidden fields, logic + variable.ConnectorOAuth
- Adds a LANGUAGE LAYER to a survey (or upserts translations of an existing layer). A language is a layer on the SAME survey: structure, logic and the collected dataset are shared; only texts are overlaid. Respondents pick the language via ?Language=<code> on the share link or the survey's language selector; anything untranslated falls back to the source text. Author content (question texts, option labels, matrix rows, survey title, custom end message) is seeded with the SOURCE texts as the translation worklist. Supply translations in translations[]: {question, text} for a question's text, {question, option:<code>, text} for an option label, {question, row:<n>, text} for a matrix row, {target:'survey-title'|'survey-description'|'end-message'|<service-slot>, text} for named targets. IMPORTANT: built-in localization of service texts (buttons, validators, service pages) exists for ru/de/en ONLY — for any other language those slots stay on the English/source fallback; the reply lists the service slot keys still needing translations — translate them and call again (idempotent upsert). Add languages LAST: questions added after the layer are not in it until you re-run configure_survey_language (the survey still works — they fall back to source text). Verified by re-reading the stored translation set. Requires the edit-survey right.ConnectorDestructiveOAuth
- Edits an EXISTING question in place: title, answer requirement (none|soft|strict), custom ID, and the option list. Options are matched by their export CODE (the numbers get_survey reports): a matching option is relabeled IN PLACE — its identity, collected answers and logic references stay intact; a new code is added as a new option; a code MISSING from the submitted list is REMOVED. Always pass the FULL desired option list — a partial list removes the options you left out. Removing options from a survey that already has responses is HIGH-CONSEQUENCE: it retroactively re-interprets collected data and cannot be undone (re-adding creates a new identity) — the call fails with a warning unless confirm:true; get the user's EXPLICIT consent first. Changing the question TYPE is not supported — delete_question and add_question instead. The reply reports the applied changes, response count and any logic rules referencing the question, verified by re-reading the stored survey. Requires the edit-survey right.ConnectorDestructiveOAuth
- Retrieve the full TypeScript source code of a specific bundled template by id. Returns a complete, compilable defineIntent() file as a string — ready to save as .ts and compile with axint.compile. Includes perform() logic, parameter definitions, and domain-specific patterns. Use: use after templates.list to fetch a complete reference template; edit it before calling compile. Inputs: id must come from templates.list; format changes source versus metadata rendering. Effects: read-only template source; writes no files and uses no network.ConnectorNo auth
- Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents and instructs your AI to keep them local—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.ConnectorNo auth
- Verify the 6-digit code sent to the patient's email. Returns a guest-scope bearer token for intake, consent, order, and checkout tools. Requires the session_id from auth_start — no email needed. After checkout and payment, call auth_check_payment to upgrade the token to full scope for portal access.ConnectorDestructiveNo auth
- Verify the 6-digit code sent to the patient's email. Returns a guest-scope bearer token for intake, consent, order, and checkout tools. Requires the session_id from auth_start — no email needed. After checkout and payment, call auth_check_payment to upgrade the token to full scope for portal access.ConnectorDestructiveNo auth
- Dump the user's monitors as a JSON structure suitable for backup, migration, or infrastructure-as-code workflows. Tokens and PII are NEVER included - only domain configuration.ConnectorNo auth
- Validate a single International Bank Account Number (IBAN) against the official ISO 13616 structure for its country. What it checks: the country code, total length for that country, the national BBAN structure, and the MOD-97 check digits. When the bank/branch code maps to a known institution, the response also includes the bank name, BIC/SWIFT code, and country. Returns JSON with `valid` (boolean), `iban`, `formatted`, `country`, `country_name`, `check_digits`, `bban`, and, when the bank is recognized, `bank_name`, `bic`, `bank_code`, `bank_city`, `sepa` and `national_check_valid`. An invalid IBAN still returns a result, with `valid: false`, an `error` message and an `error_code` (e.g. INVALID_CHECKSUM, INVALID_LENGTH, UNKNOWN_COUNTRY); it does not throw. Use this when you have one account number to verify. For many IBANs prefer `validate_bulk_ibans`; to pull IBANs out of prose use `extract_ibans_from_text` first. No account data is stored; validation runs in memory and is discarded. Requires an API key; a free key from ibanchecker.cash/api-docs covers 100 requests a month.ConnectorNo auth
- Creates and displays an interactive draw.io diagram from Mermaid.js syntax or draw.io XML — provide exactly one. **Choose the format first.** Use `xml` for diagrams of boxes and lines up to about 30 shapes: flowcharts, pipelines, decision trees, org charts, ER schemas, UML class, state and use case diagrams, mind maps, timelines, architecture, cloud and network diagrams, swimlanes, UI mockups, floor plans and anything with stencils. You place every shape yourself, laid out for the chat view (see the XML reference). Use `mermaid` for sequenceDiagram, gantt, gitGraph, pie, journey, quadrantChart, xychart-beta, sankey-beta, requirementDiagram, C4Context/C4Container/C4Component, block-beta, packet-beta, kanban, radar-beta, treemap-beta, treeView-beta, venn-beta, ishikawa-beta, zenuml, wardley-beta, eventmodeling, and for flowcharts, class and state diagrams of more than about 30 shapes (flowcharts with postLayout elk). Whenever the user asks for draw.io XML or no Mermaid, use XML for the rest of the conversation. **Call `get_drawio_reference` before your first diagram in a conversation**, once per format, with the format you chose: "mermaid" has the syntax for every type (a misspelled header renders blank), "xml" the styles, layout grid, edges, containers, layers and dark mode. Call `search_shapes` first for industry icons (AWS, Azure, GCP, Cisco, Kubernetes, P&ID, electrical) or logos. XML essentials: <mxGraphModel adaptiveColors="auto"><root><mxCell id="0"/><mxCell id="1" parent="0"/>…</root></mxGraphModel>. Every cell has a unique id. Vertices: vertex="1" with <mxGeometry x y width height as="geometry"/>. Edges: edge="1" with source and target, always with a child <mxGeometry relative="1" as="geometry"/>. Put html=1 in every style and XML-escape HTML in values (< > & "). No XML comments. Don't add waypoints. Place the shapes yourself (no postLayout) and set `routing: "libavoid"` only when an edge would otherwise cross a shape.ConnectorNo auth
- Critical-path validation, logic health, and DCMA-14 assessment of a Primavera P6 schedule. Runs the CPP critical-path validator: checks for false criticality, constraint-driven CP segments, open ends, broken logic, and surfaces a DCMA-14 block with the 14 metrics (logic, leads, lags, FS%, hard constraints, high float, high duration, invalid dates, resources, missed tasks, critical tasks, CPLI, BEI, etc.) at the chosen profile threshold (commercial / nuclear / mining). When ``baseline_xer_path`` is supplied, BEI (Baseline Execution Index) is computed. Use this tool to grade a schedule's logic health and find what should be fixed before forensic analysis. For the full HTML health-dashboard PDF render, use ``dcma14_health_check``. Args: xer_path: server-side path to the schedule XER. xer_content: full text of the schedule XER (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. project_index: which project to analyze in a multi-project XER (0 = first/primary; default). profile: DCMA threshold profile - 'commercial' (default), 'nuclear', 'mining'. baseline_xer_path: optional server-side baseline XER for DCMA BEI. baseline_xer_content: optional baseline XER text content (alternative). Returns: Full validator result dict including: - 'project_name', 'data_date', 'analysis_timestamp' - 'total_activities', 'complete', activity counts - 'critical_path_findings': list of issues - 'logic_findings', 'constraint_findings' - 'overall_rating' / 'overall_score' / 'overall_confidence': LOGIC-HEALTH verdict only (open ends, logic continuity, critical-path correctness, constraints, lags). NOT a full schedule-health verdict. - 'overall_rating_scope': always 'logic_health'; 'overall_rating_label': 'Logic Health'. Use these so the headline cannot be read as full DCMA schedule-health. - 'dcma_worst_severity': the embedded DCMA-14 worst severity (BLOCK/RED/WARN/INFO/PASS) surfaced at the top level so a DCMA hard stop is visible next to the logic-health rating rather than buried in dcma_14.report.summary. - 'dcma_blocks_despite_logic_rating': True when DCMA-14 says BLOCK/RED even if the logic-health headline reads GREEN/AMBER. - 'dcma_14': dict of 14 DCMA metric results - 'recommendations': list of remediation suggestionsConnectorNo auth
- Create a ZenSched org (step 2 of 2): verify the emailed code. Returns org_id and your zsc_ API key (shown once). Claude.ai must then Connect → Sign in with the same email — do not keep calling org tools until Connect succeeds.ConnectorNo auth
- Create a ZenSched org (step 2 of 2): verify the emailed code. Returns org_id and your zsc_ API key (shown once). Claude.ai must then Connect → Sign in with the same email — do not keep calling org tools until Connect succeeds.ConnectorNo auth
- The operator's brand & PPC decision framework: margin spine (PPD + margin bands), product postures, campaign structure/bidding, harvesting/negation logic, guardrails and decision triggers. CALL THIS before analyzing an account or proposing ANY optimization (bids, budgets, negatives, harvest, campaigns, pricing) and follow it as the default operating model; pass section= (see toc) for a focused read.ConnectorOAuth
- Load a domain-knowledge skill — themes, settings, analytics, logic-rules, editing-flows, question-types, etc. Returns markdown reference content. Use when the task touches a domain whose conventions or constraints are not obvious from the surrounding tools. For loading additional MCP tool catalogs (deferred tools by bundle name) use `load_tools` instead. Available skills: - toon-format: TOON format reference for reading and parsing form document structure - question-types: All question types with parameters, validation, and when to use each - logic-rules: Conditional logic conditions, actions, patterns, and examples - editing-flows: Editing workflows, node chaining, batch operations, and best practices - form-best-practices: Form design best practices for question design, ordering, and type selection. - analytics: Form analytics interpretation, metrics, and actionable insights - form-settings: Form configuration options, security, notifications, email customization, and data retention - form-themes: Form visual theming system — schema, constraints, design guidelines, and examples - requests: Requests: asking named people to fill a form — field keys, prefill shapes, building the form in the same call, delivery, callbacks, pollingConnectorOAuth