Skip to main content
Glama
649,985 tools. Updated 2026-10-10 12:11

"A tool for creating a billing organization to manage projects and payments" matching MCP tools:

  • Create a Stripe Checkout session for the active organization and return its hosted checkout URL. The user completes the purchase in the browser; nothing is charged by this call itself. Requires an owner API key. plan defaults to developer; an unsupported plan fails with invalid_plan. Use get_billing_info to check the current plan and create_billing_portal to manage an existing subscription.
    ConnectorNo auth
  • Get current usage against the plan limits, one entry per category (projects, specs, members, …) with the current count, the maximum and whether the category is unlimited. This is the tool that answers 'why can I not create another one'. Use this for usage against plan limits; for the AI credit balance use get_credit_balance. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Set YOUR notification preferences for one or more categories. Categories you do not mention keep their current setting. Use resetCategories to drop your override so a category follows the organization default again — an entry in categoriesJson can only set an override, never remove one. Valid categories: api_design, testing, project, mock_server, style_guide, team, portal, monitoring, security, billing, deprecation. Use this for your own preferences; for the organization defaults use update_org_notification_defaults.
    Connector
    Destructive
    API key
  • Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
    ConnectorNo auth
  • List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.
    ConnectorNo auth
  • List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Provides A-share (Chinese stock market) quantitative analysis through tools for stock screening, northbound capital flow tracking, dragon-tiger list analysis, margin trading, sector analysis, technical indicators, IPO info, and limit-up/down statistics using akshare data.
    11
    2
    MIT

Matching MCP Connectors

  • Permit-verified ADU rentals, pre-approved plans and cited ADU rules for LA, San Diego, SF and NYC.

  • AI agents hire a human to observe, log or film on site. Typed results, feasibility before payment.

  • Lists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projects the calling credential may see. Call it first in a session: the returned id is the project_id that every other tool in this server requires, and guessing that id fails. It does not return components, packages, or tokens - use list_components, list_packages, or get_style_tokens for those.
    ConnectorNo auth
  • Get the organization's trial: which tier it grants, whether it is still running, when it expires and how many days are left. Unlike the other billing tools this one only needs organization membership, not billing:read. Use this for the trial; for the paid plan behind it use get_subscription. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • List the user's workspaces AND the projects inside each workspace — projects are returned nested, so this is also the tool for finding a `project_id` (there is no separate list_projects tool). Call it first whenever another tool needs `workspace_id` or `project_id` (`list_transcriptions` filters, `find_subjects`, `list_open_questions`, `search_meeting_transcripts`). Returns id, name, type (personal/team), your role, and per-project recording counts. Cheap — one small response.
    ConnectorOAuth
  • Read remaining quotas and plan entitlement for the authenticated company. Call this when you need to know whether an active plan is in effect before registering OIDC clients or creating login links. Minting an API key does not require an active plan. Requires a company API key (aa_...) or an MCP OAuth access token. Returns planId, planStatus, periodYm, included, used, remaining, and hardCap. It does not change billing or charge a card. To start a human Pro checkout, use billing_checkout. billing_machine_pay only returns prepaid REST instructions. To manage an existing Stripe subscription, use billing_portal.
    ConnectorAPI key
  • Archive an organization: its projects are archived and stop being checked, its pending invitations are cancelled, and its subscription is cancelled at the end of the billing period. Requires a confirmationToken: call preview_operation with tool "archive_organization" and these arguments first, show the returned plan to the user, and call this tool only after the user explicitly agrees. Needs the organization:manage permission and the owner role.
    Connector
    Destructive
    OAuth
  • Get an account overview: profile, subscription status, active plans, and billing alerts. For a general look at the account, or as the starting point for a question about it. RETURNS: - user: identity, email verification status, account age, last activity - subscription: billing term/dates, paused/throttled status, payment failures, credits, discounts - active_plans[]: proxy type/count/countries, bandwidth, pricing, quotas, features - billing_alerts: consolidated "is anything wrong with the billing right now?" signal. `billing_alerts.has_failing_payment` is True when a payment is failing (card declined, insufficient funds, etc.), the most common billing problem, and `billing_alerts.failing_payments[]` carries the detail of each. NOT INCLUDED: proxy inventory (list_proxies), usage and error stats (get_bandwidth_stats, get_error_stats), the full billing history (list_payment_methods, list_transactions), the full detail of pending payments (list_pending_payments), and account restrictions (view_suspension, list_verifications).
    ConnectorOAuth
  • Returns all groups of the organization the user can access, ordered by name, each with the number of social accounts. Groups are workspaces (brands, clients, projects) that hold social accounts, posts and labels. Call it first to find group IDs for other tools. Use get_social_accounts with group_id to list the accounts of a group. A null approval_workflow means the group inherits the organization approval_workflow from get_organization, it does not mean no approval.
    ConnectorOAuth
  • INSPECTION: Inspect GCP infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check convostatus for hasDeployAttempt=true before calling. Works even after failed deploys to inspect orphaned resources. Inspect deployed GCP resources after a deployment attempt. Use this tool when the user asks about the status or details of their deployed GCP infrastructure. It fetches temporary read-only credentials securely and queries the GCP API directly. RESPONSE TIERS (default is summary for token efficiency): - Summary (default): Key fields only (~500 tokens). Set detail=false, raw=false or omit both. - Detail: Full metadata for a specific resource. Set detail=true + resource filter. - Raw: Complete unprocessed API response. Set raw=true. REQUIRES: session_id from convoopen response (format: sess_v2_...). Supported services: apigateway, bastion, billing, certificatemanager, cloudarmor, cloudbuild, cloudcdn, clouddeploy, clouddns, cloudfunctions, cloudkms, cloudlogging, cloudmonitoring, cloudrun, cloudsql, compute, firestore, gcs, gke, iam, identityplatform, loadbalancer, memorystore, pubsub, secretmanager, vertexai, vpc For a specific service's actions, call with action="list-actions". METRICS: Use list-metrics to see available Cloud Monitoring metrics for any service (no credentials needed — progressive disclosure). Use get-metrics to retrieve time-series data. Optional filters JSON: {"hours":6,"period":300}. Label breakdowns: Cloud Functions (by status), Load Balancer/API Gateway (by response_code_class), Cloud CDN (by cache_result). Secret Manager get-metrics returns operational health (version count, replication, create time) — no time-series. Bastion is an alias for Compute Engine metrics (SSH connection count not available as a GCP metric). BILLING: Use service=billing to inspect GCP billing. Actions: get-billing-info (check if billing enabled, which billing account), get-budgets (list budget alerts for the project — auto-fetches billing account). Requires roles/billing.viewer IAM role. Required IAM roles: Monitoring Viewer (roles/monitoring.viewer) for metrics, Secret Manager Viewer (roles/secretmanager.viewer) for secret health, Billing Viewer (roles/billing.viewer) for billing. EXAMPLES: - gcpinspect(session_id=..., service="compute", action="list-instances") - gcpinspect(session_id=..., service="gke", action="list-clusters") - gcpinspect(session_id=..., service="cloudsql", action="get-metrics", filters="{\"hours\":6}") - gcpinspect(session_id=..., service="billing", action="get-billing-info")
    ConnectorNo auth
  • INSPECTION: Inspect GCP infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check convostatus for hasDeployAttempt=true before calling. Works even after failed deploys to inspect orphaned resources. Inspect deployed GCP resources after a deployment attempt. Use this tool when the user asks about the status or details of their deployed GCP infrastructure. It fetches temporary read-only credentials securely and queries the GCP API directly. RESPONSE TIERS (default is summary for token efficiency): - Summary (default): Key fields only (~500 tokens). Set detail=false, raw=false or omit both. - Detail: Full metadata for a specific resource. Set detail=true + resource filter. - Raw: Complete unprocessed API response. Set raw=true. REQUIRES: session_id from convoopen response (format: sess_v2_...). Supported services: apigateway, bastion, billing, certificatemanager, cloudarmor, cloudbuild, cloudcdn, clouddeploy, clouddns, cloudfunctions, cloudkms, cloudlogging, cloudmonitoring, cloudrun, cloudsql, compute, firestore, gcs, gke, iam, identityplatform, loadbalancer, memorystore, pubsub, secretmanager, vertexai, vpc For a specific service's actions, call with action="list-actions". METRICS: Use list-metrics to see available Cloud Monitoring metrics for any service (no credentials needed — progressive disclosure). Use get-metrics to retrieve time-series data. Optional filters JSON: {"hours":6,"period":300}. Label breakdowns: Cloud Functions (by status), Load Balancer/API Gateway (by response_code_class), Cloud CDN (by cache_result). Secret Manager get-metrics returns operational health (version count, replication, create time) — no time-series. Bastion is an alias for Compute Engine metrics (SSH connection count not available as a GCP metric). BILLING: Use service=billing to inspect GCP billing. Actions: get-billing-info (check if billing enabled, which billing account), get-budgets (list budget alerts for the project — auto-fetches billing account). Requires roles/billing.viewer IAM role. Required IAM roles: Monitoring Viewer (roles/monitoring.viewer) for metrics, Secret Manager Viewer (roles/secretmanager.viewer) for secret health, Billing Viewer (roles/billing.viewer) for billing. EXAMPLES: - gcpinspect(session_id=..., service="compute", action="list-instances") - gcpinspect(session_id=..., service="gke", action="list-clusters") - gcpinspect(session_id=..., service="cloudsql", action="get-metrics", filters="{\"hours\":6}") - gcpinspect(session_id=..., service="billing", action="get-billing-info")
    ConnectorNo auth
  • Explain what UseMyContext is, what this connection can and cannot do, and where the user goes to manage their account. Call this when the user asks what UseMyContext is, what you (the AI) can do with this connection, or where to find pricing, plans, billing, teams, or settings. IMPORTANT: this connection is READ-ONLY - you cannot create/rename/delete a profile, change privacy, manage the plan or billing, set up a team, invite teammates, or connect Google Drive/Notion/kDrive; those are done by the user at usemycontext.ai, so point them to the returned links rather than attempting them or telling them to search. Returns static public information only (no user data). Read-only; nothing is written, so it is safe to call.
    ConnectorNo auth
  • Report the user's current plan and usage: their tier (Free or Premium), how many projects and how much storage they are using against their limits, their subscription status if any, and where they manage their plan. Use this when the user asks what plan they are on, how much storage or how many projects they have used, or whether they are near a limit. Metadata only - no files, facts, or profile content. This is READ-ONLY: you cannot change the plan or start a purchase; plan and billing changes are done by the user themselves at usemycontext.ai. Read-only; nothing is written, so it is safe to call.
    ConnectorNo auth
  • Rename the active organization display name (control-plane tenants.name — shown in org switcher and billing). PATCH /api/settings/organization with { name }. Scope write:settings; RBAC admin.entity.edit (OWNER/ADMIN). Does not change entity legal name or slug.
    ConnectorOAuth
  • Create a Stripe Checkout session for the authenticated company so a human can subscribe to Pro. Requires a company API key (aa_...) or an MCP OAuth access token. It does not accept a console session or a bootstrap token, and it does not mint a company or an aa_ secret. Returns url. Creating the session does not charge a card; the human pays on the Stripe page. When local billing bypass is enabled, there is no Stripe call and no charge: Pro is granted immediately with no period end, and url is the console success URL (/console?billing=ok), not a Stripe Checkout URL. If Stripe is not configured and bypass is off, the JSON includes error stripe_not_configured. For prepaid purchase instructions, use billing_machine_pay. To manage an existing subscription, use billing_portal.
    ConnectorAPI key
  • Create a new organization, owned by the caller. Only with a Mencoro connection that is not limited to one organization. Requires a confirmationToken: call preview_operation with tool "create_organization" and these arguments first, show the returned plan to the user, and call this tool only after the user explicitly agrees. Needs the organization:manage permission and the owner role.
    ConnectorOAuth
  • Store the app's Stripe API credentials so billing (checkout, subscriptions, the billing portal) works. Arguments: secretKey (the Stripe SECRET key, "sk_live_..." or "sk_test_...") and publishableKey (the Stripe publishable key, "pk_live_..." or "pk_test_..."). Both are found in the Stripe dashboard under Developers > API keys. Ask the user for these — never invent or guess a key. Returns { connected, webhookConfigured } and nothing else: the keys are never echoed back. connected=false means the credentials were stored but Stripe did not confirm them, so re-check the keys. webhookConfigured=false means Stripe events will not reach Bridge; see get_stripe_status. Use get_stripe_status to check the current state without writing. IMPORTANT: this stores the credentials but does NOT enable payments — Stripe stays switched off until setup_payments turns it on. For first-time setup prefer setup_payments, which does both. Use this only to rotate keys on an app where payments are already enabled. Before writing app code that consumes this, call get_integration_guide with topic=billing and the framework the app uses.
    ConnectorOAuth