Skip to main content
Glama
606,818 tools. Updated 2026-09-24 11:36

"How to work with Cocos .csd files" matching MCP tools:

  • Add up a timesheet of work hours, and turn them into gross pay. Use for: 'how many hours did I work this week', 'add up my shifts', 'what will I be paid for these hours', 'I worked 22:00 to 06:00, how long is that'. Handles overnight shifts: a finish time at or before the start is treated as the next day, so 22:00 to 06:00 is eight hours rather than a negative. Args: days: One dict per day worked, each with "start" and "finish" as "HH:MM" in 24 hour time, optional "break_minutes" of unpaid break, and an optional "label". Leave days off out of the list entirely. hourly_rate: Gross pay per hour. Zero returns hours only. Returns: Hours for each day, the total, and GROSS pay weekly, fortnightly, monthly and annually. For take-home pay use nz_hourly_to_salary_calculator with the rate and the hours. Does not apply overtime or penal rates, public holiday entitlements, or a minimum wage check.
    ConnectorNo auth
  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    ConnectorNo auth
  • Claim files before an agent edits them so other agents do not patch the same SwiftUI/App files concurrently. Claims are local, short-lived, and stored in .axint/coordination/claims.json. Use: use before editing shared files in parallel-agent work; release claims when done. Inputs: agentId and files identify the claim; ttlMinutes bounds ownership and force overrides stale claims. Effects: writes local coordination claims under .axint/coordination; no network.
    ConnectorNo auth
  • WORKFLOW: Step 3 of 4 - Generate Terraform files from completed design Generate Terraform files from an InsideOut session that has completed infrastructure design. ⚠️ PREREQUISITE: Only call this AFTER convoreply returns with `terraform_ready=true` in the response metadata. DO NOT call this while convoreply is still running or before terraform_ready is confirmed! If you get 'session has not reached terraform-ready state', wait for convoreply to complete first. 🎯 USE THIS TOOL WHEN: convoreply has returned with terraform_ready=true, OR the user asks to 'see the terraforms', 'generate terraform', 'show me the code', etc. **DEFAULT RESPONSE**: Returns summary table + download URL (keeps code out of LLM context). **FALLBACK**: Set `include_code: true` to get full code inline if curl/unzip fails. **CRITICAL WORKFLOW** (default mode): 1. Call this tool to get file summary and download URL 2. ASK the user: 'Where would you like me to save the Terraform files? Default: ./insideout-infra/' 3. WAIT for user confirmation before running the download command 4. Run the curl/unzip command with the user's chosen directory 5. If curl/unzip FAILS (sandbox, security, platform issues), retry with `include_code: true` **AFTER GENERATION**: Ask user if they want to review the files and then deploy with tfdeploy REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: include_code (boolean) - set true to return full code inline as fallback. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.
    ConnectorNo auth
  • WORKFLOW: Step 3 of 4 - Generate Terraform files from completed design Generate Terraform files from an InsideOut session that has completed infrastructure design. ⚠️ PREREQUISITE: Only call this AFTER convoreply returns with `terraform_ready=true` in the response metadata. DO NOT call this while convoreply is still running or before terraform_ready is confirmed! If you get 'session has not reached terraform-ready state', wait for convoreply to complete first. 🎯 USE THIS TOOL WHEN: convoreply has returned with terraform_ready=true, OR the user asks to 'see the terraforms', 'generate terraform', 'show me the code', etc. **DEFAULT RESPONSE**: Returns summary table + download URL (keeps code out of LLM context). **FALLBACK**: Set `include_code: true` to get full code inline if curl/unzip fails. **CRITICAL WORKFLOW** (default mode): 1. Call this tool to get file summary and download URL 2. ASK the user: 'Where would you like me to save the Terraform files? Default: ./insideout-infra/' 3. WAIT for user confirmation before running the download command 4. Run the curl/unzip command with the user's chosen directory 5. If curl/unzip FAILS (sandbox, security, platform issues), retry with `include_code: true` **AFTER GENERATION**: Ask user if they want to review the files and then deploy with tfdeploy REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: include_code (boolean) - set true to return full code inline as fallback. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.
    ConnectorNo auth
  • Reference guide to supply-chain simulation concepts: ordering policies, BOM, FDD formulas, event-driven simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does this work' question rather than asking for a number.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Bridges Cocos Creator 3.8.x editor with MCP protocol, enabling Claude Code to query and modify scenes, assets, and previews, and to edit prefab files offline.
    14 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • Job orders for trades and field work: parts, labour, status, completion report, invoice payload.

  • チームの働き方を支援するグループウェア Work Handler の MCP サーバー。組織・メンバーの参照、出退勤の共有、タイムカード、承認フロー等を本人の権限の範囲で操作できる。

  • Inspect the files of an EXISTING artifact: list them, search their text, read them, or review the commit history. Works with no shell, no git and no network access, so prefer it whenever you cannot run git. Pass the sessionId (the last path segment of a .../chat/<sessionId> URL). A canvasDraft field, when authorized, reports an uncommitted Canvas draft. Use action draft to inspect its projection overlay explicitly; ordinary reads remain committed files. Draft access requires write permission. Typical flow to change something: action "search" to find the file, action "read" for the files you will edit, then artifact-edit. Every response includes "revision", the artifact's current commit — pass it back as artifact-edit's baseRevision. Use action "read" with a "revision" to see how a file looked at an earlier commit (this is how you undo something). Assets — images, fonts, media — are readable too: action "read" answers with size, mime and oid under "asset": true whenever a file's bytes are not text, instead of content. That check is on the bytes, so it is the authority: an SVG reads as text, and a file with an unfamiliar extension may still come back as an asset. When a search comes back empty, check "notSearched": "assets" counts binary files a text query can never match, and "excluded" counts files under node_modules, dist or build — re-run with includeExcluded true to search those. A "tree" listing also maps any path artifact-edit cannot change under "unwritable". For generation or build progress use artifact-status instead; this shows the commit log, not build state.
    ConnectorOAuth
  • Read what a GRADUATED app actually SERVES right now — not the seed captured before it graduated. Without path: the list of files in the served version, with their size, and whether each one is server code. With path: that file's content, INCLUDING server.js — which is deliberately never served to visitors. Use this before dropyour_replace: a graduated app is replaced WHOLE, so you need its current files to avoid overwriting your own work. Large files are truncated (truncated=true, bytes reports the real size); binary files are reported as binary rather than mangled. Tier 4 only — at tiers 1-3 what the drop serves IS what you published, so use dropyour_read_content.
    ConnectorNo auth
  • Read first. States plainly what submit_enquiry does on Malta Work Permit Checker: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
    ConnectorNo auth
  • Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; for anything larger — or for putting the file on disk — the pm-files MCP server saves it to a path instead (local_files_setup says how to connect it). Reading needs only permission to see the page.
    ConnectorNo auth
  • Returns the current items in the selected project. Items are tasks for you to work on. ALWAYS call cherry_pick before doing any work on items — NEVER do work without picking first. Ask the user to confirm before calling complete_items. Show the `display` field to the user verbatim in a code block. If has_more is true, call again with cursor to get more. Do NOT show has_more or next_cursor to the user — ask "More items?" instead.
    ConnectorOAuth
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    ConnectorNo auth
  • Bid on an open task. Args: access_token: AgentAuth bearer token (requires ``market.bid``). task_id: UUID of the task to bid on. proposed_cost_units: Your price, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. estimated_duration_seconds: How long you expect the work to take. proposed_approach: Free-text summary of how you'll do the work. terms: Optional JSONB — anything else worth stating up front. confidence_score: Your self-assessed confidence, 0.0-1.0. Returns: The created bid (status ``"pending"``). The task moves to ``"bidding"`` on its first bid. Errors: ``not_found`` (no such task), ``invalid_input`` (bidding on your own task, past bid_deadline, an existing pending bid, or a task not open for bidding).
    ConnectorNo auth
  • Get how a page served from a Valet site talks to the connectors attached to it. It is the pair to get_design_system: consult that tool for the artifact's identity, this one for how it talks to its connectors. Call it before writing any page code that fetches from a connector. Returns the same-origin request contract and a paste-whole session helper that handles both sessionless and stateful connectors, plus the rules a page has to follow: handling a 403, recovering a lapsed session, and never caching a response on the caller's behalf. This needs no Valet account. It answers with static guidance about how pages work — nothing here reads an organization or a site — so an agent can call it before running any OAuth flow.
    ConnectorNo auth
  • Step 4 of the Tango working agreement (work in the open). Attach every concrete output — notes, drafts, results, files, links — as an artifact so it's part of the task record, not just chat. Real files (pdf, docx, pptx, xlsx, mp3, wav, m4a, images…) are supported: pass `content_base64` for files up to ~6 MB, `fetch_url` to have Tango download and store a hosted file itself, or call create_artifact_upload first for large files and finalize here with `upload_token`. `content` stays the path for inline text and `external_url` for a link you only want recorded. Reference artifact ids in complete_task's evidence_artifact_ids. If a lease is active, Tango attributes the artifact to the lease holder. Otherwise, pass `acting_worker_id` to identify which of your workers is acting; if you don't own that worker the attribution is dropped rather than misrecorded. Attested workers may pass `worker_signature` over the JCS-canonical artifact payload (type 'tango.artifact'); an invalid signature rejects the call and nothing is stored. Delegated workers are signed for automatically.
    ConnectorNo auth
  • Work out a New Zealand family's Working for Families entitlement. Use for: 'how much Working for Families will I get', 'what is my family tax credit', 'do I qualify for the in-work tax credit', 'how much Best Start will I get', 'will I lose Working for Families if I earn more'. CORRECT A COMMON AND EXPENSIVE MISTAKE. There is NO hours test for the In-Work Tax Credit and has not been one since 1 July 2020. Anyone with some income from paid work each week, who is not on an income-tested benefit or student allowance, qualifies. Many sources, including our own website page, still repeat the old 20 hours sole parent / 30 hours couple rule. A parent working fifteen hours a week is entitled to $7,670 this year and is often told they are not. ASK FOR THE COMBINED FAMILY INCOME, not one partner's. Everything abates against it, so an answer from one income is wrong. ASK HOW MANY CHILDREN ARE UNDER 3, not under 1. Best Start runs to the third birthday and is worth $4,041 a year per child. The In-Work Tax Credit is temporarily $7,670 a year until 31 March 2027, then reverts to $5,070, so an answer about next year differs from this one. Say which you have given. Args: children: Dependent children in the caregiver's care. family_income: Combined gross annual family income, all sources. children_under_3: How many are under 3, for Best Start. iwtc_eligible: Some paid work and no income-tested benefit. best_start_children_first_year_exempt: Under-3s in their first year born BEFORE 1 April 2026, which are exempt from the income test. iwtc_after_march_2027: Model the reverted $5,070 rate. Returns: FTC, IWTC and Best Start with each abatement shown separately, the annual, weekly and fortnightly totals, an assumptions block naming every rate used, and what the calculation excludes.
    ConnectorNo auth
  • Swamp's Agent Skill, as the SKILL.md artifact published at /.well-known/agent-skills/. This is the practice of being a resident rather than the wire format: when to register, how to make your work survive a session ending, why a finding is not a result until a peer reruns it, and how memory, sources and conversation work. Read it if you are deciding whether this place is useful to you. Read /skill.md instead for exact request bodies and headers. No credential.
    ConnectorNo auth
  • What M-Kliniki is, the services it offers in Kenya, and how its escrow payments work. Call this to describe M-Kliniki accurately to a user.
    ConnectorNo auth
  • Plain-English explanation of how scoring works, the two governing principles, what is deliberately left out (protected characteristics, luck), and the privacy stance. Use to answer "how does this work / is this fair" questions.
    ConnectorNo auth
  • Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.
    ConnectorNo auth
  • Keyword/full-text search over the Canton Network knowledge base (CIPs, Canton/Daml/Splice docs, forum, mailing lists, whitepapers, grant proposals, blog, YouTube, GitHub). Canton-specific. Do NOT use for other blockchains, the web, or local files. Use this for exact-term/name lookups; use semantic_search instead for conceptual or 'how does X work' questions, and get_doc to read a full page once you have its id. NOTE: forum matches cover the topic TITLE and the FIRST POST only; a term that appears only inside a forum reply will not surface here, so use semantic_search (which indexes all forum post bodies) when a forum discussion is likely and this returns nothing.
    ConnectorNo auth