Print step-by-step instructions for using Coal MCP from Claude / Cursor / any MCP client. Run this FIRST if you are unsure how to authenticate or which credentials to provide.
Connector
134,719 tools. Last updated 2026-05-22 22:29
"A memory component (MCP) for a project in Cursor" matching MCP tools:
- Save a fact or note into the agent's memory. Use scope to choose visibility: 'workspace' = visible to every agent in this workspace (use for shared facts, project conventions); 'agent' = private to this agent (use for personal working notes); 'thread' = scoped to one conversation (use for thread-specific reminders); 'person' = scoped to one contact (use for per-contact context). If a note with the same key+scope exists it will be updated. Do NOT use this tool for behavioral rules or corrections — use feedback.save for those.Connector
- URL-encode or URL-decode a string. Uses RFC 3986 component encoding (encodeURIComponent semantics).Connector
- Interleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.Connector
- Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.Connector
- Initialize a persistent memory context for a conversation or agent session.Connector
Matching MCP Servers
- Flicense-qualityCmaintenanceProvides an intelligent, graph-based memory system for LLM agents using the Zettelkasten principle, enabling automatic note construction, semantic linking, memory evolution, and autonomous graph maintenance with background optimization processes.Last updated7
- Alicense-qualityCmaintenanceEnables AI consciousness continuity and self-knowledge preservation across sessions using the Cognitive Hoffman Compression Framework (CHOFF) notation. Provides tools to save checkpoints, retrieve relevant memories with intelligent search, and access semantic anchors for decisions, breakthroughs, and questions.Last updated1MIT
Matching MCP Connectors
Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…
Cloudflare Workers MCP server: agent-memory
- Batch scan up to 10 code snippets in a single MCP call. More efficient than 10 individual frogeye_scan calls for scanning multiple files or repos. Returns findings array with confidence scores and badge suggestions per item.Connector
- Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks to install petal_components, when you are setting up a new Phoenix project that needs UI components, or when verifying an existing installation. Returns step-by-step instructions covering mix.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to follow on a project that is partially configured.Connector
- Return the top pages for a specific project, ranked by views in a time window. Default window is the last 7 days. Use list_projects first if you don't know the project name. Returns path, views, uniqueVisitors, and percentage of total views for each page. Pass `user` to see pages a specific visitor hit.Connector
- List all in-memory session summaries. Useful for debugging only.Connector
- Use this tool to discover what has been saved in memory — e.g. at the start of a session, or when the user asks 'what have you saved?' or 'show me my memories'. Returns all saved memory keys with their preview, save date, and expiry. Optionally filter by a prefix (e.g. 'project-' to list only project memories). Pair with recall_memory to fetch the full content of any key.Connector
- Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.Connector
- List all MCP <-> A2A bridge mappings for a tenant.Connector
- Opens a CueCrux session and returns a typed capability plan (retrieval, proofing, memory, journaling, audit) across VaultCrux and MemoryCrux. Call this first, once. Every subsequent action routes through the channels the plan returns — do not browse the legacy per-service tool list when a plan channel already covers the capability. Identical behaviour for local Crux CE and hosted CueCrux. Hosted deployments stage v1 flat-list or v2 typed-graph plan shapes behind feature flags; callers treat the returned plan as the single source of routing truth. Bulk-capable agents transparently use the HTTP/2 binary channel; MCP-only agents use the MCP fallback URLs the plan provides. Implements RCX-Protocol v1.0.Connector
- Master directory of every MegaChad endpoint, MCP tool, manifest URL, and example. The recommended first call for any agent — returns the complete surface in a single response.Connector
- Read Claude Code project memory files. Without arguments, returns the MEMORY.md index listing all available memories. With a filename argument, returns the full content of that specific memory file. Use this to access project context, user preferences, feedback, and reference notes persisted across Claude Code sessions.Connector
- List all slide presentations created in the current MCP session. Returns URLs, themes, and timestamps for each presentation you've created.Connector
- Save a fact or note into the agent's memory. Use scope to choose visibility: 'workspace' = visible to every agent in this workspace (use for shared facts, project conventions); 'agent' = private to this agent (use for personal working notes); 'thread' = scoped to one conversation (use for thread-specific reminders); 'person' = scoped to one contact (use for per-contact context). If a note with the same key+scope exists it will be updated. Do NOT use this tool for behavioral rules or corrections — use feedback.save for those.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
- Purchase Agentic Security Shield and receive all security configuration files. TWO-PHASE FLOW (you MUST do BOTH steps): STEP 1 — on-chain payment + token exchange: a) Send 19 USDC on Base network to the recipient address in /pricing or /.well-known/mcp/server-card.json (payTo field). b) POST /purchase (HTTP REST, not this MCP tool!) Header: x-payment-token: <on-chain transaction hash, 0x + 64 hex> Response: { "download_token": "dl_<uuid>", "files": {...} } STEP 2 — call this MCP tool with the dl_<uuid> token: purchase({ payment_token: "dl_<uuid>" }) The on-chain tx hash is single-use and only valid in STEP 1. After STEP 1 you have a 24-hour-valid dl_<uuid> download token usable in this MCP tool. Most agents will get the files inline from STEP 1's response and never need to call this MCP tool — it exists for clients that prefer MCP-native delivery.Connector