"A platform for sharing and collaborating on software projects" matching MCP tools:

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorOAuth

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorAPI key

• update_projectA

  3DLogo.ioA

  Use when the user wants an existing project changed without opening the studio: its title, whether it is public (a public project has a share page and, for meshes, a public GLB URL), and on logo and coin projects the style: material, lighting room, background, motion, depth, font, the wordmark on text projects; on coins also the look, coin and mark colours, and the blank edge. Only the fields given change. Making a project public needs a saved render. Style changes render the next time the project is opened and saved. Do not use for a share link that keeps the project private (create_share_link) or to make something new (create_text_logo_project, duplicate_project).

  ConnectorOAuth

• answer_llm_requestA

  Entity EnricherA

  Answer one LLM request of a job running on your model (every start tool's default unless use_platform_models=true or an explicit platform model): you are its model. Read the request under get_job_status(job_id).llm_requests (or in the start tool's return): run systemPrompt + messages with the listed tools and toolChoice on your own model, then pass the result here as response in MCP CreateMessageResult shape — {role: 'assistant', model: '<your model>', stopReason: 'toolUse' | 'endTurn', content: [{type: 'tool_use', id, name, input}] | {type: 'text', text}} — with optional usage {input_tokens, output_tokens}. toolChoice.mode 'required' means one tool_use block whose input matches the tool's inputSchema. The platform validates the answer like a provider's: a rejected answer returns as a new request with the error in a tool_result (isError) — fix and answer again. Returns the next pending request(s), the terminal result, or the running status after wait_seconds. Not for question pauses (answer_job_question). No platform LLM call. Guide: enricher://docs/llm-delegation.

  ConnectorOAuth

• acknowledge_direct_settlement_taskA

  Molt2MeetA

  DIRECT SETTLEMENT FLOW ONLY. Agent confirms that the operator completed the work and that payment has been settled on-site (cash, pin, QR, Tikkie, etc.). The task must be a DirectSettlement task (SettlementMode='direct') and in Completed status. Transitions directly to Closed — no platform escrow, no fund release. For escrow tasks use approve_task_review instead.

  ConnectorNo auth

• request_task_quoteA

  Molt2MeetA

  ESCROW FLOW ONLY. Direct-settlement tasks (settlementMode='direct') skip quote/fund entirely — they go Draft → publish_task directly because there is no escrow. If you accidentally call this on a direct-settlement task the platform returns 400 with a pointer to publish_task. Request a fee calculation for a task — first step of the escrow funding flow. Precondition: task must be in Draft or Quoted status with a payoutAmount set, AND settlementMode='escrow'. Calling this on an already-funded task returns an error. Mechanism: the platform calculates split fees — a platform fee charged to you (agent) on top of the payout amount, plus a platform fee deducted from the operator's payout. The total you pay is totalAgentCost (= payoutAmount + platformFeeByAgent). Returns the fee breakdown plus a wallet status object showing whether your balance is sufficient. Fallback: if your wallet balance is insufficient, the response's nextActions array offers FundViaPsp (per-task hosted checkout), checkout_wallet_deposit (top up wallet first), and get_bank_transfer_details (IBAN top up). Pick whichever matches your funding pattern. Next: fund_task with the chosen fundingMethod, then publish_task. Requires authentication.

  ConnectorNo auth

• how_munimji_helpsA

  HelloBooks AI AgentsA

  Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.

  ConnectorNo auth

• how_munimji_helpsA

  HelloBooks AI Agents MCP ServerB

  Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.

  ConnectorNo auth

• projects_searchA

  EpinuA

  Search Epinu real-asset projects. Returns bounded summaries only; call projects_get_deep_dive for detailed packets. Results include public projects plus the token owner's own archived, draft, or unpublished projects for duplicate checks; another owner's unpublished projects are never returned. Available without a token for public results only.

  ConnectorNo auth

• social_searchA

  socialbridge-mcpA

  Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.

  ConnectorNo auth

• retry_deployA

  LayeroA

  Run a build again — a failed one as is, or the latest commit afresh. Default (`redeploy=false`): queue the SAME build again. Allowed only for builds in the `failed` or `cancelled` state. On a running build (`queued`, `building`) the platform refuses — that is not an error but protection against a second parallel build; on a `ready` build it refuses too — use `redeploy=true`. `redeploy=true`: start a NEW build of the branch's latest commit without a push. This is how changed project settings (`project_settings`) or environment variables (`env_vars`) get applied. The result goes live the same way a push to that branch would — on the production branch that is production, so make sure the person wants that. Projects without a repository are rebuilt by deploying the folder again (`npx layero@latest deploy` or `publish_site`). ⚠️ A plain retry makes sense when the cause was external (network, registry, timeout). If the build failed on the code, a retry gives the same result: `diagnose_deploy` first, then the fix, and only then a retry.

  ConnectorOAuth

• retry_deployA

  LayeroA

  Run a build again — a failed one as is, or the latest commit afresh. Default (`redeploy=false`): queue the SAME build again. Allowed only for builds in the `failed` or `cancelled` state. On a running build (`queued`, `building`) the platform refuses — that is not an error but protection against a second parallel build; on a `ready` build it refuses too — use `redeploy=true`. `redeploy=true`: start a NEW build of the branch's latest commit without a push. This is how changed project settings (`project_settings`) or environment variables (`env_vars`) get applied. The result goes live the same way a push to that branch would — on the production branch that is production, so make sure the person wants that. Projects without a repository are rebuilt by deploying the folder again (`npx layero@latest deploy` or `publish_site`). ⚠️ A plain retry makes sense when the cause was external (network, registry, timeout). If the build failed on the code, a retry gives the same result: `diagnose_deploy` first, then the fix, and only then a retry.

  ConnectorAPI key

• create_cloud_connectionA

  Tomorrow Central: Cloud Cost SentinelB

  Start linking a cloud account so it can be scanned. `provider` is "aws", the only provider supported today; `account_id` is the 12-digit AWS account number. `software` is the Tomorrow Central software the link is for; omit it for Cloud Cost Sentinel. Each software has its own read-only role, so link once per software. This is a two-party flow and you cannot finish it alone — creating the read-only IAM role requires the human's AWS credentials. Returns a `launch_url`. Hand the human these instructions verbatim: 1. Open the launch_url (a pre-filled CloudFormation quick-create link). 2. Review the read-only role it creates, then click Create stack. 3. Tell you when the stack says CREATE_COMPLETE. Then call `verify_connection` with the returned connection_id. Verification fails with a clear message until the role exists, so polling it every ~15 seconds is safe and expected. No ARN or secret needs to be copied by anyone.

  ConnectorNo auth

• list_projectsA

  TsehaA

  Lists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projects the calling credential may see. Call it first in a session: the returned id is the project_id that every other tool in this server requires, and guessing that id fails. It does not return components, packages, or tokens - use list_components, list_packages, or get_style_tokens for those.

  ConnectorNo auth

• sm_list_projectsA

  Space Monkey Mailchimp DashboardA

  Resolve which Space Monkey projects this API key can read. Call this first when the user names a company rather than a project ID, and match on companyName — never silently mix projects.

  ConnectorOAuth

• sm_list_projectsA

  Space Monkey Mailchimp DashboardA

  Resolve which Space Monkey projects this API key can read. Call this first when the user names a company rather than a project ID, and match on companyName — never silently mix projects.

  ConnectorNo auth

• search_opportunitiesA

  FoundareeA

  Search public openings on Foundaree: jobs, freelance work, internships, projects, co-founder and advisory roles. Use it when the user is looking for work or a role ("React jobs in Bengaluru", "a co-founder role in fintech", "internships in design"), or asks what a company is hiring for. Matches the title, description, city and skills. Only open listings are returned unless `includeClosed` is true. Returns JSON with `items` (each: `username`, `title`, `type`, `companyUsername`, `location`, `description`, `skills`, `status`, `listingUrl`, `companyUrl`) and `total`. People apply on the listing page on Foundaree; this tool does not apply for anyone. Foundaree is new, so there may be few or none: say so rather than guessing.

  ConnectorNo auth

• list_workspacesA

  QuillHubA

  List the user's workspaces AND the projects inside each workspace — projects are returned nested, so this is also the tool for finding a `project_id` (there is no separate list_projects tool). Call it first whenever another tool needs `workspace_id` or `project_id` (`list_transcriptions` filters, `find_subjects`, `list_open_questions`, `search_meeting_transcripts`). Returns id, name, type (personal/team), your role, and per-project recording counts. Cheap — one small response.

  ConnectorOAuth

• ads_search_advertisersA

  Manifold MCPA

  The advertisers matching a brand name in Google's ad library, with their ids. Use when: before ads_get_advertiser_ads on Google, because that library is keyed by advertiser id and one brand has one entry per region. Not for: the ads themselves, use ads_get_advertiser_ads with the id this returns. The other libraries, which search their ads directly with ads_search_ads. Returns: List. rows[]: platform, id, name, region, ads_estimate, website. Cost: 1 credit. Cached 7 days. Example: {"platform": "google", "query": "lululemon", "region": "US"}

  ConnectorAPI key

• lab_list_projectsA

  FilmLabA

  List FilmLab projects (id, title, current pipeline stage). Call this first to find a project_id for the other tools. Shows up to 20 items; `total` counts your active projects (up to 200) and `truncated: true` means the list is cut off — sorted by last change, so older projects drop out of the shown window first.

  ConnectorOAuth

• validate_postA

  Multi Upload ToolA

  Dry run of create_post: takes the same arguments and runs the same checks (account status, plan, daily caps, monthly quota, queue room, caption and title limits, required platformSettings, scheduling window) without publishing anything. Call it before create_post on any batch, or whenever unsure — a post rejected here would otherwise fail later, sometimes hours later for scheduled posts. mediaUrls are not downloaded: file format, size and duration are only checked when the post is actually published. Returns: { valid, errors: [{ accountId, platform, error }], targets: [{ accountId, platform, scheduledFor }] }. An error with accountId null applies to the whole batch.

  ConnectorOAuth