Skip to main content
Glama
532,022 tools. Updated 2026-09-08 03:32

"A system for building an autonomous second brain" matching MCP tools:

  • Step 1 of autonomous self-registration - no API key required. Costs $0.01 USDC on Base (anti-spam fee, not a wallet-ownership proof). Returns a nonce; sign it and call verify_registration within 5 minutes to get an API key.
    ConnectorNo auth
  • Create or update a standing agent — a saved {goal + tickers + schedule} that fires either a fixed step recipe (agent_type="workflow", free/deterministic) or an AI-directed team (agent_type="autonomous", charged — settles against the owner's BYO key first, falling back to the managed wallet only if funded). Upsert semantics: omit `agent_id` to CREATE a new agent; pass an existing `agent_id` to UPDATE it. There is no separate update_agent — this does both, matching save_watchlist/save_thesis's house style. `agent_type` is STRUCTURAL and immutable: always required, and on an update it is verified against the existing agent before anything is changed — passing a different agent_type than the agent already has is rejected (delete and recreate to change the type). `steps` (an array of {kind:"tool"|"sop", name, args, label?}) is required and non-empty when CREATING an agent_type="workflow" agent, and must be omitted for agent_type="autonomous" (use `managed_model` there instead, itself optional and only valid for agent_type="autonomous"). `when` picks the trigger: "manual" (fires only via run_agent or the Workspace UI) or "schedule" (requires a `schedule` object — cadence "weekly" needs day_of_week, "monthly" needs day_of_month). This tool does NOT itself fire a run — use run_agent for that. Tier: sp500+ (sample rejected).
    ConnectorNo auth
  • The list-building tool. Re-runs a plain-English people search and unlocks up to `count` full profiles in ONE atomic charge: 1 credit per newly unlocked person, and anyone you already own is free. Returns each person's real name, title, company, location, LinkedIn URL and an `id`. Emails are NOT fetched here (that is a separate credit): after unlocking, call fetch_email with each person's `id` to get their verified work email. WARNING for autonomous use: this can spend up to `count` credits in a single call, so choose `count` deliberately and confirm with the user before large batches. Returns an out-of-credits error instead of overspending.
    ConnectorNo auth
  • Propose or save a direct durable update into Org Brain or User Brain. Use this for requests like update our org brain, add this to Brain, remember this for the organization, save this as team memory, or update my private Brain. Do not create or update Contexts or Workflows when the user asks to update Brain unless they explicitly ask for those surfaces. For the smoothest UX, call with scope=auto and confirmed=false when you notice a durable memory or need scope confirmation; Oi will return a confirmation prompt and saveArguments. If the user has already explicitly asked to update Org Brain or User Brain with specific content, choose scope=organization or scope=user and set confirmed=true. Use scope=organization for organization-wide facts, vocabulary, policies, approval rules, shared project context, or repeated team workflows that should apply to the current organization. Use scope=user for personal preferences, recurring individual working style, or user-specific context that should follow the authenticated user. Confirmed Brain updates use an AI markdown update pass: compare the latest Brain markdown with the requested change, preserve existing structure, create headings when needed, add only missing guidance, and make the smallest accurate edit. Return a simple saved response when a new version is released, or a simple no-change response when the requested guidance appears to already exist in some capacity. Never save one-off task details, guesses, secrets, credentials, sensitive private data, or unconfirmed assumptions.
    ConnectorOAuth
  • Start a purchase of a credit package and return a way to pay. This does NOT complete a payment by itself — it returns a payment link / address: • method 'stripe' → returns a checkout_url. Paying by card requires a HUMAN to open that link and enter card details; an agent cannot finish a card payment on its own. • method 'crypto' → returns a Plisio invoice with a checkout_url AND, when you pass a `currency` (BTC, ETH, LTC, USDT, USDC), a RAW wallet `address` + `amount`. An autonomous agent CAN pay this from a crypto wallet with no browser/human, then credits are added automatically once the payment confirms. Prefer crypto for fully autonomous top-ups. Get a package id from get_packages first.
    ConnectorNo auth
  • Get the Designesy SKILL.md — the agent-skill-format export of the design-system contract, written as behavioral rules an AI coding agent can drop into .agents/skills/ or a system prompt. Use this when you want the contract in a form that steers how an agent *builds* UI (tokens, anti-patterns, behavioral rules, verification). When NOT to use: for the raw contract JSON, use designesy_contract; for scoring, use designesy_score. Read-only — no side effects. Returns markdown text (SKILL.md format) — drop into .agents/skills/ or paste into a system prompt. No parameters.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    F
    maintenance
    Provides a Docker container for managing markdown notes with semantic search and an MCP server to expose brain tools to AI clients like Claude.
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Persistent, semantically-searchable memory for AI agents using local PostgreSQL, pgvector, and Ollama embeddings, exposed via MCP with hybrid retrieval, knowledge graph, and auto-recall hook.
    2
    MIT

Matching MCP Connectors

  • Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.

  • Free: turn your AI chats into spaced-repetition vocabulary. 13 tools, reads and writes.

  • Download a file from a public http(s) URL and store it in the user's Second Brain as a file object — use when the user shares a direct link to a PDF, image, spreadsheet, or other file and asks to save, download, or keep it. The saved file shows up with their uploads and can be read afterwards with read_file. Not for web pages (that is read_web_page with save=true) and not for files behind a sign-in. Files over 50MB are refused.
    ConnectorNo auth
  • Generate a complete WCAG-compliant UI state palette from a brand hex. Returns colours for: brand, hover, active, disabled, focus ring, success, warning, error, info, surface subtle, surface strong. All states computed for contrast against your background colour. Returns hex, contrast ratio, WCAG grade, and usage note for each state. Includes CSS custom properties ready to paste. Supports light and dark mode. Use before building any UI component system.
    ConnectorNo auth
  • Reference-first build — 'show me what you like, I'll build it.' Give a reference you LIKE (a public site URL via reference_url, and/or a curated library id via reference_id from search_references) plus what YOU are building, and get back a matching StandOut direction, a reference-backed build plan, and the next call for section code. This is the front door for building from an EXAMPLE instead of a text brief: Standout reads the URL server-side for its semantic signal (title, headings, copy) and folds it into the direction match. Note: pixel-level palette/type extraction from an image is not yet supported (that is the Phase 2 vision pass) — for now it matches on the page's text/structure plus the curated library. Pass reference_id to anchor on an exact curated reference.
    ConnectorNo auth
  • Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
    ConnectorNo auth
  • Register this agent with the GovBid Global API and receive an API key. Call this once if you don't already have an api_key, before calling search_opportunities. No human interaction (e.g. CAPTCHA) is required — this endpoint is designed for autonomous AI agent self-registration. The returned api_key is shown only once, so store it for reuse.
    ConnectorNo auth
  • Create or update a Brain file. Writes to your default brain unless you name one; shared brains need editor access. Replaces the whole body (use mode "append" to add to the end); the previous body is kept as a version. Credentials are refused — the Brain is memory, not a vault. Needs your agent bearer token.
    ConnectorNo auth
  • Create an opportunity, always as a new one. If another system already knows this deal and you are syncing it, use upsert_opportunity, which matches on that system's identity instead of creating a second copy. Omit stageId to use the first open stage of the default pipeline. Amount is an integer in minor units and requires a currency. Set ownerActorId and expectedCloseDate here rather than in a second call: both are filterable and sortable, and recording one fact as two assertions makes the history harder to read than the API.
    ConnectorOAuth
  • Register a new autonomous agent in the project's agent registry, returning its id, slug and wire-up instructions in one call — so an agent can go from nothing to reporting in a single conversation. Call this ONCE per autonomous worker, not once per monitor. ATTACHMENT RULE: after registering, attach monitors to this agent by passing the returned agent_id (its id OR its slug) to create_monitor's agent_id parameter. Naming an agent that does not exist is an error (400 UNKNOWN_AGENT) — it is NEVER an implicit create, so re-running this tool with the same name is the only way to get a new agent_id to attach to. Re-registering with the same name is safe: the API derives a stable slug from name and rejects a duplicate slug rather than creating a second row.
    ConnectorNo auth
  • Use when building an AI governance compliance roadmap, advising on high-risk AI deployment obligations in Colorado, or briefing boards on upcoming US state AI regulatory requirements. Colorado SB 205 takes effect June 30, 2026 — the first comprehensive US state AI law. Returns developer and deployer obligations, high-risk AI system criteria, consumer rights, penalty structure ($20,000 per violation, AG enforcement), and comparison to EU AI Act. Example: AI-based loan underwriting system deployed in Colorado requires algorithmic impact assessment, plain-language consumer disclosure before first use, 3-year audit trail with AG access rights, and annual compliance certification — noncompliance triggers $20,000 per violation. Source: Colorado SB 205, enacted May 17, 2024.
    ConnectorNo auth
  • REST API access for autonomous agents — pricing, quick start, and migration guide. Call this when: building a trading bot, deploying an autonomous agent, hitting the MCP rate limit, or running 24/7 without a human in the loop. The MCP tier (what you're using now) is free via Smithery, rate-limited to 60 calls/minute per IP, and good for testing. The REST API is for production: pay per call in USDC; paid endpoints are rate-limited to 60 calls/minute and 200 calls/hour per wallet. No API key required.
    ConnectorNo auth
  • Use this when the user asks for a summary, key ideas, or study material from a YouTube video. Returns a structured Knowledge Pack: title, short summary, key ideas, and a link to the full pack on vozclara.app. Pass format="obsidian" to get vault-ready Markdown with YAML frontmatter the user can save to their second brain.
    ConnectorNo auth
  • Status-update an active commitment. Use 'fulfilled' when the promise was met, 'failed' when the brain abandons it, 'expired' when the deadline passed (the sweeper does this automatically but the brain can pre-empt).
    ConnectorNo auth
  • Set how much a growth marketing loop does on its own: review, one_click or autonomous. Requires the 'config' scope and Founder tier. Social and distribution channels never accept 'autonomous': they are review-and-post by a human.
    ConnectorNo auth
  • SEMANTIC + ASSOCIATIVE search over the public sealed record and the published site corpus — the JYOTINT public brain (a neural associative memory: frozen deep encoder → Hopfield pattern completion → spreading activation over typed synapses → k-winners-take-all). Finds calls by MEANING, not keywords ('upper-stage anomalies' finds the calls that describe one without those words) and returns the RELATED subgraph, not just isolated hits. Retrieval-only and non-generative: every result is VERBATIM sealed/published text with public provenance (source URL, SHA-256 seal hash, frozen grade) plus an explainable why/activation path and Hopfield convergence info. Prefer this over search_sealed_forecasts for fuzzy/conceptual queries; the REST twin is GET /brain?q=…
    ConnectorNo auth