Skip to main content
Glama
114,469 tools. Last updated 2026-04-21 15:35
  • MCP Apps — interactive UI widgets for file browsing, workspace dashboards, uploads, and more. Launch apps with workspace/share context, list available apps, and get app metadata. Actions & required params: - list: list all available apps (no params) - details: app_id — get full metadata for a specific app - launch: app_id, profile_type, profile_id — renders the widget via embedded resource content with mimeType text/html;profile=mcp-app - get-tool-apps: tool_name — list apps available for a specific tool
    Connector
  • Bridge an MCP tool call to an A2A (Agent-to-Agent Protocol) agent. Translates the MCP tool_name and arguments into an A2A task, sends it to the target A2A agent, waits for completion, and translates the response back to MCP format. Use this to make any MCP tool accessible to A2A agents (Google's agent ecosystem). Requires authentication.
    Connector
  • Delete an app from Bitrise. When deleting apps belonging to multiple workspaces always confirm that which workspaces' apps the user wants to delete.
    Connector
  • Get detailed Nestr documentation by topic. Call before unfamiliar operations. Topics: search, labels, nest-model, inbox, daily-plan, notifications, insights, tension-processing, skills, mcp-apps, authentication, and more. Use topic 'topics' for the full list.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Connect YNAB to AI assistants like ChatGPT and Claude via a hosted remote MCP server with OAuth. Provides tools for reading budgets, accounts, categories, transactions, analyzing spending patterns, forecasting cash flow, tracking goal progress, and managing funds — all after signing in with your own YNAB account.

  • The verified hub for conferences and journals. Powered by AI to match your scholarly ambitions with the world's most prestigious academic opportunities.

  • Filter free-to-play games by tag (dot-separated combination of attributes). Returns matching games with title, short description, genre, platform, publisher, release date, and thumbnail.
    Connector
  • Search for games by title. Returns each game with its cheapest current price and a deal ID to get more details.
    Connector
  • Get aggregated agent experience data for an MCP service. Includes success rate, latency, common errors, usage trends, and confidence score.
    Connector
  • Get a player's completed games for a specific month. Returns game URLs, time controls, results, and player ratings.
    Connector
  • Create a local container snapshot (async). Runs in background — returns immediately with status "creating". Poll list_snapshots() to check when status becomes "completed" or "failed". Available for VPS, dedicated, and cloud plans (any plan with max_snapshots > 0). Local snapshots are stored on the host disk and count against disk quota. Requires: API key with write scope. Args: slug: Site identifier description: Optional description (max 200 chars) Returns: {"id": "uuid", "name": "snap-...", "status": "creating", "storage_type": "local", "message": "Snapshot started. Poll list_snapshots() to check status."} Errors: VALIDATION_ERROR: Max snapshots reached or insufficient disk quota
    Connector
  • Build and deploy a governed AI Team solution in one step. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to A-Team Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub. AUTO-DETECTS GitHub repo: if you omit mcp_store and a repo exists, connector code is pulled from GitHub automatically. First deploy requires mcp_store. After that, write files via ateam_github_write, then just call build_and_run without mcp_store. For small changes to an already-deployed solution, prefer ateam_patch (faster, incremental). Requires authentication.
    Connector
  • Re-deploy skills WITHOUT changing any definitions. ⚠️ HEAVY OPERATION: regenerates MCP servers (Python code) for every skill, pushes each to A-Team Core, restarts connectors, and verifies tool discovery. Takes 30-120s depending on skill count. Use after connector restarts, Core hiccups, or stale state. For incremental changes, prefer ateam_patch (which updates + redeploys in one step).
    Connector
  • Claim an API key using a claim token from the container. After calling request_api_key(), read the claim token from ~/.borealhost/.claim_token on your container and pass it here. The token is single-use — once claimed, it cannot be used again. The API key is automatically activated for this MCP session. Args: claim_token: The claim token string read from the container file Returns: {"api_key": "bh_...", "key_prefix": "bh_...", "site_slug": "my-site", "scopes": ["read", "write"], "message": "API key created and activated..."} Errors: VALIDATION_ERROR: Invalid, expired, or already-claimed token
    Connector
  • Create a new calendar event with title, dates, and optional details like location, time, and notifications. DATE RULE: The API server uses UTC. Today's date may be rejected as "past" depending on the user's local timezone. To be safe, always use tomorrow's date or later when creating events. NEVER use today's date — it will fail with "Cannot Create Events In The Past". If the user asks to create an event for today, explain this limitation and suggest tomorrow instead.
    Connector
  • Get the caller's referral earnings, milestones, and free-call status. Requires Authorization: Bearer <api_key>, has no usage charge, and returns the current discount ledger without creating a new analysis. Example: call after a referral campaign to inspect earned credits. Use this when you need balances and milestones. Use get_referral_code instead when you only need the shareable token.
    Connector
  • ⚠️ MANDATORY FIRST STEP - Call this tool BEFORE using any other Canvs tools! Returns comprehensive instructions for creating whiteboards: tool selection strategy, iterative workflow, and examples. Following these instructions ensures correct diagrams.
    Connector
  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • Returns a curated list of example plans with download links for reports and zip bundles. Use this to preview what PlanExe output looks like before creating your own plan. Especially useful when the user asks what the output looks like before committing to a plan. No API key required.
    Connector
  • Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Social Network (users, posts, follows), Knowledge Graph (topics, articles, authors), Product Catalog (products, categories, suppliers). You can use these templates directly with create_graph_project or modify them for your needs. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.
    Connector
  • Creates a visual edit session so the user can upload and manage images on their published page using a browser-based editor. Returns an edit URL to share with the user. When creating pages with images, use data-wpe-slot placeholder images instead of base64 — then create an edit session so the user can upload real images.
    Connector
  • Get an exact sat cost quote for a service BEFORE creating a payment. Useful for budget-aware agents to price-check before committing. No payment required, no side effects. Pass service=text-to-speech&chars=1500, service=translate&chars=800, service=transcribe-audio&minutes=5, etc. Returns { amount_sats, breakdown, currency }. Omit params to see the full catalog of supported services.
    Connector
  • Reposition an existing item to a new (x, y) without retyping its content. Works for every item kind: `text` and `link` set the top-left to (x, y); `line` translates every point so the stroke's bounding box top-left lands at (x, y); `image` sets the top-left like text. `kind` defaults to `text` for backward compat with older callers. Find the id + kind via `get_board`. Prefer `move` over re-creating an item when only the location changes — it preserves the id, content, author and avoids a round-trip of base64 bytes for images.
    Connector
  • Run a read-only SQL query in the project and return the result. Prefer this tool over `execute_sql` if possible. This tool is restricted to only `SELECT` statements. `INSERT`, `UPDATE`, and `DELETE` statements and stored procedures aren't allowed. If the query doesn't include a `SELECT` statement, an error is returned. For information on creating queries, see the [GoogleSQL documentation](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax). Example Queries: -- Count the number of penguins in each island. SELECT island, COUNT(*) AS population FROM bigquery-public-data.ml_datasets.penguins GROUP BY island -- Evaluate a bigquery ML Model. SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`) -- Evaluate BigQuery ML model on custom data SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Predict using BigQuery ML model: SELECT * FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Forecast data using AI.FORECAST SELECT * FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips', timestamp_col => 'date', id_cols => ['usertype'], horizon => 30) Queries executed using the `execute_sql_readonly` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `project_id` field.
    Connector
  • Show all 23 scoring signals with their default weights and descriptions. This is the baseline scoring that applies when no custom profile is specified. Use this to understand what each signal means and how much it contributes to the score before creating custom profiles. Profiles are sparse overrides on top of these defaults. This tool does not require an API key. The defaults are hardcoded and always available.
    Connector
  • Check server connectivity, authentication status, and database size. When to use: First tool call to verify MCP connection and auth state before collection operations. Examples: - `status()` - check if server is operational, see quote_count, and current auth state
    Connector
  • Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.
    Connector
  • Look up a single paper by its DOI. Args: doi: The DOI of the paper (e.g. "10.1038/s41586-024-07386-0"). api_key: Optional: Your Stripe subscription ID for paid access. Get one at https://bgpt.pro/mcp Returns: Paper with title, DOI, Raw Data, methods, results, quality scores, and 25+ metadata fields — or an error if not found. Costs $0.02 if found, free if not.
    Connector
  • Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
    Connector
  • Generate industry-standard documentation for any project using SUMA graph memory. This tool does NOT fabricate. It retrieves real war stories, architecture rulings, and deployment facts from the K-WIL graph, then uses Gemini to render them as professional documentation. The graph IS the source of truth — suma_doc makes it readable. Why this beats a generic doc generator: Generic: "Here is how to install." (stateless, stale, hallucinated) suma_doc: "We chose REST over MCP because [Architect Ruling Apr 5]. Here is how it works in production: [real deployment from graph]. Avoid X — we tried it and [root cause]." Args: prompt: What documentation to generate. Be specific. Examples: "Write a README for the SUMA MCP Server API" "Generate an ARCHITECTURE.md explaining the ring_search algorithm" "Write a CHANGELOG entry for today's /api/wakeup deployment" "Create an API reference for /api/ingest and /api/search" "Write an onboarding guide for a new backend engineer joining the QMS team" project: Optional filter to narrow graph search to a specific product. Examples: "suma-mcp", "squad-qms", "squad-ghostgate", "squad-companion" doc_type: Optional hint to shape output format. "readme" → GitHub README with badges + sections "architecture" → Design doc with decisions, trade-offs, diagrams description "api_reference" → Endpoint table + request/response examples "changelog" → Conventional Commits format, grouped by type "onboarding" → Step-by-step guide for a new engineer "runbook" → Ops runbook with commands, failure modes, escalation If omitted, Gemini infers the best format from the prompt. Returns: document: The generated documentation (markdown) nodes_used: Number of graph nodes retrieved as source material source_summary: Brief description of what the graph provided doc_type_detected: What format was generated
    Connector
  • Search for existing entities (people, galleries, museums, auction houses, institutions, foundations, collectors) by name. Use this before creating a new entity to check for duplicates — the system includes ~2,500 major galleries, museums, and auction houses. Returns matching entities for autocomplete-or-create flow. If no match is found, create a new entity via create_entity.
    Connector
  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • Opens a CueCrux session. Returns a capability plan covering retrieval, proofing, memory, journaling, and audit across VaultCrux and MemoryCrux. Call this first. All subsequent work flows through the plan's channels. Works identically for local Crux CE installations and the hosted CueCrux platform. The plan carries typed routing hints; hosted deployments can stage a legacy-compatible handshake shape or the newer v2 graph shape behind feature flags, but callers should always treat the returned plan as the source of routing truth. Bulk-capable agents use the HTTP/2 binary channel transparently; MCP-only agents use the MCP fallback URLs in the plan. Implements RCX-Protocol v1.0.
    Connector
  • Verify that the FXMacroData API and MCP server are reachable.
    Connector
  • Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents
    Connector
  • Bridge an A2A (Agent-to-Agent Protocol) task to an MCP server. Extracts the intent from the A2A task, maps it to an MCP tool, calls the tool, and wraps the result in A2A response format. Use this to let A2A agents interact with any MCP server. Requires authentication.
    Connector
  • Get full details of a previous MCP session by ID. Returns the complete result including participant responses and moderator synthesis. Use list-sessions first to find session IDs.
    Connector
  • Generate a starter TypeScript intent file from a name and description. Returns a complete defineIntent() source string ready to save as a .ts file — no files are written, no network requests made. On invalid domain values, returns an error string. The output compiles directly with axint.compile. Use this when creating a new intent from scratch; use axint.templates.get for a working reference example, or axint.schema.compile to generate Swift without writing TypeScript.
    Connector
  • List all slide presentations created in the current MCP session. Returns URLs, themes, and timestamps for each presentation you've created.
    Connector
  • Lists aggregation views (materialized views and procedures) created for a project. **When to use this tool:** - When the user asks "what views exist?", "my aggregations", "my materialized views" - Before creating a new view to check it doesn't already exist - To get the view ID for deletion **Response format:** Returns a JSON array with each view's ID, full_name (dataset.name), type, SQL, description, and creation date.
    Connector
  • Create and save a new Workflow in the workspace. IMPORTANT: Always validate the config with workflow_specs_validate before creating the workflow. The config is the same JSON format used by workflow_specs_run and workflow_specs_validate. Once saved, the workflow can be executed by ID via workflows_run. Returns the created workflow including its document ID. Save this ID — it is required for workflows_update.
    Connector
  • Get an upload URL to upload a single image to a project. Returns a pre-built upload URL and instructions. The caller must perform the actual upload using curl since the MCP server cannot access local files. This endpoint uploads images only. To add annotations, call annotations_save with the image ID from the upload response. For bulk uploads with annotations, use images_prepare_upload_zip.
    Connector