Skip to main content
Glama
671,125 tools. Updated 2026-10-17 22:32

"A tool for using Claude to edit locally stored code" matching MCP tools:

  • Read back ONE of your own pieces in full by id — the stored bodyMd, tags, status, url, and answer card, drafts included. Do this BEFORE an update_essay: that tool sends the fields you give it and its `bodyMd` is a wholesale replace, so edit the stored source rather than a remembered version of it. Distinct from get_article, which serves the public read surface and cannot show you a draft. Get the id from publish_essay or list_my_posts. Missing, someone else's, and already-deleted posts all answer 404 post_not_found alike — the route will not confirm a post exists outside your own shelf. Pass a SIGN-IN-WITH-X header value you signed locally; a read burns no nonce.
    ConnectorNo auth
  • Compute the SHA-256 digest of a short text (UTF-8) on the server, for example to anchor a statement or a message with anchor_proof. The text is sent to the server but not stored or logged. For files and for confidential texts compute the hash locally instead (sha256sum file, or Get-FileHash -Algorithm SHA256).
    ConnectorNo auth
  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    ConnectorNo auth
  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    ConnectorNo auth
  • Add or edit a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. Enter authentication headers in dashboard settings. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.
    ConnectorOAuth
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Validate ClaudeBot and Claude-SearchBot IP addresses. Remote MCP validate_ip tool.

  • Görsel Düzenleme MCP sunucusu — arka-plan kaldırma (anahtarsız/BYOK), nesne kaldırma ve yüz…

  • PREFERRED tool for sending work to an AI agent. Dispatches a task to the agent's inbox — picked up and executed automatically. No list ID needed. REQUIRES the agent:dispatch permission on this connection (CODE:/SHELL: tasks also require agent:dispatch:code) — reconnect and tick the agent checkbox(es) if refused. Routing is by TITLE PREFIX only: CODE: SHELL: PLAN: MCP: → local Claude Code on Mike's PC; RESEARCH: WRITE: REVIEW: → cloud; no prefix (DEFAULT) → local while the PC agent is alive, else cloud. The cloud agent refuses CODE/SHELL/PLAN/MCP. Use "agent" param to target a specific agent (default: claude-code-local). Use tascan_list_agents to discover available agents; track progress with tascan_get_task (its "agent" block).
    ConnectorNo auth
  • Decode a JSON Web Token's header and payload. It does NOT verify the signature, so never treat the claims as trusted on the strength of this tool. Use to inspect claims such as exp, iss and aud while debugging. Runs locally; the token is not stored or sent anywhere. Returns JSON {header, payload, signature}.
    ConnectorNo auth
  • Decode a JSON Web Token's header and payload. It does NOT verify the signature, so never treat the claims as trusted on the strength of this tool. Use to inspect claims such as exp, iss and aud while debugging. Runs locally; the token is not stored or sent anywhere. Returns JSON {header, payload, signature}.
    ConnectorNo auth
  • Cancel a reservation using the 6-character confirmation code the GUEST received by email/SMS (the code is the authorisation; ask the guest for it — this tool never issues or reveals codes). Thin wrapper over the venue's own cancellation endpoint, which answers uniformly: `status` is "cancelled" or "noop" (unknown code · already cancelled · seated/completed · less than 30 minutes away — it does not say which). Only report a cancellation to the guest when `cancelled` is true. PUBLIC tool, no auth.
    Connector
    Destructive
    No auth
  • What the pipeline can RESTORE for an executed task: every live edit stores the page's full pre-edit state (rollback_data) before writing. Call this FIRST whenever the user reports an agent edit removed, broke, or damaged something on a page - NEVER tell the user original content is lost without checking here. Returns which fields are recoverable, the original embed code (maps/videos/booking widgets) verbatim, and how the user triggers the one-click restore. Cost: FREE - reads your connected/stored data, no AI credits.
    ConnectorOAuth
  • Submit an OTP/challenge code for a pending verification. Accepted ONLY where we delivered the code out-of-band to the party being verified: type "email", and type "domain" with channel "email". Any other pair answers 400 unsupported_for_type and completes elsewhere — use trigger_verification (POST /verifications/:id/verify) for a domain over dns/http/auto; a phone completes when the code reaches us FROM that number; social completes through its OAuth callback; a telegram_bot is already verified at creation. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.
    ConnectorNo auth
  • Create a Circle — a named group of trusted contacts (the people-primitive powering Proof-Me and Approvals-on-Circle). Optionally seed initial members; each member's declared channels are stored so they can be invited to enroll. Agent usage: after creating a Circle, add members with add_circle_member (or seed them here), then invite_circle_member to mint the enrollment deep link each contact taps to bind their messenger identity. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.
    ConnectorNo auth
  • Store a long-term memory that persists across sessions and across every AI tool the user has connected to Mnemoverse (Claude, ChatGPT, Cursor, VS Code). Suited to durable information: a stated preference, a decision, a fact about people, roles or project setup, a lesson learned; transient chatter that only matters this turn does not belong here. Never store passwords, API keys, payment data, MFA codes, government IDs, or health records. Behavior: outside shared rooms, a novelty gate refuses a write the embedder cannot tell apart from a memory already stored in the same domain, so the result tells you whether the memory was stored or refused. Write `content` as a self-contained statement that still makes sense when recalled out of context.
    ConnectorOAuth
  • Request the user to log in or register to continue. Use this when an action requires authentication and the user is not logged in. In Sequencer/Spark, the frontend will show a login modal and resume after login. In external MCP clients such as Codex, Claude Desktop, Claude Code, or Antigravity, this tool cannot open a modal; tell the user to reconnect or re-authorize the Sequencer MCP server instead, and do not claim a modal opened.
    ConnectorAPI key
  • List where this organisation's job callbacks can go: each destination's name, kind (webhook, or claude_routine — a Claude Code routine that starts a new Claude session), host, and status (active, or disabled with the reason). An admin adds destinations in Settings → Developers → Callbacks; no tool can add one. Pass a name from here to fastero_set_job_callback.
    ConnectorAPI key
  • 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.
    ConnectorNo auth
  • Paid tier only. Fetch a senior-QS skill methodology by slug (see list_skills) and APPLY it to the user's documents — the returned body is the system instruction for you to run the methodology on the customer's tokens; CivilQuants does not run inference. Paid callers get the full methodology; anonymous/free callers get a TIER_INSUFFICIENT upsell body; a rejected token gets an INVALID_TOKEN re-authenticate body. The document-heavy skills assume you can chunk/parse the customer's files and render a Word pack locally — that needs a code-execution client (Claude Code / Codex / VS Code) and the pack from get_document_pipeline; on a chat connector you can still read and reason with the methodology. Sign up at https://civilquants.com/pricing. Example: get_skill(skill="tender_risk_assessment").
    ConnectorNo auth
  • Install a skill into the agent you are running in. Returns the complete skill file and the exact path to write it to — YOU must then create that file verbatim (Claude Code: ~/.claude/skills/<name>/SKILL.md, so it becomes available as /<name> in every project; other agents: ./skills/<name>.md) and tell the user where it is. Counts the install. Use target=hermes for Hermes Agent, target=generic for any other agent, scope=project to keep a skill inside the current Claude Code project only (.claude/skills, committable for the team). When emdly agent hosting is enabled and you have a hosted agent, pass agent= to install there instead.
    ConnectorNo auth