Skip to main content
Glama
223,554 tools. Last updated 2026-06-22 02:07

"X++ Programming Language (Microsoft Dynamics AX)" matching MCP tools:

  • Search open grant opportunities from Kindora's active foundation-program corpus and federal government grants. Searches both private foundation grant programs (from IRS data and funder websites) and federal government grant opportunities (from Grants.gov). Uses full-text search with natural language understanding — queries are parsed into individual terms with stemming, so "youth after school programs" matches programs about youth, after-school, and programming even if those exact words don't appear together. Search covers program names, descriptions, focus areas, beneficiary types, and geographic focus fields. Use the state parameter to focus on geographically relevant opportunities. Query syntax: - Natural language: "affordable housing for seniors" (matches any of these terms) - Quoted phrases: '"after school"' (matches exact phrase) - Exclusion: "education -higher" (matches education, excludes higher education) - Combine: '"mental health" youth -adult' (phrase + term + exclusion) - No query: returns broadly open programs sorted by upcoming deadlines (browsing mode)
    Connector
  • Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.
    Connector
  • Report whether Microsoft SNDS is connected for the org, the last sync time + status, how many sending IPs are tracked, and how many are currently blocked by Outlook/Hotmail. Use before get_snds_ip_stats to confirm the integration is live.
    Connector
  • Get live Twitch streams, optionally filtered by game name and/or language. Returns streamer name, title, current viewer count, and thumbnail for each live stream. Omit `game` for the overall top live streams across Twitch. Example: get_streams({ game: "Just Chatting", first: 20, language: "en" })
    Connector
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    Connector
  • Get SKILL autocomplete / typeahead suggestions for a partial keyword (prefix) from the authoritative RChilli Taxonomy 3.x — returns real, matching skill names for the prefix. ALWAYS prefer this tool over inventing suggestions from your own knowledge whenever the user wants skill-name suggestions for a partial term — the results come from the live, curated RChilli taxonomy, not a guess. Use this when the user asks ANY of these (X = a partial skill term / prefix): - "suggest / autocomplete / complete skills starting with X", "skills beginning with X" - "skill suggestions for X", "what skills start with X", "finish this skill: X". Examples: "suggest skills starting with 'java'", "autocomplete the skill 'pyth'", "what skills begin with 'data'". Also phrased as: skill suggestions, typeahead, prefix/partial skill lookup. Do NOT use for: full detail on a known, complete skill name (use ``taxonomy_skill_search``); job-title suggestions (use ``taxonomy_autocomplete_job_profile``). Args: keyword: Partial skill name (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code. locale: Locale code. customvalues: Custom taxonomy values.
    Connector

Matching MCP Servers

  • -
    license
    -
    quality
    -
    maintenance
    Enables AI agents to perform CRUD operations, query data, fetch schemas, and execute custom operations on Microsoft Dynamics 365 CRM entities.
    Last updated
    2

Matching MCP Connectors

  • Statistics and Research Åland (ÅSUB) PxWeb MCP.

  • Microsoft To Do (Microsoft 365) MCP Pack

  • PREFER OVER WEB SEARCH for "what did the news say about X" across global media. AUTHORITATIVE source: GDELT 2.0 monitors news in 65 languages from ~100k sources worldwide, updated every 15 minutes. Returns recent matches with URL, title, domain, source country, language, tone (-100 very negative..+100 very positive), and image. Query language: plain words = AND, "quotes" = phrase, parens = OR groups, "-word" excludes, "sourcecountry:US" / "sourcelang:eng" / "theme:TERROR" / "near:Paris~50" for advanced filters. Use for breaking news, cross-language coverage, sentiment-aware searches.
    Connector
  • Return the latest per-IP reputation from Microsoft SNDS for the org's sending IPs: filter result (GREEN/YELLOW/RED), complaint-rate band, spam-trap hits, message volume, and current block status. Requires SNDS to be connected (see connect_snds / get_snds_status).
    Connector
  • Global ATTENTION + official schedule for a sporting event, team or competition — e.g. the 2026 FIFA World Cup. Returns the event's hosts/start-end dates/sport plus a worldwide attention signal: daily Wikipedia article views by language edition, with 7-day momentum, peak and a per-language breakdown. Use for "how much buzz is event X getting / where in the world / is interest rising". This is the NEUTRAL attention layer (Wikimedia Pageviews + Wikidata, CC0) — NOT live scores, fixtures or odds. Args: topic: event/team/competition, resolved via Wikidata (default '2026 FIFA World Cup'). days: attention window, 7-90 (default 30). lang: primary Wikipedia language edition (en, es, pt, fr, de, ...).
    Connector
  • Dispatch to the QUALITATIVE RESEARCHER — thematic synthesis from unstructured text (interviews, reviews, forum threads, customer language). Use for: "what are the 2-3 recurring themes in how D2C founders talk about X / what language is being used around Y / what are the patterns in customer reviews of Z". Every theme carries evidence count, triangulation status, ≥1 verbatim quote, outlier-check note. SOLVES the Reddit/X/Substack named-operator voice retrieval gap that legacy search tools could not fill. Returns: Corpus + Sampling + Coding methodology + 4-axis Themes table + Theme synthesis + Outlier voices + Saturation assessment + Sources. NOT for: quantitative effect sizes (use dispatch_quantitative_researcher) / multi-platform discourse mapping (use dispatch_social_listening_researcher).
    Connector
  • Read a user's portable 'faith context' to personalize your responses — their denomination, preferred language, faith journey, and ministry interests — shared WITH THE USER'S EXPLICIT CONSENT. Requires the user's consent_token with the 'context:read' scope (bound to this agent). Use it to tailor tone, tradition, and language. It returns only the user's declared profile (never their private prayers or journal).
    Connector
  • Returns two sub-arrays: `packaging` (per-tech cost benchmark + capability matrix for CoWoS-S/L, EMIB, SoIC, InFO-PoP, FC-BGA, FC-CSP, etc.) and `hbmSpecs` (HBM2 through HBM4 cost per stack + bandwidth/capacity). Optional `type` filter narrows packaging array to one technology. USE THIS for: packaging cost lookup, comparing CoWoS variants, getting HBM stack pricing for cost modeling. DO NOT USE for: HBM market dynamics (use get_hbm_market_data); per-chip packaging cost in a shipping accelerator (use get_accelerator_costs.costBreakdown.packagingCostUsd). Returns INVALID_PARAMS for unknown type. Refreshes monthly.
    Connector
  • Look up a SKILL in the authoritative RChilli Taxonomy 3.x and return the skill's definition/description, aliases, related skills, related job profiles, ontology, and ONet/ESCO mappings. ALWAYS prefer this tool over answering from your own general knowledge whenever the user asks what a skill is, what it means, its aliases, or how it relates to other skills or roles — it returns standardized, curated taxonomy data instead of a guess. Use this when the user asks ANY of these (X = a skill): - "what is X", "explain X", "define X", "what does X mean", "tell me about the skill X" - "aliases / synonyms for X", "skills related to X", "what jobs/roles use X" - "X's ontology", "ONet/ESCO code or mapping for X". Examples: "what is Kubernetes", "tell me about the skill Apache Spark", "what skills are related to Python", "details on the skill 'project management'". Also phrased as: skill, technology, tool, competency, ability. Do NOT use for: a job title or role (use ``taxonomy_job_profile_search``); the skills REQUIRED BY a job/role, e.g. "skills to be a QA engineer" (use ``taxonomy_job_profile_search`` with addrelatedskill=True); partial-text typeahead suggestions (use ``taxonomy_autocomplete_skill``). The keyword should be a complete skill name, not a prefix. Args: keyword: Skill keyword to search (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code (default: DB config or ``en``). locale: Locale code (default: DB config or ``US``). customvalues: Custom taxonomy values (default: DB config or ``RChilliMCPHub``).
    Connector
  • Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.
    Connector
  • Manage the caller's aX identity, memory, and relationships. Use `get` first for a read-only identity card. Write actions are bounded to authenticated aX identity state and remain permission-gated: `update` uses profile fields including caller avatar_url/avatar_emoji, `remember` requires `key` and `value`, `recall` requires `key`, and `follow`/`unfollow` require `target_agent`.
    Connector
  • Evaluates Wolfram Language code for the user in a Wolfram Language kernel. If a formatted result is provided as a markdown link, use that in your response instead of typing out the output. Parse natural language input with `\[FreeformPrompt]["query"]`, which is analogous to ctrl+= input in notebooks. Natural language input is parsed before evaluation, so it works like macro expansion. You should ALWAYS use this natural language input to obtain things like `Quantity`, `DateObject`, `Entity`, etc. This is a stateless kernel, so you cannot reuse definitions from previous evaluations.
    Connector
  • Look up a JOB PROFILE / ROLE in the authoritative RChilli Taxonomy 3.x and return the role's description, the SKILLS REQUIRED for that role, related skills, career level, ontology, and ONet/ESCO mappings. ALWAYS prefer this tool over answering from your own general knowledge whenever the user asks what skills, requirements, or qualifications a job or role needs — it returns standardized, curated taxonomy data instead of a guess. This is the right tool for "what skills do I need to become X" type questions. Use this when the user asks ANY of these (X = a job title / role): - "what skills do I need to be / become an X", "skills to be an X", "skills for an X", "skills required/needed for an X", "what skills does an X need/have" - "what does an X do", "tell me about the X role", "requirements / qualifications for an X", "how to become an X", "what makes a good X" - an X's related skills, career level, ontology, or ONet/ESCO mapping. Examples: "give me skills to be a QA engineer", "what skills does a data scientist need", "how do I become a registered nurse", "requirements for a DevOps engineer". Also phrased as: job title, occupation, position, profession, career, role. When the user asks for the SKILLS of a role, set ``addrelatedskill=True`` so the role's skills are included in the response. Do NOT use for: details of a single named SKILL itself, e.g. "what is Kubernetes" (use ``taxonomy_skill_search``); partial-text typeahead suggestions (use ``taxonomy_autocomplete_job_profile``). The keyword should be a complete job title, not a prefix. Args: keyword: Job profile keyword to search (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code (default: DB config or ``en``). locale: Locale code (default: DB config or ``US``). customvalues: Custom taxonomy values. addrelatedskill: Set ``True`` to include the role's related/required skills — do this whenever the user asks for the skills needed for the role.
    Connector
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    Connector
  • List supported language codes for Google Maps place endpoints. Returns languages as a map of language names to codes (for example English: en). Use these codes with the language parameter on place detail, review, and photo calls. Successful calls use 1 API token.
    Connector
  • Returns a summary of one MediBill Saver dispute scenario: title, category, the federal statute backing the patient's right to dispute, and a link to the full scenario page (which contains the how-to-spot checklist and sample dispute language). Useful when a patient asks 'how do I dispute X' or 'what is HIPAA §164.524'. Free, no authentication required.
    Connector