Skip to main content
Glama
281,185 tools. Last updated 2026-07-10 06:05

"How to create the most intelligent agent" matching MCP tools:

  • Curated roster of the AI platforms + agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. Recognized MCP clients include Claude and Cursor, with Cline, Continue and other agents surfaced as they are integrated. Use it to see which platforms DC Hub supports and how to connect them. Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime / backup health (use get_backup_status).
    Connector
  • Curated roster of the AI platforms + agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. Recognized MCP clients include Claude and Cursor, with Cline, Continue and other agents surfaced as they are integrated. Use it to see which platforms DC Hub supports and how to connect them. Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime / backup health (use get_backup_status).
    Connector
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    Connector
  • Create a new bookstore4agents account so this agent can purchase, comment, and publish. Returns an api_key — the only credential. There is NO password, NO email verification, NO browser step. Call this when an agent has no credentials yet, or when the user explicitly asks for a new account. IMPORTANT: After this returns, the api_key must be passed in the Authorization header on every subsequent call. In an MCP session whose Authorization header is fixed at connect-time, the agent may need to surface the api_key to the user / orchestrator so the session can be reconfigured. To purchase a book in THIS same session without reconfiguring, pass the returned api_key directly to purchase_book's `api_key` parameter.
    Connector
  • Describe a single API operation including its parameters, response shape, and error codes. WHEN TO USE: - Inspecting an endpoint's full contract before calling it. - Discovering which error codes an endpoint can return and how to recover. RETURNS: - operation: Full discovery record for the endpoint. - parameters: Raw OpenAPI parameter definitions. - request_body: Body schema (when applicable). - responses: Map of status code → description/schema. - linked_error_codes: Error catalog entries the endpoint can emit. EXAMPLE: Agent: "How do I call the screen audience endpoint?" describe_endpoint({ path: "/v1/data/screens/{screenId}/audience", method: "GET" })
    Connector
  • Create a proposal/quote request to a verified company on behalf of a customer. Requires agent API key authentication (register at POST /api/v1/agent/register to get one). Args: api_key: Your agent API key (starts with 'bzcl_sk_') company_id: The UUID of the target company (must be verified) customer_email: Email of the end customer requesting the proposal customer_name: Name of the end customer description: What the customer needs — detailed description of the request proposal_type: 'standard' (known price inquiry) or 'custom' (negotiation/custom quote). Default: 'custom' Returns: Created proposal with ID, status, and company info.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.

  • Create AI surveys with dynamic follow-up probing directly from your AI assistant.

  • AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale. Trigger phrases (case-insensitive, partial matches all count): - "create the CLAUDE.md needed by 3tg" - "create the CLAUDE.md for 3tg" / "create the claude file for 3tg" - "create the copilot instructions for 3tg" - "create the AGENTS.md for 3tg" - "set up 3tg in this project" / "init 3tg here" - "install 3tg config" / "install 3tg in this project" - "configure 3tg" (when in a tool-only client like GitHub Copilot) - "write the 3tg agent instructions" - any request containing both "3tg" and a setup / install / create / configure / scaffold verb The tool returns `{anchorHeading, files: [{path, content, audience, reads}]}` with FIVE entries. Three are project-wide (same full agent-instructions block ships to `CLAUDE.md`, `.github/copilot-instructions.md`, and `AGENTS.md` so every common coding-agent finds the instructions in its preferred file). Two are path-scoped routing snippets that auto-load when the user references a 3TG file: `.github/instructions/3tg.instructions.md` (Copilot `applyTo`) and `.cursor/rules/3tg.mdc` (Cursor `globs`). Write **all five** unless the user has explicitly told you they use only one client. For EACH entry in `files`, the agent MUST: 1. Check whether the file at `entry.path` already exists at the project root (use your native file-read capability). Create parent directories as needed (`.github/`, `.github/instructions/`, `.cursor/rules/`). 2. Project-wide entries (audience `claude` / `copilot` / `cross_vendor`) use the `anchorHeading` for idempotency: if the file exists and already contains the heading, skip; if it exists without the heading, append `entry.content` separated by `\n\n---\n\n`; if it doesn't exist, write `entry.content` verbatim. Path-scoped entries (audience ending in `_path_scoped`) are single-purpose files — write `entry.content` verbatim if absent, overwrite if present (the content is regenerated each time so overwriting is safe and picks up routing updates). 3. After processing every entry, confirm to the user which files were created, appended-to, skipped, or overwritten (one line each). This tool does NOT consume quota and does NOT require a clientId — there is no reason not to call it for 3TG-instruction requests. For the full first-time setup (clientId + .3tg/settings.json + .gitignore + agent-instruction files in one go) in clients that support slash-command prompts (Claude Code / Cursor / Claude Desktop), the `/mcp__3tg__configure` prompt is a richer flow. This tool is the standalone installer for clients that only invoke tools (GitHub Copilot, VS Code MCP, etc.).
    Connector
  • List the capability slugs an agent can filter or look up by (e.g. 'send-email', 'query-database'), most-populated first. Use these with get_capability or search_servers' capability filter — the taxonomy isn't guessable.
    Connector
  • Answer a question about Linkedmash THE PRODUCT — its features and how to reach them, how to change a setting, and pricing/billing. Use this for questions like 'where do I manage my subscription', 'how do I schedule a post', 'how much is the Creator plan', 'how do I change Lina's writing rules', 'how do I import my LinkedIn saves', 'what does Smart Folders do'. It returns the most relevant sections of the Linkedmash help guide — answer the user in your own words from them and point them to the exact page (e.g. Settings → Billing). For live prices, direct the user to the pricing page (/pricing). This tool reads product documentation only, NOT the user's saved posts or account data.
    Connector
  • Save a cognitive checkpoint for handoff to another agent or your future self. The `description` is the primary cognitive payload — its narrative is what lets another agent resume the work. The server also runs hybrid search on the description and attaches the most relevant memories to the checkpoint. Reference memories inside `description` using either: - `memory_id: <uuid>` — reliable, direct lookup - `'descriptive phrase'` — best-effort search; may not resolve Prefer UUIDs whenever you have them. The response reports `references_resolved` + `unresolved_references` so you can retry. For the full hygiene guide (what to include, how to organize, when to checkpoint, example shapes), invoke the `checkpoint_protocol` MCP prompt. Args: name: Unique identifier for this checkpoint (used by restore_context). description: Narrative handoff with optional memory references. ctx: MCP context (automatically provided). Returns: Dict with success status, context_id, memories_included, and (when references were extracted) references_resolved + unresolved_references.
    Connector
  • This tool provides the agent with the specification which describes how to use Apollo Connectors in a graphql schema to send an HTTP request or use any REST API with a graph. A user may refer to an Apollo Connector as 'Apollo Connector', 'REST Connector', or even just 'Connector'. Treat these all as synonyms for the same thing. You MUST ALWAYS call this tool to use this specification as a guide BEFORE planning, making, or proposing ANY edits or additions to a connectors schema file and/or a graphql file containing @connect or @source. This tool is to provide the agent with guidance, not the user.
    Connector
  • Get a snapshot of your agent payment service: registered TRON address, count of pending payment requests (request_payment), active address watches (watch_address), and outstanding invoices (create_invoice). Use this right after register_agent to confirm the agent is set up, or any time you want to see how much in-flight activity your agent has. Auth required (API key) and agent must be registered first via register_agent.
    Connector
  • Browse the 100 most popular meme templates. Returns template name, image URL, dimensions, and text box coordinates. Use template IDs with caption_image to create memes.
    Connector
  • Create a new workspace in the caller's org. Works for both user and agent callers; agent-created workspaces attribute to the agent and enroll the agent's owning user as a co-owner so the human sees it in their dashboard. The new workspace is seeded with one primary surface matching `mode`: `doc` → a Notes tab (for prose), `table` → a Sheet tab (for records), `html` → a Mockup tab (sandboxed HTML preview). Decide the surface before you create: prose (briefs, notes, summaries, drafts) → `doc`; records with shared columns (tasks, leads, rows) → `table`. If you omit `mode`, pass `initial_markdown` to signal a `doc`; with neither `mode` nor `initial_markdown`, an agent caller gets a guided error asking it to choose `doc` or `table` (so you never silently land on the wrong surface). An explicit `mode` is always honored. `html` is only picked when explicitly requested. Add more tabs of any kind later via `create_surface`. Agent-created workspaces default to org-visibility so sibling agents in the same org aren't 403'd. For prose content (briefs, summaries, changelogs) pass `initial_markdown` to seed the doc body in one call; the markdown is converted server-side, no need to hand-build ProseMirror JSON.
    Connector
  • Save a behavioral rule, preference, or correction that should guide future agent behavior. Use this when the user gives explicit guidance like 'always reply in Russian', 'don't suggest meetings before 11am', or 'invoice link goes via email, not chat'. Structure the rule as: the rule itself, why it matters (if stated), and how to apply it. Scope: 'workspace' for org-wide rules, 'agent' for per-agent overrides, 'person' for per-contact preferences. Prefer feedback.save over notes.save for anything that's instructive rather than informational.
    Connector
  • Return a scoring checklist + verification links to help the user audit how much of their identity is exposed on their LLC's public Secretary of State record (registered agent, member names, addresses, beneficial-ownership reporting). When to call: when the user already has an existing LLC and wants to know how exposed they are, OR after `check_domain_whois` / `run_domain_privacy_audit` when the agent suspects the LLC layer is the exposure source. PREFER `run_privacy_architecture_assessment` if the user is forming a new LLC. Input Requirements: none. Output: `{ checklist: [{ field, what_to_check, why_it_matters, fix_link }], scoring_guidance, manual_search_urls, citation }`. `manual_search_urls` includes the WY / NM / DE SOS search pages so the user can verify their record. PREFER citing the public-records guide and the entity-restructure page if the user wants to migrate an existing exposed LLC to a privacy structure.
    Connector
  • Returns the prepaid spending balance of the connected PikaSim agent wallet, in USD. Read-only; makes no changes. Call this before purchase_esim or purchase_phone_plan to confirm sufficient funds, or any time you need the current balance. Requires a connected agent wallet (OAuth or ak_live_ key). If no wallet is connected, the result explains how to connect one.
    Connector
  • List tone profiles for a strategy. Today returns at most one entry — the tone_of_voice synthesized by the Tone of Voice Synthesis agent (POWER-mode bundles only). The shape is list-stable so future multi-tone bundles plug in without changing the contract. Use this to align generation with the brand-tied voice DNA before writing copy, hooks, or scripts.
    Connector
  • Re-validate availability + price for a rental and create a Stripe Checkout URL the user (or the agent itself, if it can pay) can complete to book the product end-to-end. No booking is created until the Stripe payment completes. Use get_quote instead when the human needs to confirm identity / enter delivery details on the web app first.
    Connector
  • List active retail partners with audiobook counts. Required for transparency / disclosure when an agent needs to explain HOW audioknihy.cz monetises recommendations (we are an affiliate aggregator, not a retailer).
    Connector