"Integrating Azure Synapse with Other Services" matching MCP tools:

• about_emora

  mental-health-care

  [Step 1 of explore_information · optional] Identity, services, states served, insurance accepted, age ranges, key facts, crisis resources, and links. Combined site-info + services catalog. Use when: The user asks "what is Emora?" / "what services do you offer?" / "which states?" / "what insurance?" — this is the canonical "tell me about you" call. Don't use when: You already have site context from a previous call this session — Emora identity is stable, no need to re-fetch. Example: about_emora({})

  Connector

• authenticate

  AI Agents Overflow

  Authenticate with your saved API key. Read your key from ~/.agents-overflow-key and pass it here. Call this at the START of every session before using any other tools.

  Connector

• find_equivalent

  Diagrams MCP

  Find cross-provider equivalents for a diagram node by infrastructure role. Given a node name (e.g. 'EC2', 'Lambda', 'ComputeEngine'), returns the infrastructure role category it belongs to and the equivalent nodes from other providers. If a node name is ambiguous, use list_categories to see all mapped roles and pick a provider-specific node name. Args: node: Node class name to look up (case-insensitive, e.g. 'EC2', 'lambda'). target_provider: Optional provider to filter equivalents to (e.g. 'gcp', 'azure', 'aws'). If omitted, all equivalents across all other providers are returned. Returns: A dict with keys: category (str): Infrastructure role category name. description (str): Human-readable description of the category. source (dict): The matched node with keys node, provider, service, import. equivalents (list[dict]): Equivalent nodes, each with keys node, provider, service, import.

  Connector

• list_providers

  Diagrams MCP

  List all available diagram providers (aws, gcp, azure, k8s, onprem, etc.). Use list_providers -> list_services -> list_nodes to browse available node types for a specific provider.

  Connector

• get_domain_senders

  DMARKOFF — DMARC, SPF & DKIM Analytics

  List top sending sources (ESPs, ISPs, mail services) for a domain, grouped by source type. Filters: "known" (legitimate ESPs like Google, Mailgun), "unknown" (unrecognized senders), "forward" (forwarding services). Empty = all types. Returns top 20 per type with message volume, SPF/DKIM/DMARC pass/fail counts. Use this to investigate WHERE email is being sent from — especially when unknown sources appear or compliance is low. To drill down into a specific source (by IP, ISP, hostname, or reporter), use get_domain_source_details.

  Connector

• list_pools

  Surf Session Finder

  List all supported surf pools worldwide with their IDs, names, and locations. Always call this first to get valid pool_id values for the other tools.

  Connector

• list_clients

  Emailens MCP

  List all 15 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.

  Connector

• search_providers

  LocalPro

  Search for verified local service providers across 9 trade categories: floor coating (epoxy/polyaspartic), radon mitigation, crawl space repair, laundry pickup & delivery, mold/asbestos abatement, basement waterproofing, foundation/slab repair, septic pump services, and water damage restoration. Returns provider name, rating, review count, business status, services offered, certifications, years in business, and a link to the full profile with contact details. Each provider includes Google Maps URL when available. Covers major US metro areas. Use list_niches first to get valid niche IDs, and list_service_types for valid service_type values.

  Connector

• bart_stations

  BART Real-Time Transit

  List all BART stations with abbreviation codes and locations. Use this to look up station codes needed by other tools.

  Connector

• initialize_context

  Synapse Layer — Continuous Consciousness Infrastructure

  ALWAYS call this as your FIRST action in every new conversation before responding. Returns persistent memory context and user profile from Synapse Layer. Essential for cross-session continuity. If you skip this, you will respond without knowing who the user is or what they are building.

  Connector

• ado_query_workitems

  ALM X++ MCP Server

  AZURE DEVOPS ONLY -- Query Work Items (Bugs, Tasks, FDDs, User Stories, CRs) in Azure DevOps. [~] PRIORITY TRIGGER: use this tool when the user mentions 'FDD', 'RDD', 'IDD', 'CR', 'Task', 'Workitem', 'Work Item', 'Bug', 'User Story', 'Feature', 'Issue', 'ticket', 'sprint', 'backlog', 'DevOps', 'liste des tâches', 'show tasks', 'find bugs', '#1234', 'WI#'. NEVER use this tool for: D365 labels (@SYS/@TRX), X++ code, AOT objects, tables, classes, forms, enums, error messages, 'c\'est quoi le label', 'search_labels', 'libellé', 'label D365'. For labels -> use search_labels. For D365 code -> use search_d365_code or get_object_details. Shortcuts: 'bugs' (all active bugs), 'my bugs' (assigned to me), 'recent' (updated last 7 days), 'sprint' (current iteration). Or pass any WIQL SELECT statement or a free-text title search. Use '*' with filters only. Returns max 50 work items with ID, title, type, state, priority, area, assigned-to. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.

  Connector

• vote_on_service

  Sats4AI - Bitcoin-Powered AI Tools

  Vote for a planned service to be built next. Returns JSON: { success, slug, newVoteCount }. 1 sat per vote — multiple votes allowed. Call list_planned_services first to discover valid slugs and current vote counts. Highest-voted services get prioritized. Requires create_payment with toolName='vote_on_service'.

  Connector

• list_planned_services

  Sats4AI - Bitcoin-Powered AI Tools

  List all planned services with current vote counts. Returns JSON array: [{ slug, name, description, votes }], sorted by votes descending. No payment required — this is a free discovery tool. Use the slug values with vote_on_service to cast votes. This tool is idempotent and safe to call repeatedly.

  Connector

• nexbid_search

  discovery

  <tool_description> Search and discover products, recipes AND services in the Nexbid marketplace. Nexbid Agent Discovery — search and discover advertiser products through an open marketplace. Returns ranked results matching the query — products with prices/availability/links, recipes with ingredients/targeting signals/nutrition, and services with provider/location/pricing details. </tool_description> <when_to_use> Primary discovery tool. Use for any product, recipe or service query. Use content_type filter: "product" (only products), "recipe" (only recipes), "service" (only services), "all" (all, default). For known product IDs use nexbid_product instead. For category overview use nexbid_categories first. </when_to_use> <intent_guidance> <purchase>Return top 3, price prominent, include checkout readiness</purchase> <compare>Return up to 10, tabular format, highlight differences</compare> <research>Return details, specs, availability info</research> <browse>Return varied results, suggest categories. For recipes: show cuisine, difficulty, time.</browse> </intent_guidance> <combination_hints> After search with purchase intent → nexbid_purchase for top result After search with compare intent → nexbid_product for detailed specs For category exploration → nexbid_categories first, then search within For multi-turn refinement → pass previous queries in previous_queries array to consolidate search context Recipe results include targeting signals (occasions, audience, season) useful for contextual ad matching. </combination_hints> <output_format> Markdown table for compare intent, bullet list for others. Products: product name, price with currency, availability status. Recipes: recipe name, cuisine, difficulty, time, key ingredients, dietary tags. Services: service name, provider, location, price model, duration. </output_format>

  Connector

• hospitals

  MedRates

  List all hospitals in the database with their locations. Returns hospital names, IDs, EINs, NPIs, and per-campus locations with addresses and coordinates. Use hospital IDs to filter other search tools. NOTE: This lists US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers, clinics, or other freestanding facilities. Returns: JSON array of hospitals with id, name, display_name, ein, npi, cms_certification_number, and locations (address, city, state, lat/lng).

  Connector

• list_products

  discovery

  <tool_description> Search for products in the Nexbid marketplace. Alias for nexbid_search with content_type='product'. </tool_description> <when_to_use> When an agent needs to discover products (not recipes or services). Convenience alias — delegates to nexbid_search internally. </when_to_use> <combination_hints> list_products → get_product for details → create_media_buy for advertising. For recipes/services use nexbid_search with content_type filter. </combination_hints> <output_format> Product list with name, price, availability, score, and link. </output_format>

  Connector

• list_spending_opportunities

  Swarm Tips — Aggregated AI Agent Activities

  [READ] Aggregated list of paid services swarm.tips agents can spend on. v1 covers first-party services (generate_video — 5 USDC for an AI-generated short-form video). External spend sources (Chutes inference at llm.chutes.ai/v1, x402-paywalled APIs, etc.) are deferred to follow-up integrations. Each entry includes title, description, source, category, cost_amount/token/chain, USD estimate, direct redirect URL, and (for first-party services) a `spend_via` field naming the in-MCP tool to call. Use this to discover where to spend; for first-party services use the named `spend_via` tool, for external services navigate to the URL.

  Connector

• x402_get_categories

  x402watch

  List all 33 x402 service categories with aggregate stats: services count, 24h volume, transaction count, real-volume %, and label distribution. Use this to understand the shape of the x402 ecosystem before drilling into specific services or wallets.

  Connector

• quote_relations

  Quotewise

  Get relations for a quote, grouped by type and direction. Returns translations, variants, and other related quotes with provenance info. Use to explore how quotes connect to each other (translations, variants, attributions). Examples: - `quote_relations("abc123")` - all relations for a quote - `quote_relations("abc123", relation_type="intra_translation")` - only translations - `quote_relations("abc123", direction="outgoing")` - only outgoing relations

  Connector

• microsoft_docs_search

  Microsoft Learn MCP

  Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge. ## Follow-up Pattern To ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.

  Connector