Skip to main content
Glama
810,443 tools. Updated 2026-11-20 05:54

"A server for exploring the concept of superpowers" matching MCP tools:

  • Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B). query_ckg walks outward from one concept. This intersects the reachable sets of two or more, which is the shape of most real questions — "the component that satisfies A AND applies to B". Neither anchor alone answers it; the answer lives in the overlap. Every branch is an exact set of declared edges, so the intersection is exact. A concept appears only if a declared path reaches it from each anchor. A relation missing from the graph produces an empty result, never a guess. Args: branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes everything within `depth` hops, or an anchor plus an explicit relation path using '>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the frontier. '*' matches any relation. Mix both forms freely. depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths. direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default). mode: 'AND' (default) intersects branches; 'OR' unions them. limit: Max concepts listed, 1-200 (default 40). The true count is always shown. Returns: Markdown with the query plan and its per-step set sizes, then the answer set with taxonomy tags. Reports which branch was empty when the intersection is empty.
    ConnectorNo auth
  • Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B). query_ckg walks outward from one concept. This intersects the reachable sets of two or more, which is the shape of most real questions — "the component that satisfies A AND applies to B". Neither anchor alone answers it; the answer lives in the overlap. Every branch is an exact set of declared edges, so the intersection is exact. A concept appears only if a declared path reaches it from each anchor. A relation missing from the graph produces an empty result, never a guess. Args: branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes everything within `depth` hops, or an anchor plus an explicit relation path using '>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the frontier. '*' matches any relation. Mix both forms freely. depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths. direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default). mode: 'AND' (default) intersects branches; 'OR' unions them. limit: Max concepts listed, 1-200 (default 40). The true count is always shown. Returns: Markdown with the query plan and its per-step set sizes, then the answer set with taxonomy tags. Reports which branch was empty when the intersection is empty.
    ConnectorNo auth
  • Hybrid search — combines keyword + semantic search via RRF. Uses Reciprocal Rank Fusion (RRF) to merge exact-word results with meaning-based results. **This is the recommended tool for "discourses about X" / concept queries**, because the semantic side catches suttas that discuss a concept using different vocabulary (e.g. some mindfulness-of-breathing suttas use `assasati/passasati/dīghaṁ` instead of `ānāpānassati`). ⚠️ **Send the question and nothing else. Do not pad the query.** The whole string becomes one vector, so every word you add moves it. Appending your own candidate terms — synonyms, Pāli equivalents, a keyword list — searches for the blend, not for the question. Measured on `Buddha flies in the sky`: asking it plainly put the right passage at **rank 1** (3 relevant suttas). Appending three guessed Pāli terms (`buddha, agga, sagga`) pushed it down to **rank 5** and left only 1 — because `agga` (supreme) and `sagga` (heaven) drag the vector toward their own meanings. Have candidate terms worth searching? Give them their own `search_by_keyword` call and merge the two result lists. One tool asks what a passage means, the other asks where a word occurs; combined into a single string they cancel out. Rewriting the question to sound more canonical does not help either — the same query phrased as `rose into the air and flew like a bird` scored **zero** relevant hits. 💡 **Hints for the AI client:** - English queries usually work best (e.g. `mindfulness of breathing`) because the embedding model is multilingual but EN-primary. - Thai stop-word handling is weak. If a Thai query underperforms, the AI client should translate to Pāli/English first (see server instructions). - The default `limit=5` is often too small for a topic survey — use `limit=15-20` (max 20) for good coverage. - `language` only chooses what comes back; it does not change what matches or how results are ranked. - Looking for a concrete thing rather than a concept (an animal, an object, a place)? `search_by_keyword` over `language="english"` is often better. The translations are segment-aligned to the Pāli, so one search for `turtle` finds every turtle passage whatever the Pāli underneath says (`kacchapa`, `kumma`, `maṇḍūkakacchapa`), and each hit still carries its segment id. - Ranking is by similarity, NOT canonical importance — locus classicus suttas (e.g. MN118, DN22) may rank below smaller suttas that happen to use the exact vocabulary. Treat results as a starting point, then call `get_sutta` for the canonical references.
    ConnectorNo auth
  • Which verifier: one fact_id → verify_fact_lineage; a list of fact_ids or derived_ids → verify_facts; a number with no id → match_derived; a number quoted from filing text or insider/13F rows → verify_filing_figures; every number in a saved report → verify_report_figures; figures a later filing revised → check_report_figures_current. Use this tool when the user asks BOTH what a financial figure is AND which filing reported it — e.g. "What was Apple's most recently reported revenue, and which 10-Q filed it?" or "Show me the accession ID for Tesla's latest net income." Returns a single fact plus its complete filing provenance: entity, concept, period, value, accession ID, filing URL, and form type (10-K, 10-Q, etc.). Use this INSTEAD OF `search_companies` when the user already names a company and wants a financial figure with its source filing — `search_companies` only resolves identifiers and returns no financial data. Use this INSTEAD OF `get_company_fundamentals` when the user explicitly wants the filing/form type or the accession ID — `get_company_fundamentals` returns metrics across periods but omits filing provenance. Two lookup modes: (1) by fact_id (deterministic SHA-256 identity) or (2) by concept name plus a ticker (most recently reported fact). Optionally pin a point-in-time cutoff via as_of_date (YYYY-MM-DD) — returns the latest filing accepted by SEC on or before that date (no look-ahead); check `_meta.pit_safe`. DURATION: a single 10-K tags BOTH a 12-month figure and a 3-month Q4 stub at the same period_end; on a tie this returns the longer (headline) window, and every result carries `period_type` and `period_span_days` so a 3-month stub is never mistaken for the annual figure. Provide either fact_id or concept (required). Returns DATA_NOT_AVAILABLE_FOR_PERIOD if no matching fact exists (NO_FACTS_BEFORE_AS_OF_DATE when a concept was only filed after `as_of_date`). Available on all plans. FACT REFERENCE: `fact_id` also takes a fact reference, the company's 10-digit CIK, a hyphen and the fact_id (0000320193-97960097ffc0ea39388b21822abea04be91df63698bec0422f8e4327b0a5247b). A reference names its own company, so it needs no `ticker`: every lineage returns its `fact_ref`, and you may build one from a result's CIK and fact_id. Given both, `ticker` must name the reference's company or the call is refused. Third mode: `derived_id` (a `drv1:` id a tool gave you for a COMPUTED figure) re-reads the input facts, re-runs the registered formula and returns the recomputed `lineage.display` with a `derived` block listing the inputs; `verified:false` plus an `error` code says why it could not be proven. `ticker` is not needed: the id carries its own filer.
    ConnectorNo auth
  • Get Venture Insights' live service catalogue: the FREE Concept Diagnostic (a research-backed viability study of one venture concept, delivered to the founder's inbox) and the paid study tiers with live SAR prices. Call this first when your user asks what Venture Insights offers, what it costs, or whether the free diagnostic is worth requesting.
    ConnectorNo auth
  • Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    Exposes the full functionality of the Superpowers framework as MCP tools to provide AI assistants with advanced capabilities like automated planning, debugging, and parallel development. It seamlessly integrates with clients like Claude Desktop, Cursor, and Trae for an enhanced AI-driven coding experience.
    2
    5
    MIT

Matching MCP Connectors

  • Pay-per-call tools for agents: search, page reading, emails, company data, media. Sign in, no key

  • Git AOAuth

    Many AI agents on one repo, every change lands on main. Read code, propose changes, review, read CI.

  • Find TCLP content (clauses, glossary terms, guides) associated with a named concept. Unlike `search`, this performs a deterministic name match against Entity nodes in the knowledge graph rather than a relevance-ranked semantic search. Use it when you have a specific term or concept (e.g. "scope 3 emissions", "net zero") and want to retrieve every clause or glossary entry that explicitly references it. Args: name: The entity or concept name to look up (exact match, case-insensitive). limit: Maximum number of results to return (1–50). include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" and "results" where each hit includes the source content node, its plain-text `summary` (null when it has none), its `child_name` (a clause's child name, null otherwise) and the entity names that matched. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
    ConnectorNo auth
  • Find TCLP content (clauses, glossary terms, guides) associated with a named concept. Unlike `search`, this performs a deterministic name match against Entity nodes in the knowledge graph rather than a relevance-ranked semantic search. Use it when you have a specific term or concept (e.g. "scope 3 emissions", "net zero") and want to retrieve every clause or glossary entry that explicitly references it. Args: name: The entity or concept name to look up (exact match, case-insensitive). limit: Maximum number of results to return (1–50). include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" and "results" where each hit includes the source content node, its plain-text `summary` (null when it has none), its `child_name` (a clause's child name, null otherwise) and the entity names that matched. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
    ConnectorNo auth
  • WRITE ACTION — builds, modifies, or fixes an EXISTING project with a natural-language instruction. Use ONLY when the user clearly asks for a change ("add X", "fix Y", "change the theme"). If the user is only asking for advice, analysis, review, or suggestions ("what could be improved?", "review my bot"), do NOT call this — answer from the project's info instead; a review request is not an edit. Describe ONLY the desired change — DreamAgent's AI automatically handles code, tests, rebuild, and redeployment. Completed changes are saved and committed automatically. ASYNCHRONOUS: returns immediately with the session_key; monitor with dreamagent_get_edit_progress (or dreamagent_get_chat_status with the returned session key) until a terminal state. A run has succeeded only once run_status reaches 'completed'. Each edit consumes AI usage from the account's plan. ERRORS: failures are returned as tool errors. If the edit was rejected before starting, the message says 'the edit was NOT started' plus the reason — HTTP 402 insufficient usage allowance, 409 another edit already active, 423 session lock held by another session, 404 wrong project id, 401 no account connected. ONE EDIT AT A TIME: the API rejects a second concurrent edit on the same project (409); check progress and wait for the current edit. SUPERPOWERS: projects can use the account's enabled add-on AI tools. To add or use one, name the feature in the message — DreamAgent's agent knows the enabled tools and wires the integration, UI and job handling automatically. Check the catalog with dreamagent_list_superpowers; disabled tools are enabled at dreamagent.cloud → Superpowers.
    Connector
    Destructive
    No auth
  • WRITE ACTION — builds, modifies, or fixes an EXISTING project with a natural-language instruction. Use ONLY when the user clearly asks for a change ("add X", "fix Y", "change the theme"). If the user is only asking for advice, analysis, review, or suggestions ("what could be improved?", "review my bot"), do NOT call this — answer from the project's info instead; a review request is not an edit. Describe ONLY the desired change — DreamAgent's AI automatically handles code, tests, rebuild, and redeployment. Completed changes are saved and committed automatically. ASYNCHRONOUS: returns immediately with the session_key; monitor with dreamagent_get_edit_progress (or dreamagent_get_chat_status with the returned session key) until a terminal state. A run has succeeded only once run_status reaches 'completed'. Each edit consumes AI usage from the account's plan. ERRORS: failures are returned as tool errors. If the edit was rejected before starting, the message says 'the edit was NOT started' plus the reason — HTTP 402 insufficient usage allowance, 409 another edit already active, 423 session lock held by another session, 404 wrong project id, 401 no account connected. ONE EDIT AT A TIME: the API rejects a second concurrent edit on the same project (409); check progress and wait for the current edit. SUPERPOWERS: projects can use the account's enabled add-on AI tools. To add or use one, name the feature in the message — DreamAgent's agent knows the enabled tools and wires the integration, UI and job handling automatically. Check the catalog with dreamagent_list_superpowers; disabled tools are enabled at dreamagent.cloud → Superpowers.
    Connector
    Destructive
    No auth
  • WHEN: object name is unknown, partial, or you need to find by concept/keyword. Search the D365 F&O knowledge base for X++ code, tables, classes, forms, views, enums, EDTs, security objects using natural language or partial names. Returns ALL chunks (metadata, Declaration, methods) for the top-scoring objects so the LLM has complete context on the first call. Lower-scoring results return a short preview. No follow-up get_object_details call is needed for top results. NOT for listing all objects in a model -- use list_objects for that. NOT when the exact name is known -- use get_object_details for that. NEVER call search_d365_code twice in the same conversation turn. If one search did not find the object, answer from what you have -- do not repeat the search. When you need context on MORE THAN ONE concept simultaneously, use batch_search instead -- it runs all queries in parallel and is faster. NEVER call for ADO items (FDD, RDD, IDD, Bug, Task, PR, WorkItem, sprint, #1234) -- use ado_* tools instead.
    ConnectorNo auth
  • Search Vectree's library of ~95,000 interactive concept diagrams by meaning, not keywords. Vectree explains how things work as zoomable, labelled schematics — each diagram breaks a topic into nodes you can read or drill into. Use this when the user wants a diagram, a visual explanation, a systems overview, or a map of how the parts of something fit together. Describe the topic in natural language; the search is semantic, so a full question works better than a bare keyword. Results are ranked by how closely they match and by the quality of the model that generated them. Each result carries a slug — pass it to `get_diagram` for the full content of one diagram. Only public, already-generated diagrams are searched. Nothing is generated on demand, so a topic with no match simply has no diagram yet.
    ConnectorNo auth
  • Ranked unified search for equivalent terms across multiple medical terminologies. Use this tool to: - Find the same concept in different coding systems - Compare how terminologies represent a concept - Support terminology mapping and data integration Searches across: ICD-11, LOINC, RxNorm, and MeSH. Set `target_terminologies` to limit which are searched, or set `source_terminology` to exclude one (e.g. when you already have a code from that terminology and want equivalents elsewhere). The two combine: source is subtracted from targets. `limit` caps candidates per terminology (default 5, max 10). Every candidate carries `match_score` (lexical similarity to the search term, 0-1) and `rank` (global position across all searched terminologies) — both computed by this server, since upstreams don't expose comparable relevance scores. Candidates from different terminologies whose titles are lexically identical are clustered in `groups` — a strong same-concept signal (absence of a group is NOT evidence of non-equivalence). Searches upstreams in English. For official pt-BR content, use the dedicated tools: `icd11_search`/`mesh_search` accept `language: "pt"`, and `cid10_search` is natively Portuguese.
    ConnectorNo auth
  • Add an identity concept at zero usage, or add text as an alias using alias_of. Requires editor; resolution may incur embedding/judge cost. Probe first; if the text already resolves to an incumbent, offer that concept instead of blindly retrying. Aliases resolving to another concept are refused. embedding_model selects a new type's space only. Returns concept details and link; manage existing aliases with update_concept_alias. See enricher://docs/semantic-ids.
    ConnectorOAuth
  • Remove or promote a concept alias using alias IDs from get_semantic_concept. Requires editor; no LLM call. action='remove' stops that surface form resolving to this concept; removing the last alias is refused. action='set_canonical' changes its displayed form. To add an alias use add_semantic_concept(alias_of=...). Returns the outcome. See enricher://docs/semantic-ids.
    Connector
    Destructive
    OAuth
  • Search the recipe collection semantically (dense + ColBERT hybrid) to gather the members of a theme. Pass a rich natural-language concept, not just a keyword — e.g. 'cozy cold-weather baked desserts', 'bright summer salads with fresh vegetables', 'Latin American and Caribbean mains', 'anything featuring apples'. Returns up to `limit` compact hits {id,title,cuisine,dietary,cookbook}. Call once per theme concept; call again with a broader/narrower query if a group is too small or too big. Do NOT rely on cuisine labels alone — many recipes are unlabelled and only reachable by concept search.
    ConnectorOAuth
  • Search Taiwan (ROC) law articles by legal concept, keyword, or a specific article reference. Backed by a Qdrant hybrid (dense + bigram-sparse, RRF-fused) search over a curated set of major Taiwan laws and regulations (laws only, not court decisions). Use it when you don't yet know which article applies. Use get_article_by_number instead when you already know the law and article number, search_law_titles to resolve a law's official name, and search_decisions for court rulings. Returns matching articles with law name, article number, relevance and text; historical versions are marked.
    ConnectorAPI key
  • Use this when a person is exploring a travel type before choosing (where can I go, which months, what does it cost), or to get the exact slugs search_listings needs: returns the destinations, months and price ranges for ONE travel type and party. Do not use it to find specific trips: find_trips does that in one call. Required parameters (all four): - niche: ONE travel type — "ski", "golf", "surf", "diving", "hiking", "charter", "cycling", "football", "carrental", "f1", "running", "americanfootball", "yoga", "triathlon", "cruise", "coach", "holidayhome", "roundtrip", "citybreak", "dance", "wellness", "safari", "culture", "sportsevent", "camping", "hunting", "culinary", "fishing", "language", "racket", "motorcycle", "riding", "birding", "sailing", "concert", "umrah", "adventure". Single niche per call; to compare niches, call once per niche. - market: market code (one of "dk", "de", "nl", "be", "se", "gb") - adults: number of adult travelers (1-20) - children: number of children (0-20) Occupancy is required because counts and prices depend on group size — the overview is scoped to this exact cohort. Returns: - totalCount: total listings for this niche and group size - priceRange: { min, max } total price range - pricePerPersonRange: { min, max } per-person price range - averages: { price, pricePerPerson, stars, durationDays } — useful for setting expectations - dateRange: { earliest, latest } departure date range - destinationCount: total unique destinations available - availability.byMonth: array of { period: "2026-04", count, minPrice } — listings per month with cheapest price. Use this to suggest optimal travel months. - ratingDistribution: star-bracket counts - topDestinations: array of { destinationSlug, countrySlug, count, minPrice } — top 15 destinations sorted by popularity - facets: unfiltered facet counts for the main filterable fields (countries, providers, durations, etc.) Use availability.byMonth to guide users toward dates with the most options and best prices. Use topDestinations to suggest popular destinations. Use averages to set price expectations.
    ConnectorNo auth
  • Enumerate the valid values for a parameter, straight from the backend. Call this BEFORE guessing a parameter value. `kind` selects which catalog; three kinds are scoped by a query parameter (`ticker`, or `q` / `cik` / `manager_type`) and refuse the call without it: - "event_types" -> valid `event_type` for `list_realtime_events` (eps_update, company_update, biggest_mover, ...) - "financial_items" -> standardized EDGAR line items ("revenue", "operatingIncome") for a CUSTOM report's `financial_items` (`generate_report_for_stock`, or a scheduled "create-full-report" step) - "financial_ratios" -> EDGAR ratios ("grossProfitMargin") for that report's `ratios` - "as_reported_items" -> NEEDS `ticker`. The filer's OWN tagged XBRL concepts from its 10-Q / 10-K filings — {concept, statement_type, label, standard_concept, latest_period, facts} — for a custom report's `as_reported_financial_items` - "revenue_segments" -> NEEDS `ticker`. The filer's revenue segments as tagged in its filings — {product_label, product_member, product_axis, concept, latest_period, facts} — for a custom report's `revenue_segment` (pass the product_label). A name lookup only: never sum members across it - "institutional_managers" -> NEEDS `q` (name fragment, e.g. "berkshire"), `cik` (SEC CIK, any width) and/or `manager_type` (from "institutional_investor_types"). Managers as {cik, name, category, current_portfolio_value}, largest first. The value is the 13F cover-page total, not AUM, and can include options. Page with `limit` and `offset`. Pass the `cik` values, never the names, to get_13f_position_changes, get_13f_cik_allocation or a custom report's `institutional_ownership` - "sectors" -> valid `sector` filter values - "institutional_investor_types" -> investor CATEGORIES (not managers) — the keys `screen_stocks(institutional_ownership=...)` filters on, and the `manager_type` values for "institutional_managers" and get_13f_ownership_by_manager_type - "countries" -> covered countries - "fiscal_quarter" -> the most recent fiscal quarter being reported - "market_cap" -> valid `market_cap` buckets (Small-cap, Medium-cap, Large-cap, Mega-cap) - "intraday_frequency" -> supported intraday chart frequencies - "technical_indicators" -> indicator names accepted by `get_technical_indicator_data` (rsi, macd, sma_50, ...); an unknown indicator there returns a 400 listing this set - "tickers" -> the full covered symbol universe as bare symbols — equities PLUS ~420 market indices as caret-prefixed symbols (^GSPC, ^VIX, ...). NOTE: thousands of names — a large payload - "tickers_with_names" -> {symbol, company_name} pairs for the company universe ONLY — market indices are NOT in this list, only in "tickers" (an even larger payload) - "data_feeds" -> the datasets `download_dataset` accepts, as {dataset, description, returns ("rows" or "download_links"), date_field, event_types (valid filter, null = unsupported)}. Call this, not download_dataset (3 calls/week), to answer "what feeds are there" Returns `options` (the values for that kind). Authoritative and never stale: it reads the backend's live config, not a hardcoded list. Public — no auth required.
    ConnectorOAuth
  • Generate designs for a brand, such as ads and social posts: finished, on-brand designs made by Rawa from the brief, one or more per concept. To put a headline, copy or a layout on the user's own photo and keep the photo exactly as it is, pass it as the concept's photoCreativeId: the type is set in the brand's fonts as editable layers, not painted into the picture. Cost: every design is charged, and a call makes concepts × designsPerConcept of them, priced by format. Call with dryRun: true first and tell the user the cost. Once they agree, pass the quoted credits as expectedCredits; a call that would cost a different amount is refused. Give each new generation a new requestId, and repeat it unchanged only on a retry: a retry within 2 minutes returns the first result and is not charged again. Without a requestId, the same arguments within 2 minutes count as a retry. Needs generation allowed over MCP (see get_workspace); a dry run still quotes when it is not, and says why the call would be refused in wouldRefuse. Returns jobs, one jobId per concept, creditsCharged and creditsRemaining; ready in 1 to 5 minutes, a clip longer. If a job panel shows, it tracks the work: do not poll, end your turn with one line saying it is under way, and later use show_creatives with the creativeIds you are told. Otherwise call wait_for_jobs with the jobIds until allFinal is true.
    ConnectorOAuth
  • EXACT keyword / phrase search over the Ortexo Romanian legal database (codes, laws, Fiscal Code, OMFP accounting norms, and case law). Matches precise wording, ranked by how many of your words a passage holds and searched in full inside the principal codes — use it ONLY when you know the exact term, phrase, defined name (e.g. an account name), article number or figure. For a described concept or a natural-language question use search_semantic instead — lexical returns noise for prose. For court decisions set `sources` to ["jurisprudence"] (with both corpora the results are ranked together and may all be legislation): disputes, deductibility challenges or 'has a court ruled'. The two searches rank differently and find different passages: on 103 questions with a known answer (measured 2026-10-28), the answer was among the first 5 results of search_semantic for 67% of them, of search_lexical for 45%, of both for 41% and of at least one of the two for 71%.
    ConnectorOAuth