"A server for Shopify development tools and API integration" matching MCP tools:

• publish_articleA

  BlogSEOA

  Queues an article for publishing to one of the website's connected integrations (WordPress, Shopify, Webflow, webhook...). It goes live on the site unless that integration is set to draft mode. When provider is omitted and exactly one integration is eligible it is used; otherwise the eligible options are returned. Eligibility: generated or failed-to-publish articles can go to any active integration; an article published in draft can only be re-pushed to its own CMS; a live article can only be re-sent to a webhook (use sync_article_to_cms to push edits to a CMS). Asynchronous: the publish runs in the background within a few minutes; poll get_article until status is published or the status label reads Failed to publish. Pass confirm=true once the user has approved; without it the tool only returns where the content would be published and whether it goes live. Pass website_id when the account has several websites (see get_account).

  Connector

  Destructive

  OAuth

• get_technologiesA

  AgentDataA

  Use this when the user asks which companies use a particular technology (for example Intercom, Zendesk, HubSpot, Shopify, Stripe), or which technologies are most used. With a slug: companies detected using that technology, 20 per page. company_count is every company detected using it; listed_count is how many the list can page through, so stop at page ceil(listed_count / 20). Without a slug: the technology index, most-used first, with company counts (default 100, up to 1,000). Slugs are lower-case with hyphens, e.g. intercom, hubspot, google-analytics, shopify. Works without an API key; no contact reveals.

  ConnectorNo auth

• nsw_da_search_applicationsA

  NSW Development Applications (x402)A

  Search NSW development applications by council, suburb, postcode or lodgement date, newest lodgement first. Returns up to 100 development applications per call with address, status, cost, dwellings, storeys and development types, plus has_more for paging with offset. status, application_type, development_type and min_cost must be combined with council, suburb or postcode. Use get_application for the full record of a result. Costs $0.01 per call, paid via x402 in USDC on Base; clients without x402 support receive the payment requirements as an error result. Failed calls are not charged. Source: NSW Department of Planning, Housing and Infrastructure (NSW Planning Portal), CC BY 4.0.

  ConnectorNo auth

• query_integrationA

  spacesheepB

  Read data through the integrations this person's spacesheep agent can use: connected MCP servers (Granola meeting notes and transcripts, and any other server added under Settings → Integrations), OAuth accounts (Google Calendar, Linear, Zoom), Stripe, and pasted-key APIs (web search, Apify, Mixpanel, custom). Credentials stay on spacesheep's side; the call goes through the same path the agent uses. With no integration: the list of what is connected, each with how to call it. With integration plus path (and body, method, account or url as its line says): one call. For an MCP server, path is a tool name and body its arguments; path "tools" lists its tools. For a REST API, path is relative to its base. Read only: a call that could change something (a write method, or an MCP tool the server doesn't mark read-only) is refused and nothing is sent. Available with a spacesheep API key the person created, not over an OAuth connection.

  ConnectorOAuth

• shop_requestA

  ecomdlyA

  Call the API of a connected e-shop (Shoptet, Upgates, Shopify, WPJ Shop, WooCommerce, PrestaShop, Shoper, Shopware, Magento, BigCommerce, IdoSell) — ecomdly adds the owner's API access, you never see or need the key. Follow the platform's skill (shop_list names it) for paths and limits, and for the job itself (product titles, descriptions, translations, prices, stock, feeds) a skill from the ecomdly catalog — search_skills first, before you change products. `path` is relative to the API (Shoptet: /api/orders?page=1, Upgates: /orders?page=1, Shopify: /graphql.json and WPJ Shop: /admin/graphql/ with a POST body {"query": …}, WooCommerce: /orders?per_page=50, PrestaShop: /orders?display=full, Shoper: /orders?limit=50, Shopware: /search/order with a POST body of criteria, Magento: /V1/orders?searchCriteria[pageSize]=50, BigCommerce: /v2/orders?limit=50 or /v3/catalog/products, IdoSell: /orders/orders/search with a POST body {"params": {…}}). Reading always works (GET, GraphQL queries, Shopify bulk queries, Shopware and IdoSell searches, a Shoper bulk of GETs); changes (other POST/PUT/PATCH/DELETE, GraphQL mutations) only where the owner allowed them on ecomdly, and only what the owner confirmed in this conversation. For a custom API you sign in yourself as its docs say, writing {{secret}} where the key goes (headers, path or body). Returns the status, the limit headers and the body (long bodies are cut — page through, or use a snapshot / bulk query).

  ConnectorNo auth

• site_draftA

  GemmeinA

  Opens a draft of the app's Development site — its frontend: HTML, CSS, JavaScript, images, fonts, served as static files at https://<slug>-dev.gemmein.dev, a private preview. Returns a draftId for site_put_file and site_publish. A draft carries the files the Development site serves now, so an edit sends only the files that changed — site_read returns a file's current contents to edit; site_publish can also take files away (remove) or publish the draft's files alone. Static files only: server code (a Node server, an API route, server-side rendering) is not hosted here — server logic runs in relays (call_url) or on the app's own server. The page loads the Gemmein SDK from the site itself: import { gemmein } from "/__gemmein/sdk.js". Development only.

  ConnectorNo auth

• get_integration_statusA

  ReploB

  Check one integration's connection status in the selected Replo project. Returns connected, not_connected, or needs_reconnect, along with a dashboard URL for setup when available. externalAnalytics lists supported SQL views and their maximum cache age, not proof the connection can fetch metrics. Check this before querying external metrics, including when a provider's tools are absent from your catalog. Analytics integration keys include triple-whale, contentsquare, intelligems, google-analytics, google-search-console, shopify, and converge. connectFailureMessage explains a failed connection attempt. isAlwaysAvailable identifies a built-in integration; isSettingsManaged identifies setup in integration settings. This tool does not connect an account or change permissions.

  ConnectorNo auth

• get_integration_statusA

  ReploB

  Check one integration's connection status in the selected Replo project. Returns connected, not_connected, or needs_reconnect, along with a dashboard URL for setup when available. externalAnalytics lists supported SQL views and their maximum cache age, not proof the connection can fetch metrics. Check this before querying external metrics, including when a provider's tools are absent from your catalog. Analytics integration keys include triple-whale, contentsquare, intelligems, google-analytics, google-search-console, shopify, and converge. connectFailureMessage explains a failed connection attempt. isAlwaysAvailable identifies a built-in integration; isSettingsManaged identifies setup in integration settings. This tool does not connect an account or change permissions.

  ConnectorNo auth

• connect_integrationA

  AideA

  Start connecting Gmail, Shopify, Zendesk, Front or Gorgias. Returns a dashboard `url` that opens the sign-in for that service, and `tellUser`: give the user both, then check get_setup_status once they are done. Pass Zendesk `subdomain`, Gorgias `account` or Shopify `shop` when known; otherwise the page asks. Helpdesks (Zendesk, Front, Gorgias) need the Pro plan (`plan_feature_unavailable` otherwise); set_up_helpdesk finishes one once connected.

  ConnectorOAuth

• bank_accountsA

  Inferventis — Financial Data, News & Web MCPA

  Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

  ConnectorNo auth

• bank_accountsA

  Inferventis MCP ServerA

  Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

  ConnectorNo auth

• intel_stackA

  TunnelMind Data APIB

  Fetches up to 32KB of the domain's HTML and response headers from the edge, then fingerprints the content for known CMS platforms, JavaScript frameworks, CDN providers, and analytics tools. Detection is based on meta generator tags, script src patterns, response headers, and cookie names. Use this tool when: - You need to know what CMS (WordPress, Drupal, Shopify) a site runs. - You are assessing a domain's infrastructure before a security review. - You want to identify analytics or marketing tools a site embeds. Do NOT use this tool when: - You want HTTP headers and security posture — use `intel_http` instead. - You want tracker database classification — use `get_domain` instead. - You need robots.txt AI policy — use `intel_robots` instead. Inputs: - `domain` (query, required): Domain to fingerprint. Returns: - `cms`: detected content management system, or null. - `frameworks`: JavaScript/backend frameworks detected. - `cdn`: CDN provider detected, or null. - `analytics`: analytics and tracking tools detected. - `meta_generators`: raw meta generator tag values. Cost: - Free. No API key required. Latency: - Typical: 2-4s (HTML fetch), p99: 7s.

  ConnectorNo auth

• disable_connectorA

  CorpusIQC

  Hide a connector's tools from the active tool list for the current user. Use when the user says they don't use a service or wants to pause a connector, such as 'disable Shopify' or 'hide TikTok'. The connector remains configured and can be restored with enable_connector. Disabled connectors still appear in get_connector_status marked Paused.

  ConnectorNo auth

• pingA

  mcp-serverA

  Verify the connection to Debitura and show which creditor account the API key belongs to. Call this first to confirm the integration is set up correctly.

  ConnectorNo auth

• pingA

  DebituraA

  Verify the connection to Debitura and show which creditor account the API key belongs to. Call this first to confirm the integration is set up correctly.

  ConnectorNo auth

• delete_api_keyA

  Timix.AIA

  Permanently revoke one of your Integration API keys. Any MCP clients or integrations using the key will lose access immediately and cannot be restored. Returns a preview; re-call with the confirm_token and an idempotency_key to commit.

  ConnectorNo auth

• roki_validate_requestA

  ROKI ConnectA

  Validate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces. Critical for this API: it ignores unknown fields and returns 201, so a typo produces a misconfigured payment rather than an error. The response names what it dropped in `warnings`, but by then the payment exists - validating here means it is never created. Always validate before writing or shipping integration code.

  ConnectorNo auth

• list_examplesA

  EpsilonA

  List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.

  ConnectorAPI key

• get_god_promptA

  GodPrompt MCP ServerA

  Returns the complete GodPrompt.md — a single-file universal system prompt for AI software development (47KB, ~1145 lines). Use this when you want the full payload in one shot. For progressive disclosure (smaller context), use get_core_skill and the reference tools instead.

  ConnectorNo auth

• nsw_da_get_summaryA

  NSW Development Applications (x402)A

  Get free counts of NSW development applications by status, application type and council. Call this first: it shows how many development applications are loaded, the exact council names the other tools accept, and the status and application type values. Optional filters narrow the counts. Counts refresh every 6 hours while the history backfill extends coverage back to 2018. Free, no payment needed. Source: NSW Department of Planning, Housing and Infrastructure (NSW Planning Portal), CC BY 4.0.

  ConnectorNo auth

• get_unified_connection_mcp_urlA

  Unified.to MCP ServerB

  Get the MCP remote server URL for a specific connection ID. Returns a ready-to-use, connection-scoped Streamable HTTP MCP endpoint that exposes that connection's integration-specific tools. Authenticate with a workspace API key to use this. The URL embeds a credential and grants tool access without a further login, so treat it as a secret. It does NOT expire on its own. Revocation depends on the mode (see the `mode` parameter): an 'api'-mode URL carries the workspace API key and is revoked by rotating that key (which affects every URL that used it); a 'user'-mode URL is scoped to this one connection and is revoked by deleting the connection. Optional server options (permissions, tools, aliases, defer_tools, hide_sensitive, include_external_tools) are baked into the returned URL as query parameters.

  ConnectorNo auth